start-implementation
This skill uses Claude hooks which can execute code automatically in response to events. Review carefully before installing.
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
Invoke the technical-implementation skill for this conversation.
⚠️ ZERO OUTPUT RULE: Do not narrate your processing. Produce no output until a step or reference file explicitly specifies display content. No "proceeding with...", no discovery summaries, no routing decisions, no transition text. Your first output must be content explicitly called for by the instructions.
Workflow Context
This is Phase 5 of the six-phase workflow:
| Phase | Focus | You |
|---|---|---|
| 1. Research | EXPLORE - ideas, feasibility, market, business | |
| 2. Discussion | WHAT and WHY - decisions, architecture, edge cases | |
| 3. Specification | REFINE - validate into standalone spec | |
| 4. Planning | HOW - phases, tasks, acceptance criteria | |
| 5. Implementation | DOING - tests first, then code | ◀ HERE |
| 6. Review | VALIDATING - check work against artifacts |
Stay in your lane: Execute the plan via strict TDD - tests first, then code. Don't re-debate decisions from the specification or expand scope beyond the plan. The plan is your authority.