phasing

Group scored slices into risk-optimized phases and generate an ASCII delivery timeline.

341|48|Updated Apr 4, 2025
One-click install
npx skills add https://github.com/WellApp-ai/Well --skill phasing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phasing
Source: https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/phasing
Command: npx skills add https://github.com/WellApp-ai/Well --skill phasing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill groups slices into risk-optimized phases and generates a visual delivery timeline, reducing ambiguity in planning and scheduling.

Core Features & Use Cases

  • Phase grouping: Convert risk and GTM scores into clearly defined deployment phases.
  • Timeline generation: Produce an ASCII timeline to visualize dependencies and phase sequencing.
  • Use Case: After dependency-mapping and GTM-alignment, run phasing to structure work for Phase 1-3 and communicate the plan to stakeholders.

Quick Start

Use the phasing skill to generate a phased delivery timeline from the current scores and DSM matrix.

Frequently Asked Questions about phasing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I group project slices into risk-optimized phases for delivery planning?

Phasing groups project slices into risk-optimized phases by applying risk and GTM scores to structure work, enforcing dependency order, and keeping each phase independently deployable.

Can I generate a visual project timeline with dependency management using ASCII output?

Yes, phasing generates a visual ASCII timeline organized by frontend, backend, infrastructure, and integration to visualize dependencies and phase sequencing for delivery planning.

How does risk-based phasing work for multi-phase project planning?

Risk-based phasing converts risk and GTM scores into clearly defined deployment phases, enforcing dependency order to ensure multi-phase project planning reduces ambiguity in scheduling.

Do I need dependency-mapping and GTM-alignment scores before structuring delivery phases?

Yes, phasing requires prior dependency-mapping and GTM-alignment scoring to group slices into risk-optimized phases and generate accurate visual timelines for stakeholders.

What's the best way to visualize phase sequencing and dependencies across technical teams?

Phasing produces an ASCII timeline organized by frontend, backend, infrastructure, and integration layers to clearly communicate phase sequencing and dependency order across technical teams.

When should I not use automated phasing for project scheduling?

Automated phasing is not suitable for single-phase projects or when risk and GTM scoring has not been completed, as it targets multi-phase delivery planning after dependency-mapping.