Borrowing it
Nothing to install: this file belongs to j5ik2o/okite-ai. 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/j5ik2o/okite-ai/main/.claude/commands/kiro/spec-design.mdgit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/j5ik2o/okite-ai/spec-design)<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/spec-design"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/spec-design.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.00007 | $0.01878 |
| Opus 5 | $0.00003 | $0.00939 |
| Sonnet 5 | $0.00001 | $0.00376 |
| Haiku 4.5 | $0.00001 | $0.00188 |
Grade A, and why
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 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.
This is a copy
92% identical to kiro-spec-design — 73 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Design Generator
<background_information>
- Mission: Generate comprehensive technical design document that translates requirements (WHAT) into architectural design (HOW)
- Success Criteria:
- All requirements mapped to technical components with clear interfaces
- Appropriate architecture discovery and research completed
- Design aligns with steering context and existing patterns
- Visual diagrams included for complex architectures </background_information>
Execution Steps
Step 1: Load Context
Read all necessary context:
.kiro/specs/$1/spec.json,requirements.md,design.md(if exists)- Entire
.kiro/steering/directory for complete project memory .kiro/settings/templates/specs/design.mdfor document structure.kiro/settings/rules/design-principles.mdfor design principles.kiro/settings/templates/specs/research.mdfor discovery log structure
Validate requirements approval:
- If
-yflag provided ($2 == "-y"): Auto-approve requirements in spec.json - Otherwise: Verify approval status (stop if unapproved, see Safety & Fallback)
Step 2: Discovery & Analysis
Critical: This phase ensures design is based on complete, accurate information.
-
Classify Feature Type:
- New Feature (greenfield) → Full discovery required
- Extension (existing system) → Integration-focused discovery
- Simple Addition (CRUD/UI) → Minimal or no discovery
- Complex Integration → Comprehensive analysis required
-
Execute Appropriate Discovery Process:
For Complex/New Features:
- Read and execute
.kiro/settings/rules/design-discovery-full.md - Conduct thorough research using WebSearch/WebFetch:
- Latest architectural patterns and best practices
- External dependency verification (APIs, libraries, versions, compatibility)
- Official documentation, migration guides, known issues
- Performance benchmarks and security considerations
- Read and execute
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 · 180 lines · 7 tokens per session scan A 844f5e2714da
spec-design is a command published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 1,878 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to kiro-spec-design, differing in 73 lines, and is treated as a copy.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.