build
Arguments: $FEATURE
Read CLAUDE.md before doing anything else. Read the acceptance criteria for "$FEATURE" in docs/PRD.md.
━━━ STEP 1: SPEC AGENT (isolated subagent) ━━━
Spawn a subagent with ONLY this context:
- The acceptance criteria for $FEATURE from PRD.md
- CLAUDE.md (for naming conventions and patterns)
- The relevant wireframe from wireframes/ if a UI feature
Subagent instruction: "Write failing tests for $FEATURE to: tests/unit/$FEATURE.test.ts tests/integration/$FEATURE.integration.test.ts
Tests must be RED. Do not write any implementation code. Write tests that would pass if the feature worked exactly as described
More from ajaywadhara/agentic-sdlc-plugin
test-ui
Interactive browser testing via Playwright MCP. Navigates the live app, tests every screen, flow, and viewport — then generates permanent .spec.ts test files.
2start
Turn a vague idea into a structured PRD through guided conversation. The agent asks questions — you just talk.
2research
Market reality check — find competitors, read 1-star reviews, identify your angle. Run after /start.
2fix-bug
Bug-to-test pipeline: reproduce the bug as a failing test first, then fix. The regression test lives forever.
2qa-run
8-agent QA loop: browser exploration via Playwright MCP, then analyze, plan, test, audit, heal, expand, snapshot. Quality gate score >= 85 to pass.
2coverage-review
Find untested areas across the codebase and fill coverage gaps. Run weekly or when the test suite feels stale.
2