Commands
Workflow commands
All 10 commands covering the complete development lifecycle — from planning to autonomous overnight builds.
Typical workflow order
/plan/tdd/verify/code-review/ralph-loopPlanning
1 commandDefine what to build before writing any code
/planPlanningThink before buildingReads your specification, explores the existing codebase, and creates a detailed implementation plan. Surfaces risks, asks clarifying questions, and identifies the right order of operations.
- Analyzes PRD acceptance criteria, data model, and API design
- Creates step-by-step implementation plan with dependencies
- Identifies risks and open questions
- Waits for your explicit approval before writing any code
/plan docs/prds/001-my-feature.mdImplementation
3 commandsWrite code the right way — TDD, clean, verified
/tddImplementationTests first, alwaysEnforces test-driven development. Writes a failing test, implements the minimum code to pass it, then refactors. Repeats for each acceptance criterion.
- RED: write a failing test for the next AC
- GREEN: implement minimum code to pass
- REFACTOR: improve without changing behavior
- Targets 80%+ coverage on new code
/tdd/build-fixImplementationDiagnose, don't guessReads build error output, identifies root causes, and applies targeted fixes. Works incrementally — fixes one error at a time, rebuilds, and repeats.
- Reads full error messages and stack traces
- Identifies root cause before attempting fixes
- Applies targeted changes, not broad rewrites
- Rebuilds after each fix to verify
/build-fix/refactor-cleanImplementationLess code, same behaviorRemoves dead code, unused imports, and unnecessary complexity. Runs tests before and after every change to ensure nothing breaks.
- Identifies unused exports, imports, and variables
- Consolidates similar functions
- Improves naming without changing behavior
- Tests before and after every change
/refactor-cleanQA
3 commandsVerify correctness, security, and quality
/verifyQAEvery quality gate, every timeRuns all 8 quality gates in sequence and reports pass/fail for each. These are requirements, not suggestions. A feature is not done until all gates pass.
- Build (0 errors), Types (0 errors), Lint (0 warnings)
- Tests (all pass, 80%+ coverage)
- Security (no OWASP vulnerabilities)
- Debug logs (0 console.log), Type safety (no any/as), File size (max 300 lines)
/verify/e2eQATest real user flowsGenerates and runs end-to-end tests using Playwright. Tests real user flows through browser automation — page loads, navigation, form submissions, and critical journeys.
- Auto-generates Playwright test scripts
- Tests critical user journeys end-to-end
- Captures screenshots and traces on failure
- Uses accessibility-tree selectors for stability
/e2e/code-reviewQAA second pair of eyesSecurity audit and architecture validation. Reviews every change for OWASP vulnerabilities, code quality violations, architecture rule breaches, and common mistakes.
- OWASP Top 10 vulnerability scanning
- Architecture and design pattern validation
- RLS policy completeness check (Supabase)
- Rates findings: Critical, Warning, Info
/code-reviewAutomation
2 commandsLet Claude build autonomously overnight
/ralph-loopAutomationBuild while you sleepThe most powerful feature. Claude works autonomously — writing code, running tests, fixing errors — until every quality gate passes and your completion promise is 100% true.
- Iterates: read spec → check state → implement → verify → repeat
- Built-in error recovery: pivots strategy after 3x same error
- Status report at 80% of max iterations
- Only outputs completion promise when genuinely true
/ralph-loop "Build feature X" --max-iterations 30 --completion-promise "All tests pass"/cancel-ralphAutomationTake back the wheelStops an active Ralph Loop. Use when you want to take over manually, change direction, or if the loop is not converging on the desired outcome.
- Immediately stops the autonomous loop
- Preserves all work done so far
- Git history shows every iteration
- Resume with a new /ralph-loop if needed
/cancel-ralphSafety
1 commandProtect your work before risky changes
/checkpointSafetySave before you experimentCreates a git restore point with a descriptive tag. Use before risky changes, large refactors, or experiments so you can always roll back.
- Creates a tagged git commit as restore point
- Descriptive tag for easy identification
- Roll back with a single git command
- Zero cost — just a commit and tag
/checkpoint