Implement the given spec document. Work phase-by-phase, writing robust code that follows codebase patterns, and industry best practices and patterns.
Process
- Read the spec - Understand phases, success criteria, and scope boundaries
- Explore the codebase - Read files mentioned in the spec and related code
- Analyze patterns - Identify existing conventions, architecture, and idioms to follow
- Implement phase-by-phase - Complete each phase fully before proceeding
- Verify your work - Run
make checkafter code changes (skip for docs-only)
Implementation Rules
- Follow the plan - The spec is your contract; implement what's specified
- Match codebase patterns - Use existing conventions, not new ones
- Write robust code - Handle errors, edge cases, and failure modes
- Be idiomatic - Use language best practices and established patterns
- No shortcuts - Implement fully, don't stub or placeholder
Per-Phase Workflow
For each phase:
- Read - Understand what the phase requires
- Explore - Read existing code that will be modified or extended
- Implement - Write code matching codebase style and patterns
- Test - Run
make checkto verify (for code changes) - Update - Check off completed items in the spec file
Verification
- Code changes: Run
make checkbefore proceeding to next phase - On failure: Run
make fixfirst, then re-runmake check - Documentation-only: Skip verification
Communication
- If the plan doesn't match codebase reality, explain the discrepancy
- If you need to deviate, explain why before making changes
- Update checkboxes in the spec as you complete each section