distillation-implementationlisted

# Distillation Implementation (Stage 3) Execute the distillation plan, task by task. Every task is a port: bring the reference's encoded decisions into your project — preserving the keep-verbatim items exactly, following the task's adaptation notes, and wiring the seams to your dependencies. **Why subagents:** You delegate logic-heavy chunks to fresh agents with isolated context. By crafting their instructions precisely — the task's keep-verbatim items, its seam substitutions, its adaptation notes — you keep them focused and stop the reference's packaging from leaking into your project. They never inherit your session's history; you hand them exactly the chunk they need. This also preserves your own context for coordination work. **Core principle:** Fresh subagent per logic-heavy chunk + two-stage distillation-aware review (spec compliance then code quality) = faithful port, fast iteration. Mechanical chunks go direct. **Continuous execution:** Do not pause to check in with the user between tasks. The human gates are between stages, not between tasks. Execute the whole plan, then finish the branch. Stop only for a BLOCKED you cannot resolve, genuine ambiguity, or completion. ## When to Use You're in Stage 3: the distillation plan is approved. Execute it. One decision drives each task — whether it takes the subagent path or the direct path. ```dot digraph when { "Task: logic-heavy or risky?" [shape=diamond]; "Dispatch implementer subagent + two-stage review" [sh