Speckit.plan
Technical Planner - Create plan.md from spec (data model, API contracts, research).From its SKILL.md
npx -y skills add wedabro/bro-skills --skill speckit.planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 252 tokens by cl100k_base, as published. Nobody here has run it
🎯 Mission
Convert spec.md (WHAT) to plan.md (HOW). Use Goal-Backward thinking to ensure your plan leads directly to Success Criteria.
📋 Protocol
Phase 0: Research
- Scan spec → list unknowns ("NEEDS CLARIFICATION").
- Research the solution → write to
research.md.
Phase 1: Data Model
- From entities in spec → create
data-model.md. - Determine relationships (1:N, N:N).
Phase 2: API Contracts
- From User Scenarios → create
contracts/[entity].md.
Phase 3: Architecture
- Create
plan.mdwith: Folder structure, Component hierarchy, State management, Docker topology.
Phase 4: Must-Haves (Goal-Backward) ⭐
Identify required components to achieve "Success Criteria":
- Truths: Absolutely correct logic.
- Artifacts: Key files/outputs.
- Key Links: Links between modules.
Gate Check
- Compare plan vs constitution → REPORT if rules are violated.
🚫 Guard Rails
- DO NOT write code during the planning step.
- MUST check constitutional compliance.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.