Borrowing it
Nothing to install: this file belongs to reinhardhq/claude-code-spec-boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/reinhardhq/claude-code-spec-boilerplate/main/.claude/commands/kiro:spec-design.mdgit clone --depth 1 https://github.com/reinhardhq/claude-code-spec-boilerplateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-design)<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-design"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-design"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00006 | $0.02968 |
| Opus 5 | $0.00003 | $0.01484 |
| Sonnet 5 | $0.00001 | $0.00594 |
| Haiku 4.5 | $0.00001 | $0.00297 |
Grade A, and why
kiro:spec-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Design
Create comprehensive technical design for feature: $ARGUMENTS
Interactive Approval: Requirements Review
CRITICAL: Design can only be generated after requirements are reviewed and approved.
Requirements Review Process
- Requirements document: @.kiro/specs/$ARGUMENTS/requirements.md
- Spec metadata: @.kiro/specs/$ARGUMENTS/spec.json
Interactive Approval Process:
- Check if requirements exist - Verify that requirements.md has been generated
- Prompt for human review - Ask user: "requirements.mdをレビューしましたか？ [y/N]"
- If 'y' (yes): Automatically update spec.json to approve requirements and proceed with design generation
- If 'N' (no): Stop execution and instruct user to review requirements.md first
Auto-approval update in spec.json when user confirms review:
{
"approvals": {
"requirements": {
"generated": true,
"approved": true // ← Automatically set to true when user confirms
}
},
"phase": "requirements-approved"
}
User Interaction Example:
📋 Requirements review required before generating design.
📄 Please review: .kiro/specs/feature-name/requirements.md
❓ requirements.mdをレビューしましたか？ [y/N]: y
✅ Requirements approved automatically. Proceeding with design generation...
Context Analysis
Requirements Foundation
CRITICAL: Design must be built upon approved requirements document.
- Requirements document: @.kiro/specs/$ARGUMENTS/requirements.md
- EARS format requirements: Each requirement with acceptance criteria
- User stories mapping: Design components must address specific user stories
- Constraints and acceptance criteria: Must be reflected in technical decisions
Verification Required: Ensure requirements.md exists and is approved before proceeding.
Steering Context
- Current architecture: @.kiro/steering/structure.md
- Technology stack: @.kiro/steering/tech.md
- Product constraints: @.kiro/steering/product.md
Current Spec Context
- Current design: @.kiro/specs/$ARGUMENTS/design.md
- Spec metadata: @.kiro/specs/$ARGUMENTS/spec.json
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 403 lines · 6 tokens per session scan A 2f08bcbe137d
kiro:spec-design is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It adds 6 tokens to every session and 2,968 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.