Agent skill · product strategy · 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. Use when the user says: "write a tech spec", "create a technical specification", "I need a tech spec for this feature", "quick spec", "small project spec", "we don't need a full PRD", "just a tech spec", "spec out this change", "document this feature". QUICK FLOW TRACK ONLY (1-15 stories). If scope grows beyond ~15 stories or involves multiple teams / external integrations at scale, stop and redirect to bmad-prd + bmad-architecture instead — those skills are built for that complexity. Supports three intents: Create (new spec), Update (revise an existing tech-spec.md), Validate (review a draft for completeness against BMAD criteria).
Why this skill is useful
Adds a structured template and process for creating lightweight technical specifications that streamline project planning and documentation.
What it needs
About 4k tokens when loaded. Last updated 2026-06-20. 471 stars on the source repository.
What this skill does
BMAD Tech Spec — Quick Flow 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 --- Workflow Step 1 — Identify intent 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 Step 2 — Gather context For Create, collect (interactively or from existing project files): 1. Problem & solution — what are we solving and how? 2. Scope — what is in scope? What is explicitly out of scope? 3. Functional requirements — numbered, MoSCoW-tagged (MUST / SHOULD / COULD) 4. Non-functional requirements — performance, security, accessibility targets that are relevant; omit boilerplate that does not apply 5. Technical approach — stack, key components, data model sketch, API surface (if any) 6. Story list — high-level backlog items; the scrum-master skill will compile them into full story files 7. Dependencies & risks — third-party libs, external services, known unknowns 8. Decision log entries — any choices made during this conversation that belong in bmad-output/decision-log.md Load bmad-output/project-context.md if present — it is the project constitution and must not be contradicted without a recorded decision. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/bmad-tech-spec