Get started · ~5 minutes
specmaster is a Claude Code skill. It runs inside Claude Code and writes your PRD + spec as Markdown files you download.
Clone it straight into your Claude Code skills directory:
git clone https://github.com/dubedad/specmaster ~/.claude/skills/specmaster
Then restart Claude Code (or open a new session) so it registers the skill.
In any project, start the skill:
/specmaster
It asks one question — which lane:
Then it interviews you briefly — only for intent (the problem, who it's for, scope, the outcomes). Everything else it generates. Prefer to pre-write the kickoff? Use the configurator →
specmaster generates the full spec, validates it (quality + traceability + anti-vagueness), and shows you the PRD with a score and any findings. Review, then approve. It won't present a stale validation — if the spec changed, it re-validates first.
Everything lands in one run folder as Markdown:
specs/<your-project>-<M|I>-<date>/ ├─ PRD.md ← your spec (download this) ├─ requirements.ears.md ← testable requirements ├─ acceptance/*.feature ← Gherkin "done" criteria ├─ artifacts/ ← workflow, UX, UI, data model, logic model, ADRs ├─ VALIDATION.md └─ MANIFEST.md
Open the folder, download PRD.md (and anything else you need). It's plain Markdown — read it, share it, or hand it to a build agent.
The requirements.ears.md + acceptance/*.feature are a build contract. Hand them to any coding agent, or if you use the GSD toolchain:
ultraplan # turn the spec into a plan # or: /gsd-plan-phase --prd PRD.md goal # build until the Gherkin scenarios pass
ba-*, pump-*, dama-*, gsd-*, bpmn-from-website, or prd-authoring installed, specmaster uses them as accelerators — otherwise it uses its inline method.