Skill 3 of 6 · Execute
deep-implement
/deep-implement
Executes your reviewed plan phase by phase - implement, validate, fix, commit - leaving a clean checkpoint after every phase.
What it does for you
Execution you don't have to babysit
The plan is the contract. deep-implement builds exactly what it specifies - and proves each step before moving on.
Checkpoints, not big bangs
Each phase is implemented by a fresh agent, validated, and committed on green - so every commit is a known-good restart point instead of one giant risky diff.
Walk away or stay in the loop
Autonomous mode runs unattended and only pings you on a hard blocker or completion. Collaborative mode gates every phase on your approval. Switch anytime.
It never thrashes
A bounded fix loop caps retries at two, then hands back a structured blocker report stating exactly what failed, what was tried, and the one decision it needs from you.
Resumable by anyone
Progress lives in the plan document itself, not in chat history. Close the laptop mid-run - any fresh agent picks up at the first unfinished phase tomorrow.
The discipline
Every phase lands green - or not at all
Validation gates on new failures in the code it changed, so pre-existing noise never stalls a run - and genuinely broken work never slips through.
Broken code is never committed. If a phase can't validate within the fix cap, deep-implement stops, preserves the work in flight, and hands you a blocker report - it doesn't paper over the failure and keep going.
Where it fits
The only skill that writes source code
Everything before it sharpens the spec; everything after it verifies the result.