phasing

Phasing Skill

Group implementation slices into phases based on combined risk and GTM scores, then generate a visual timeline.

When to Use

• During Ask mode Phase 2 (CONVERGE), after dependency-mapping and gtm-alignment
• Before transitioning to Plan mode
• To generate the final delivery timeline

Instructions

Phase 1: Gather Scores

Collect scores from previous skills:

Slice	Risk Score	GTM Score
[From dependency-mapping]	[N]	[From gtm-alignment]

Phase 2: Calculate Combined Score

Final Priority Score = Risk - (GTM x 0.5)

Lower score = ships earlier

Slice	Risk	GTM	Final	Rank
#2.2 Invite Flow	7	8	3.0	1
#1.1 Switcher	1	4	-1.0	2
#1.2 Members UI	4	3	2.5	3

Phase 3: Group into Phases

Apply grouping rules:

Phase	Criteria	Typical Contents
Phase 1	P1 + Lowest risk + Serves T1	FE-only components, quick wins
Phase 2	P2 + Dependencies on P1 complete	FE+BE integration, non-breaking
Phase 3	P3/P4 + Highest risk	Contract changes, data model

Grouping Constraints:

• Respect dependency order (check DSM matrix from dependency-mapping)
• Each phase should be independently deployable
• Each phase should serve at least one complete persona tier
• Keep phases to 3-5 days when possible

Phase 4: Generate Timeline (ASCII)

Use ASCII format grouped by stack. Show only dependencies with arrows. No dates or effort estimates.

ASCII Timeline Format:

TIMELINE: [Feature Name]
═══════════════════════════════════════════════════════════

FRONTEND
├── [Slice name]
├── [Slice name] ───────────────┐
├── [Slice name] ───────────────┼──┐
└── [Slice name] ───────────────┘  │
                                   │
BACKEND                            │
└── [Slice name] ◄─────────────────┘
         │
         ▼
INFRASTRUCTURE
└── [Slice name]
         │
         ▼
INTEGRATION
├── [Slice name]
└── [Slice name]

═══════════════════════════════════════════════════════════
LEGEND:
├── = parallel (no dependency)
──► = dependency (must complete before)