spec-to-plan

Converts a PRD into a phased implementation plan using tracer-bullet vertical slices.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/BING0116-gif/math-AI-assistant --skill spec-to-plan-bing0116-gif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-to-plan
Source: https://github.com/BING0116-gif/math-AI-assistant/tree/main/.agents/skills/spec-to-plan
Command: npx skills add https://github.com/BING0116-gif/math-AI-assistant --skill spec-to-plan-bing0116-gif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished PRD into an actionable engineering plan is hard: teams either jump straight into coding without structure or produce plans that are too coarse to execute. This Skill bridges that gap by translating requirements into ordered, end-to-end vertical slices grouped into phases. ## Core Features & Use Cases - Tracer-Bullet Slicing: Breaks a PRD into thin, end-to-end vertical slices that cut through schema, domain, API, and UI layers, each independently demoable. - Phase Ordering by Risk and Value: Groups slices into 2-5 phases so the riskiest assumptions are validated first and something demoable ships early. - Durable Plan Document: Writes a Markdown plan file to ./plans/ capturing architectural decisions (routes, schema, models, auth) plus per-phase acceptance criteria. - Use Case: After finalizing a PRD for a weekly admin summary email feature, run this Skill to produce ./plans/weekly-admin-summary-email.md with three phases, each with acceptance criteria ready to hand to an engineer or execution skill like /tdd. ## Quick Start Ask the AI to turn the PRD in the current conversation into a phased implementation plan using tracer-bullet vertical slices and write it to the plans directory.

Frequently Asked Questions about spec-to-plan

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

FAQPage Schema
How do I turn a PRD into an implementation plan?▼

Provide the PRD in the conversation or point to its file path, then invoke the skill. It identifies durable architectural decisions, drafts tracer-bullet vertical slices, groups them into 2-5 phases, and writes a Markdown plan file to ./plans/.

What is a tracer-bullet vertical slice in software planning?▼

A tracer-bullet slice is a thin, end-to-end piece of functionality that cuts through all relevant layers such as schema, domain, API, and UI. Each slice is independently demoable, and many thin slices are preferred over a few thick ones.

When should I use spec-to-plan versus writing tasks directly?▼

Use it when you have a finalized PRD and need phased planning before execution. If requirements are still fuzzy, clarify them first with requirement-gathering steps; detailed implementation belongs to downstream execution skills like /tdd.

Does the plan include specific file names and function signatures?▼

No. The plan deliberately excludes brittle implementation details like file names and function signatures. It records only durable decisions such as route paths, schema shapes, model names, and authentication approach.

Where is the generated implementation plan saved?▼

The plan is written as a Markdown file in the ./plans/ directory, named after the feature, for example ./plans/weekly-admin-summary-email.md. The directory is created automatically if it does not exist.