phase-planning

Phase planning generates a 5-phase structure with validation gates that automatically distributes timelines and scope based on your project's complexity score. The plan includes explicit criteria for progressing between phases, ensuring you neither over-scope simple work nor under-estimate complex delivery.

Validation gates are mandatory checkpoints between phases that verify readiness before proceeding. They prevent phase overflow by enforcing explicit criteria—such as spec completeness or risk sign-off—ensuring each phase meets its objectives before moving forward, reducing rework and delivery failures.

Yes. For higher-complexity projects, phase planning generates wave-coordination mapping that identifies which work streams can run in parallel. This optimization reduces timeline compression while maintaining validation integrity across overlapping phases.

The Skill accepts a complexity_score input that drives both phase count distribution and timeline allocation. Lower complexity consolidates work into shorter phases; higher complexity extends phases and adds coordination overhead, automatically tailoring the plan to your actual project scope.

Yes. Phase plans are persisted to Serena, enabling cross-session retrieval and tracking. This allows you to reference earlier phase definitions, gate decisions, and coordination mappings without rebuilding the plan structure.

Provide your project name, a complexity_score (typically 0–1 range), and spec_analysis_result data. These inputs determine phase distribution, gate criteria, and timeline estimates. Serena dependency integration enables historical context if prior phases exist.