From shazam
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
npx claudepluginhub qhuang20/shazam --plugin shazamThis skill uses the workspace's default tool permissions.
Break a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in `./plans/`.
Breaks approved specs/PRDs into phased vertical slices with durable decisions, HITL/AFK classification, and walking skeleton first. Use when features are too large for one PR.
Turns requirements into structured implementation plans with subtasks, dependencies, file paths, and test scenarios. Use after brainstorming or to formalize clear requirements before coding.
Generates structured phased implementation plans from feature descriptions, sized for 30-50k token sub-agent contexts, with clarifying questions, acceptance criteria, and dependencies. Invoke before multi-phase execution.
Share bugs, ideas, or general feedback.
Break a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in ./plans/.
The PRD should already be in the conversation. If it isn't, ask the user to paste it or point you to the file.
If you have not already explored the codebase, do so to understand the current architecture, existing patterns, and integration layers.
Before slicing, identify high-level decisions that are unlikely to change throughout implementation:
These go in the plan header so every phase can reference them.
Break the PRD into tracer bullet phases. Each phase is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones - Do NOT include specific file names, function names, or implementation details that are likely to change as later phases are built - DO include durable decisions: route paths, schema shapes, data model namesPresent the proposed breakdown as a numbered list. For each phase show:
Ask the user:
Iterate until the user approves the breakdown.
Create ./plans/ if it doesn't exist. Write the plan as a Markdown file named after the feature (e.g. ./plans/user-onboarding.md). Use the template below.
Source PRD:
Durable decisions that apply across all phases:
User stories:
A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
User stories:
...
After the plan is saved, suggest: "Plan ready! Next: /prd-to-issues to turn phases into GitHub Issues, or /grill-me to stress-test the plan first."