phase-planning

# Phase Planning Skill

## Overview

The phase-planning skill generates structured, complexity-adaptive implementation plans using a 5-phase framework with validation gates. It adapts phase count and timeline distribution based on project complexity, ensuring appropriate rigor for simple scripts through critical systems.

## When to Use

Use this skill when:
- Planning implementation after spec analysis complete
- Need structured timeline with validation checkpoints
- Want systematic progression with quality gates
- Require resource allocation and effort distribution
- Have complexity score from spec-analysis (0.0-1.0)

DO NOT use when:
- No spec analysis available (run @spec-analysis first)
- Ad-hoc tasks without formal planning needs
- Quick experiments or prototypes

## Core Competencies

1. **Complexity-Adaptive Planning**: Automatically adjusts phase count (3-6 phases) based on complexity score, ensuring appropriate rigor without over-engineering
2. **Timeline Distribution**: Calculates optimal time allocation per phase using algorithmic formula with complexity and domain-based adjustments
3. **Validation Gates**: Defines explicit success criteria between phases to prevent downstream failures and ensure quality progression
4. **Wave Coordination**: Maps parallel execution patterns to phases for multi-agent coordination when complexity >=0.5
5. **Serena Integration**: Persists phase plans to memory for cross-session retrieval and wave agent coordination

## Inputs

**Required:**
- `complexity_score` (float 0.0-1.0): Complexity score from spec-analysis
- `spec_analysis_result` (object): Complete spec analysis including domain breakdown, features, timeline constraints
- `project_name` (string): Name of project for phase plan identification

**Optional:**
- `timeline_constraint` (string): Total available timeline (e.g., "40 hours", "2 weeks")
- `domain_preferences` (object): Override domain-based timeline adjustments
- `custom_phases` (array): Custom phase definiti