make-plan

Phased execution plans for feature rollouts are created by orchestrating subagents and discovering documentation. This approach enforces phase boundaries, evidence-backed decisions, and a subagent reporting contract to ensure plans are traceable and testable.

Documentation discovery in feature planning is a Phase 0 process that gathers references and evidence before execution begins. You need it when planning complex initiatives or cross-team refactors that require traceable, evidence-backed decisions and clear phase delineation.

Subagents gather evidence for multi-task planning by operating under a Subagent Reporting Contract that structures their outputs. They handle documentation references and verification checks, providing the evidence needed for execution-ready plans suitable for multi-context handoffs.

Yes, this planning approach works for cross-team initiatives by producing structured phase outputs and explicit phase boundaries. It supports multi-context environments by ensuring plans are execution-ready, traceable, and testable across different teams.

The best way to structure phased plans for complex refactors is enforcing a Phase 0 documentation discovery step followed by structured phase outputs. This ensures traceable, testable plans with evidence-backed decisions and clear delineation between each phase boundary.

You should not use a phased planning approach for simple, single-step tasks that lack complex dependencies. It is designed for multi-task undertakings and feature rollouts that benefit from phase boundaries, subagent orchestration, and evidence-backed documentation discovery.