Borrowing it
Nothing to install: this file belongs to kaze-jp/kusa. 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/kaze-jp/kusa/main/.claude/commands/kiro/spec-requirements.mdgit clone --depth 1 https://github.com/kaze-jp/kusaWrote 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/kaze-jp/kusa/spec-requirements)<a href="https://agentmods.dev/commands/kaze-jp/kusa/spec-requirements"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/spec-requirements.svg" alt="Measured on agentmods" 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.00000 | $0.00530 |
| Opus 5 | $0.00000 | $0.00265 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
spec-requirements 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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expand Requirements
Expand initial requirements into a full, structured requirements document using EARS format.
Usage
/kiro:spec-requirements <feature-name>
Instructions
-
Read the initial requirements from
.kiro/specs/$FEATURE_NAME/requirements-init.md. If it does not exist, instruct the user to run/kiro:spec-initfirst. -
Read steering documents for additional context:
.ao/steering/product.mdfor product goals.ao/steering/tech.mdfor technical constraints.ao/steering/structure.mdfor codebase conventions
-
Expand each initial requirement by:
- Breaking compound requirements into atomic statements
- Adding missing edge cases and error scenarios
- Ensuring each requirement is testable and measurable
- Applying the correct EARS pattern for each requirement type
-
Apply EARS format rules strictly:
- Every requirement MUST follow one of the five EARS patterns
- No ambiguous language (avoid "should", "may", "might")
- Each requirement must be independently verifiable
- Requirements must not describe implementation details
-
Generate
requirements.mdwith this structure:
# Requirements: <feature-name>
## Document Info
- Feature: <name>
- Status: Draft
- Created: <date>
## Functional Requirements
### Core Behavior
FR-001: <EARS formatted requirement>
FR-002: ...
### User Interactions
FR-010: ...
### Edge Cases
FR-020: ...
### Error Handling
FR-030: ...
## Non-Functional Requirements
### Performance
NFR-001: ...
### Security
NFR-010: ...
### Accessibility
NFR-020: ...
## Acceptance Criteria
<High-level acceptance criteria for the feature>
## Traceability
<Map from requirements-init items to expanded requirements>
-
Validate completeness: Ensure every item from
requirements-init.mdis addressed in the expanded document. -
Report the output path and suggest
/kiro:spec-designas the next step.
Output
.kiro/specs/<feature-name>/requirements.md
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.
- 6d ago First seen · 88 lines · 0 tokens per session scan A b0739a739a14
spec-requirements is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 530 tokens. 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.