Huruikagi

kiro-spec-design

Create comprehensive technical design for a specification

kiro-validate-design

Interactive technical design quality review and validation

kiro-validate-gap

Analyze implementation gap between requirements and existing codebase

Configure or explicitly update SpecBind for a project and complete the resulting aftercare. Use for an explicit SpecBind binary or project-asset update request, initial post-install review, or later changes to Agents, role models, artifact language, project instructions, templates, shared Rules, operational adapters, Steering, or existing artifacts affected by configuration changes.

sb-debug

Use directly when the user asks why a Task failed or cannot be implemented. Establish the root cause, categorize it, and return a next action. Read-only; never starts implementation or applies the fix.

sb-drive

Drive the active milestone through every safe reachable planning, implementation, and validation action. Park branch-local attention and continue elsewhere; stop before release execution.

sb-implement

Implement or resume one roadmap item — executing a Spec's approved task plan through returned review or diagnosis with dispatched implementers and reviewers, or performing and completing a Direct change. Do not use for a diagnosis-only request asking why work failed or cannot be implemented.

sb-plan

Plan active Spec work through Requirements, Design, Contract Review, and Tasks, or run one explicitly requested planning phase for one named Spec. Ordinary planning uses one named Spec or explicit all-Spec scope.

sb-release

Close the active milestone — bind the version, run the project's release procedure, judge whether it worked, and finalize the whole milestone once it did.

sb-review-task

Judge whether one implemented task is done correctly, from the actual diff and the approved requirements, design, and plan.

sb-adopt

Establish Specs from an explicitly selected existing implementation, then retire this temporary adoption Skill after successful finalization.

kiro-spec-requirements

Generate comprehensive requirements for a specification

Data & Documents Listed

kiro-steering-custom

Create custom steering documents for specialized project contexts

kiro-steering

Manage {{KIRO_DIR}}/steering/ as persistent project knowledge

sb-gap-analysis

Compare what a change needs against what the repository already provides, and record the findings worth keeping. Informs the decision; does not make it.

sb-status

Report where a Spec or active milestone is in its lifecycle and what can happen next. Read-only; do not use to judge whether completed implementation is actually done.

sb-steering

Maintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.

sb-validate-design

Independently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.

kiro-spec-tasks

Generate implementation tasks for a specification

sb-discovery

Turn a change request or Source Collection into confirmed Spec and milestone boundaries.

kiro-discovery

Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

kiro-impl

Implement approved tasks using TDD with subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.

kiro-debug

Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.

kiro-review

Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.

kiro-spec-batch

Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel sub-agent dispatch by dependency wave.

kiro-spec-init

Initialize a new specification with detailed project description

kiro-spec-quick

Quick spec generation with interactive or automatic mode

kiro-validate-impl

Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.

kiro-verify-completion

Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.

sb-contract-review

Judge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on.

sb-dev-merge-dependabot

Review and integrate Dependabot pull requests in Huruikagi/specbind one at a time, with current-branch checks, main CI verification, and affected dependency or toolchain validation. Use when asked to handle or merge SpecBind Dependabot PRs; do not use for dependency upgrades that have no Dependabot PR.

sb-dev-forward-test

Run the behavioral forward tests for SpecBind's embedded skills against a fixture project, using subagents with no prior context. Use when a product-managed skill changed materially, before a release, or when a decision's effect on agent behavior needs checking.

sb-dev-resolve-dogfooding

Triage and resolve open dogfooding-labeled Issues in Huruikagi/specbind through contract analysis, product implementation, verification, commit and push, and evidence-backed Issue disposition. Use when asked to work through SpecBind dogfooding findings; do not use for general Issue triage.

sb-dev-sync-docs

Keep SpecBind's English and Japanese public documentation aligned and the Japanese copy natural and readable. Use for changes or language-quality reviews under docs/en or docs/ja, bilingual navigation, or public documentation URLs; exclude English-only generated reference pages and internal repository documentation.

kiro-spec-status

Show specification status and progress