Implement the following specification: $ARGUMENTS
Workflow
Phase 1: Requirement Extraction (10% of effort)
- •Read the spec file (if a path was given) or parse the description
- •Extract atomic, testable requirements
- •Identify dependencies (internal and external)
- •Create a checklist of acceptance criteria
Phase 2: Test-First Development (25% of effort)
For each requirement:
- •Write a failing test that captures the requirement
- •Run the test to confirm it fails (red)
- •Move to the next requirement
Phase 3: Implementation (50% of effort)
For each failing test (in dependency order):
- •Implement the minimum code to make the test pass
- •Run the test to confirm it passes (green)
- •Refactor if needed (keeping tests green)
- •Check for regressions after each change
Spiral detection: If you find yourself editing the same files 3+ times without making progress, stop and reassess your approach.
Phase 4: Verification (15% of effort)
- •Run the full test suite
- •Walk through each acceptance criterion — does the implementation satisfy it?
- •Check for edge cases not covered by tests
- •Report results
Output
At completion, present:
code
## Implementation Summary Requirements: [N total, N implemented, N deferred] Tests: [N passing, N failing, N skipped] Files changed: [list] Acceptance Criteria: - [criterion 1]: PASS | FAIL - [criterion 2]: PASS | FAIL Deferred items (if any): - [item]: [reason deferred]