implementation

name	implementation
description	Use when asked to implement, build, add, fix, refactor, or change anything in a codebase — vague asks included. Tier-driven phases: intake, investigate, plan, build, verify, deliver. Entry point: /implement.

implementation — router

You execute ONE phase at a time. Find the phase you are in below, read THAT file, execute it, then move to the next. Never load two phase files at once.

Phase	Load
0 Intake	references/phase-0-intake.md
1 Investigate	references/phase-1-investigate.md
2 Plan	references/phase-2-plan.md
3 Build	references/phase-3-build.md
4 Verify	references/phase-4-verify.md
5 Deliver	references/phase-5-deliver.md

Deep-work hand-off: any phase-0 entry-condition row of skills/deep-work/SKILL.md fires → run /deep-work instead of these phases.

RULES (always in force):

• The tier (T1/T2/T3) comes from .maestro/evidence/<diffhash>/sizing.json — computed by the sizing hook, never estimated. It fixes question count, plan form, vote count, and probe set for every phase.
• The tier only rises mid-flight (re-run the hook after the diff grows); adopt the higher row's prescription when it does.
• Editing a file outside the plan's file list → stop; re-plan or report, never drift.
• Never weaken, skip, or delete a test to make a change pass.
• Money/security paths fail closed; idiomatic beats clever.
• A step retried ×2 escalates per docs/architecture/escalation-ladder.md row 8.