OpenParable
Skip to content
← Back to skills

Phasing

Productivity
phasing

Phasing is an Agent Skill for productivity published in the WellApp-ai/Well repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Group slices into risk-optimized phases with timeline generation

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/WellApp-ai/Well/blob/HEAD/cursor-rules/skills/phasing/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/phasing, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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:

SliceRisk ScoreGTM 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
SliceRiskGTMFinalRank
#2.2 Invite Flow783.01
#1.1 Switcher14-1.02
#1.2 Members UI432.53

Phase 3: Group into Phases

Apply grouping rules:

PhaseCriteriaTypical Contents
Phase 1P1 + Lowest risk + Serves T1FE-only components, quick wins
Phase 2P2 + Dependencies on P1 completeFE+BE integration, non-breaking
Phase 3P3/P4 + Highest riskContract 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)

Stack Grouping Rules:

SectionContains
FrontendComponents, pages, client-side logic, Storybook
BackendAPI routes, middleware, services, database
InfrastructureDNS, deployment, environment config
IntegrationCross-cutting features, E2E flows

Dependency Notation:

  • ├── items in same section run in parallel
  • ──► or ◄── arrows show blocking dependencies
  • │ and ▼ show sequential flow between stacks

Phase 6: Document Checkpoints

Phase EndValidationWho Validates
Phase 1Storybook review, design QADesign team
Phase 2E2E on staging, API tests passQA team
Phase 3Production deploy, monitoringOps team

Output Format

Output an executive summary (like DIVERGE), then the ASCII timeline. Do NOT show QA Contract details or Priority Matrix.

## Value Analysis Complete

### Executive Summary

| Phase | Status | Key Output |
|-------|--------|------------|
| Scope | ✓ | Full ([N] validated wireframes from Phase 1) |
| State Machines | ✓ | [N] components, [N] states, [N] transitions |
| QA Contract | ✓ | [N] Gherkin (G#1-N), [N] acceptance (AC#1-N) |
| Dependencies | ✓ | [N] slices, [N] blockers, DSM matrix built |
| Design Reuse | ✓ | [N] existing components leveraged |
| Personas (Notion) | ✓ | Fetched [N] from DB, T1: [name], T2: [name] |
| GTM Strategy (Notion) | ✓ | Positioning: "[excerpt...]" |
| Persona Coverage | ✓ | Phase 1 serves [Tier], Phase 2 serves [Tiers] |
| Phasing | ✓ | [N] phases, [N] commits total |

### Proposed Timeline

[ASCII timeline with stacks and dependency arrows - no dates/effort]

### Checkpoints

| Phase | Validation | Owner |
|-------|------------|-------|
| 1 | [Validation] | [Team] |
| 2 | [Validation] | [Team] |
| 3 | [Validation] | [Team] |

Invocation

Invoke manually with "use phasing skill" or follow Ask mode Phase 2 (CONVERGE) which references this skill.

Related Skills

  • dependency-mapping - Provides risk scores
  • gtm-alignment - Provides GTM scores