phase-planner

Generates per-track phase plans of agent-executable task cards from PRD and architecture documents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vinodkrishna221/Q-Trace --skill phase-planner-vinodkrishna221
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-planner
Source: https://github.com/vinodkrishna221/Q-Trace/tree/main/.agents/skills/phase-planner
Command: npx skills add https://github.com/vinodkrishna221/Q-Trace --skill phase-planner-vinodkrishna221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD and architecture document into work that autonomous coding agents can execute without human clarification is hard; this Skill converts those inputs into per-track phase plans made of self-contained task cards with context, deliverables, tests, and dependencies. ## Core Features & Use Cases - Four-phase spine: Structures every track (fe, be, data, ai, ship) into P0 Skeleton, P1 Core, P2 Integration, and P3 Polish phases. - Agent-executable task cards: Each card carries CONTEXT written for a cold agent session, a DELIVERABLE, a single TEST, DEPENDS/UNBLOCKS links, a DEMO note, and a timebox capped at 4 hours. - Dependency and load management: Emits a cross-track DAG, flags file-surface conflicts between cards, and enforces load limits (70% of builder hours, 50% capacity in the final third). - Use Case: After running /blueprint on a hackathon project, invoke this Skill to produce plans/fe-phase-plan.md and plans/be-phase-plan.md so parallel agents can start work immediately from the repo alone. ## Quick Start Run the phase-planner skill with /phase-plan to turn the PRD and architecture docs into per-track phase plans of task cards.

Frequently Asked Questions about phase-planner

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

FAQPage Schema
How do I turn a PRD into tasks an AI coding agent can execute?

Run the phase-planner after /blueprint to generate per-track phase plans. Each task card includes CONTEXT written for a cold agent session, a DELIVERABLE, a TEST command, and dependency links, so an agent with zero chat history can execute it from the repo alone.

What is the maximum size for a task card in a phase plan?

The maximum timebox is 4 hours; anything bigger must be split until it fits. Cards as small as 30 minutes are legitimate, and the plan should sum to no more than 70% of a builder's realistic hours.

How do parallel frontend and backend tracks avoid blocking each other?

P0 cards are mock-shaped: the frontend builds on contract mocks and the backend returns contract-shaped fakes, so tracks never wait on each other in P0/P1. Swapping mocks for live integrations is an explicit P2 card.

What is QUICK mode in phase planning?

QUICK mode produces one combined plan file covering only P0 and P1 phases with at most 12 cards total. It is intended for smaller scopes where the full four-phase, per-track plan structure is unnecessary.

When should I not use a full four-phase plan?

Skip the full structure for very small efforts where QUICK mode (P0+P1, 12 cards or fewer) suffices. The four-phase spine is designed for multi-track events with parallel builders and a demoable wow moment.