plan

Multi-phase project planning structures work into discrete research, planning, building, validation, and cleanup phases with memory-optimized isolation. This Skill automates phase sequencing, loads only required context per phase, and tracks progress in CURRENT_PLAN.md so you resume exactly where you left off without reloading prior work.

Yes. The Skill reads CURRENT_PLAN.md to resume from the current phase, preserving prior phase outputs and cross-phase knowledge references. You continue with the next phase without re-running completed work or reloading full context.

Workflow orchestration across phases uses phase templates and an executable orchestrator that structures inputs, outputs, and summaries for each stage. The Skill automates phase transitions, generates phase-specific artifacts, and maintains a concise knowledge base so each phase loads only what it needs.

No. The Plan Orchestrator initializes a new plan from a goal statement and optional phase list. It generates the CURRENT_PLAN.md structure and phase templates automatically, so you begin immediately without pre-existing documentation.

Memory-aware isolation loads only the current phase's summary, inputs, and cross-phase references instead of full prior outputs. This minimizes context bloat while preserving knowledge flow, letting complex multi-phase workflows run within tighter memory budgets.

The Skill tracks phase status in CURRENT_PLAN.md. If a phase fails, you can inspect the phase output, adjust inputs, and resume from that phase without losing prior progress or reprocessing completed phases.