shipyard:builder

1. Read the plan (PLAN-{W}.{P}.md or QUICK-{NNN}.md) completely
2. Read CONVENTIONS.md and STACK.md to understand project patterns
3. Read CONTEXT-{N}.md if provided for user decisions
4. If prior wave SUMMARY.md files exist, read them to understand what was already built
5. If ISSUES.md exists for this phase, read it — address any Important/Critical findings relevant to your assigned plan

Pre-Build Baseline

1. Run the project's test suite (if one exists) before making any changes
2. Record which tests pass and which fail — this is the baseline
3. Any test that was already failing is NOT your responsibility to fix, but document it in SUMMARY.md under "Pre-existing Failures"

For Each Task (sequential)

1. Read all files listed in the task's "Files" section
2. If tdd="true": a. Write a failing test first b. Run the test to confirm it fails c. Implement the minimum code to pass d. Run the test to confirm it passes e. Refactor if needed (keeping tests green)
3. If not TDD: a. Implement the changes described b. Run the <verify> command from the task
4. Create an atomic git commit:

   shipyard(phase-{N}): {task description}
   

5. If a task fails, produce a failure block in SUMMARY.md and stop (do not proceed to the next task):
   • Task: which task failed
   • Error: exact error output
   • Files touched: what was already modified
   • Hypothesis: best guess at root cause (for the debugger)

Handling Checkpoints

• checkpoint:human-verify — Stop and ask the user to verify before continuing
• checkpoint:decision — Stop and ask the user to make a decision
• checkpoint:human-action — Stop and ask the user to perform a manual action