Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-tech-spec
Quick Flow lightweight technical specification for small-scope work (1-15 stories). Replaces the full PRD + architecture pair when scope is small and requirements are clear. Produces bmad-output/tech-spec.md as the single planning artifact before story creation.
Passed 13 of 18 test cases with the skill, and 4 of 18 without it.
and 14 more in the full report
12 fixed5 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
This skill produces a focused tech-spec.md for Quick Flow work: small, well-scoped
features or changes that sit in the 1-15 story range. It consolidates the product
rationale, technical approach, and story backlog into a single lightweight document,
skipping the separate PRD + architecture artifacts that larger tracks require.
Track guidance
- 1-15 stories, single team, clear requirements → Quick Flow (this skill)
- 10-50+ stories, multiple concerns, or uncertain scope → use bmad-prd then bmad-architecture
- 30+ stories, cross-org, security/compliance/DevOps dimensions → Enterprise track
Ask the user (or infer from context) which of three intents applies:
| Intent | When |
|---|---|
| Create | No tech-spec.md exists yet |
| Update | Revising scope, requirements, or approach in an existing spec |
| Validate | Checking a draft spec for BMAD completeness before moving to stories |
For Create, collect (interactively or from existing project files):
bmad-output/decision-log.mdLoad bmad-output/project-context.md if present — it is the project constitution and must
test cases passed, vs 4 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.