spec-to-plan
Turn a PRD into an Implementation Plan
This skill translates what needs to be built (the PRD) into how it will be built (a phased implementation plan). It breaks the PRD into tracer-bullet vertical slices, orders them into phases, and writes the result as a Markdown plan file in ./plans/.
When to Use
Use this skill when:
- You already have a PRD or equivalent spec and now need a concrete implementation plan.
- You want to think in phases, not just issues: what gets built first, what can be deferred, and how slices build on each other.
- You intend to drive downstream work (e.g.
/slice-the-spec,/incremental-tdd) from a single, durable planning document.
If the requirements are still fuzzy, use /grill-me and /spec-writer first.
Workflow
You can compress steps if the context is already clear, but keep the core structure: PRD → slices → phases → plan file.
- Confirm the PRD is in context
More from kambleakash0/agent-skills
english-humanizer
Detects and removes AI-generated writing patterns from English text. Rewrites content to sound natural, authentic, and genuinely human.
40grill-master
Relentlessly interview the user when they want to learn about a topic, plan, or design until you both reach a shared, testable understanding, before any planning or implementation.
15spec-writer
Create a comprehensive Product Requirements Document from conversation and repo context. Use when the user wants a PRD, product spec, feature requirements, or similar documentation.
13slice-the-spec
Turn a PRD into a Kanban-ready backlog of vertically sliced issues, with clear dependencies and HITL/AFK flags.
13git-workflow
>
13incremental-tdd
Test-driven development with a strict red-green-refactor loop, vertical slices, and deep modules. Use to build features or fix bugs using TDD.
13