Break feature specifications into phased implementation plans with self-contained files.
npx skills add https://github.com/robertdp/claude-code-skills --skill phase-robertdp
Please help me install this Agent Skill. Skill: phase Source: https://github.com/robertdp/claude-code-skills/tree/main/skills/phase Command: npx skills add https://github.com/robertdp/claude-code-skills --skill phase-robertdp
This Skill helps you break a feature spec or requirement set into a structured, phased implementation plan that agents can execute with minimal context. It is designed to reduce ambiguity, prevent scope creep, and make complex work easier to hand off across sessions.
Ask the phase skill to decompose a spec file into a phased implementation plan.
High-intent search queries and answers about installing and using this skill.
To break a feature specification into a phased implementation plan, you decompose the spec into self-contained files for minimal-context execution. This produces a master plan, sequential phase instructions, and state tracking for agent handoff.
Decomposing requirements for agent handoff involves generating a master plan and sequential phase instructions with state tracking. This structured decomposition prevents scope creep and makes complex work easier to hand off across sessions.
You map requirements to implementation phases for coverage tracking by critiquing the plan for blocking issues and tracking state across sequential files. This ensures every requirement maps to a phase before a finalize step handles verification.
Yes, you can use phased execution plans for repository-aware work without a complete spec. The system interviews the user to gather missing requirements and inspects the repository to identify affected files before decomposing the work.
Codebase-aware planning for file-by-file decomposition works by inspecting the repository to identify affected files, patterns, and test infrastructure. It then generates self-contained phase files so each phase can be implemented independently with minimal context.
A limitation of minimal-context execution for complex feature implementation is that each phase operates independently, meaning inter-phase dependencies must be strictly managed through state tracking to prevent execution failures during agent handoff.
BRANDNEWSHVTMap directory structure and trace data flows across codebase modules.
hksloverIdentify the current workflow phase and select the next continuation step.
T-ravAudit integration test coverage across modules for gaps and anti-patterns.
gotalabTransforms Notion spec documents into actionable implementation plans and tasks with progress tracking.
