generateTurn a plan, a goal or a recorded spec into SDODS features, steps and page objects, proposed for review.
healDiagnose a failing SDODS scenario and propose the smallest locator or step fix. Defaults to the last failed run.
planPlan tests for a feature area with the SDODS planner — a tagged scenario plan saved as a proposal.
recordRecord a browser flow with SDODS for a given project, environment, user role and device, save it as a runnable spec, replay it, and optionally convert it into a Gherkin feature with reusable steps. Use when the user says "record", "codegen", "capture a flow", "re-record as <role>", or wants the same
reviewReview SDODS feature files for tagging, step reuse, data-driven refactors and best practices.
runRun SDODS test suites for a project across environments, layers (ui/api/hybrid/recorded), browsers, suites (@smoke/@regression) and user roles, then read the results. Use when the user says "run the tests", "smoke on staging", "regression on all browsers", "run as <role>", or asks what failed.
setupCheck that SDODS is ready in this project — CLI, Node, browsers, workspace and MCP server — and fix what is missing.
start-uiStart the SDODS web UI on any OS and get the first user signed in. Use when someone says "start the UI", "open the dashboard", "run the web app", "sdods serve", "I can't log in", "it says the web UI is not available", "port 4444 in use", "how do I register", or is onboarding onto SDODS for the first
upgradeMap application or API changes to the SDODS scenarios they affect and propose updates.
workspaceWork in an SDODS test-automation workspace — BDD features for UI, API and hybrid flows. Use when writing, fixing or reviewing Gherkin features, steps, page objects or project/env YAML, running suites, reading results, or using the sdods CLI or its MCP tools.