kiro-spec-requirements SKILL.md skillA
kiro-spec-requirements from huruikagi/specbind is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add huruikagi/specbind/kiro-spec-requirements@git:20260815.def1c6bPins git:20260815.def1c6b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- huruikagi/specbind
- Path
tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-spec-requirements/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260815.def1c6b, committed Aug 15, 2026
- First version recorded
- Apr 5, 2026
- Size
- 8,532 bytes
- Repository stars
- 2
- License
- MIT
Generate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# kiro-spec-requirements Skill
## Core Mission
- **Success Criteria**:
- Create complete requirements document aligned with steering context
- Follow the project's EARS patterns and constraints for all acceptance criteria
- Focus on core functionality without implementation details
- Make inclusion/exclusion boundaries explicit when scope could otherwise be misread
- Update metadata to track generation status
## Execution Steps
### Step 1: Gather Context
If steering/spec context is already available from conversation, skip redundant file reads.
Otherwise, load all necessary context:
- Read `{{KIRO_DIR}}/specs/{feature}/spec.json` for language and metadata
- Read `{{KIRO_DIR}}/specs/{feature}/brief.md` if it exists (discovery context: problem, approach, scope decisions, boundary candidates)
- Read `{{KIRO_DIR}}/specs/{feature}/requirements.md` for project description
- Core steering context: `product.md`, `tech.md`, `structure.md`
- Additional steering files only when directly relevant to feature scope, user personas, business/domain rules, compliance/security constraints, operational constraints, or existing product boundaries
…Read the whole file at its exact version.
How to install
mdr add huruikagi/specbind/kiro-spec-requirements@sha256:f547109d772cc413The line at the top of this page pins the label git:20260815.def1c6b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_r72fx67jv5mlkbsf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 5, 2026 and Aug 15, 2026, about one every 66 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260815.def1c6b latest | 2026-08-15 | def1c6b | 8,532 B | A | view · diff |
| git:20260405.b18f665 | 2026-04-05 | b18f665 | 7,777 B | A | view · diff |
| git:20260405.8a81ba3 | 2026-04-05 | 8a81ba3 | 9,416 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8532 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
huruikagi/specbind · 2 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r72fx67jv5mlkbsf GET https://markdownregistry.com/api/v1/resolve?ref=huruikagi/specbind/kiro-spec-requirements GET https://markdownregistry.com/api/v1/blob/f547109d772cc41397f993d0f51c1c795ea5d7b49025d60c9120beaffef0f0c1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from huruikagi/specbind
Every file in huruikagi/specbind