kiro-spec-init SKILL.md skillA
kiro-spec-init 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-init@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-init/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260815.def1c6b, committed Aug 15, 2026
- First version recorded
- Apr 5, 2026
- Size
- 3,192 bytes
- Repository stars
- 2
- License
- MIT
Initialize a new specification with detailed 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
# Spec Initialization
<instructions>
## Core Task
Generate a unique feature name from the project description ($ARGUMENTS) and initialize the specification structure.
## Execution Steps
1. **Check for Brief**: If `{{KIRO_DIR}}/specs/{feature-name}/brief.md` exists (created by `/kiro-discovery`), read it. The brief contains problem, approach, scope, and constraints from the discovery session. Use this to pre-fill the project description and skip clarification questions that the brief already answers.
2. **Clarify Intent**: The Project Description in requirements.md must contain three elements: (a) who has the problem, (b) current situation, (c) what should change. If a brief.md exists and covers these, skip to step 3. Otherwise, ask the user to clarify before proceeding. Ask as many questions as needed; do not fill in gaps with your own assumptions.
3. **Check Uniqueness**: Verify `{{KIRO_DIR}}/specs/` for naming conflicts. If the directory already exists with only `brief.md` (no `spec.json`), use that directory (discovery created it).
4. **Create Directory**: `{{KIRO_DIR}}/specs/[feature-name]/` (skip if already exists from discovery)
5. **Initialize Files Using Templates**:
…Read the whole file at its exact version.
How to install
mdr add huruikagi/specbind/kiro-spec-init@sha256:e31925c7944ea3e9The 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_2mmaskaxysld5c32)
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 | 3,192 B | A | view · diff |
| git:20260405.b18f665 | 2026-04-05 | b18f665 | 3,196 B | A | view · diff |
| git:20260405.c65c43c | 2026-04-05 | c65c43c | 4,068 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 (3192 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_2mmaskaxysld5c32 GET https://markdownregistry.com/api/v1/resolve?ref=huruikagi/specbind/kiro-spec-init GET https://markdownregistry.com/api/v1/blob/e31925c7944ea3e9abf441348632112b83cae16a7603c3bdd13c4f69d43e214a
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