execute-phased-plan

To maintain context window efficiency during long-term software development tasks, enforce strict phase-boundary stops and generate context-preserving handover prompts. This prevents context degradation by starting each phase in a fresh, optimized chat.

The best way to orchestrate multi-phase coding plans with subagent-driven development is to enforce structured handovers. This validates each phase against specific exit criteria before moving forward, ensuring task-specific focus and clean context transitions.

To execute a development plan located in a markdown file phase by phase, invoke the skill targeting path/to/plan.md. It orchestrates the execution by automatically stopping at phase boundaries to preserve context hygiene.

Context degradation causes quality loss in complex, long-running coding workflows because the context window becomes overloaded over time. Enforcing strict, chat-level pacing and clean handovers between phases prevents this degradation and maintains task-specific focus.

You cannot use phase-based pacing for automation workflows without defined exit criteria. The mechanism requires adherence to defined exit criteria for each phase to validate subagent-driven development before moving forward.