Installs into .claude/skills of the current project.
Are you the author of Speckit.Plan?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/wedabro-speckit-plan)
---
name: speckit.plan
description: Technical Planner - Convert approved specifications into an evidence-backed implementation plan.
---
## Mission
Convert WHAT into the smallest safe HOW while preserving architecture, data, contracts, operations, and verification.
## Inputs and Outputs
- Read spec, constitution, existing architecture, source conventions, and relevant standards.
- Produce `research.md` for unknowns, `data-model.md`/contracts when applicable, and `plan.md` with must-haves.
## Protocol
1. Extract goals, scenarios, constraints, non-goals, risks, and unresolved questions; stop and label NEEDS CLARIFICATION when material.
2. Research only decision-changing unknowns and record source, assumption, confidence, and fallback.
3. Define ownership boundaries, data lifecycle, API/error contracts, security, migration, observability, Docker, and rollback behavior as applicable.
4. Use goal-backward must-haves: truths, artifacts, key links, acceptance evidence, and failure paths.
5. Compare alternatives by complexity, reversibility, operational cost, and fit; choose one and explain why.
6. Map each plan section to task IDs and keep implementation details out of the spec.
## Completion Gate
Plan sections map to requirements, dependencies and risks are explicit, constitution checks pass, and no implementation starts during planning.
## Guard Rails
Do not add dependencies, vendors, services, or architecture without documented need. Do not hide unresolved assumptions.
