npx claudepluginhub dominik-rehse/stdd --plugin stddfeature-name# /stdd:spec — Create Feature Specification Feature: $ARGUMENTS ## Task Create `docs/specs/$ARGUMENTS.md` by asking the user questions. Do not invent answers. Be as detailed as the feature warrants. Include everything an implementor needs to write the code and its tests without guessing. ## Questions to ask (in order) 1. What problem does this solve? Who uses it? 2. What are the inputs and outputs? (types, constraints, examples) 3. What happens normally? What are the edge cases? What errors are possible? 4. How do we know it's done? (each criterion must be independently testable) Stop...
/specStarts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.
/specAuthors structured NLSpec from natural language description using multi-AI research, with adversarial completeness validation, scoring, and saved spec file.
/specGenerates complete feature specifications from a feature name or rough idea, spanning requirements to implementation plan.
/specInitiates phased Spec Mode for a feature description: interactively refines requirements (EARS), designs (Mermaid, TS interfaces), and tasks, generating requirements.md, design.md, tasks.md.
/specGenerates spec docs from feature description: requirements.md (EARS notation), design.md (Mermaid diagrams, TS interfaces), tasks.md (implementation plan).
/specGenerates structured specs from minimal feature description using Kiro method: requirements.md (EARS notation), design.md (Mermaid diagrams, TS interfaces), tasks.md (impl plan).
Feature: $ARGUMENTS
Create docs/specs/$ARGUMENTS.md by asking the user questions. Do not invent answers.
Be as detailed as the feature warrants. Include everything an implementor needs to write
the code and its tests without guessing.
Stop asking once you have enough to fill the template. Do not ask unnecessary questions.
# Spec: $ARGUMENTS
## What
<answer from Q1>
## Inputs / Outputs
<answer from Q2>
## Behavior
- Normal: <from Q3>
- Edge cases: <from Q3>
- Errors: <from Q3>
## Acceptance Criteria
- [ ] <from Q4>
- [ ] <from Q4>
Spec written to docs/specs/$ARGUMENTS.mdRun /stdd:tdd $ARGUMENTS to write tests and implement.