~ / rigs / sohampatwardhan / kiro-sdd-skills

sohampatwardhan/kiro-sdd-skills

Agent skills for Kiro-style spec-driven development (SDD)

↗ GitHub ★ 0 MIT updated 17d ago collection Kiro
stack: JavaScript
share on X
ARCHETYPE
Automator
Hooks on every lifecycle event: format, lint, notify, log.
CONTEXT TAX · EVERY TURN
~1.3k tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
1/5
Pre-tool screening hook · details
Quality 0/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit sohampatwardhan/kiro-sdd-skills/skills ./rig-kiro-sdd-skills/skills

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit sohampatwardhan/kiro-sdd-skills/skills/kiro-design .claude/skills/kiro-design
$ npx degit sohampatwardhan/kiro-sdd-skills/skills/kiro-hooks .claude/skills/kiro-hooks
$ npx degit sohampatwardhan/kiro-sdd-skills/skills/kiro-mermaid .claude/skills/kiro-mermaid
$ npx degit sohampatwardhan/kiro-sdd-skills/skills/kiro-requirements .claude/skills/kiro-requirements
$ npx degit sohampatwardhan/kiro-sdd-skills/skills/kiro-sdd .claude/skills/kiro-sdd
$ npx degit sohampatwardhan/kiro-sdd-skills/skills/kiro-steering .claude/skills/kiro-steering
$ npx degit sohampatwardhan/kiro-sdd-skills/skills/kiro-tasks .claude/skills/kiro-tasks

Merge into .claude/settings.json (project) or ~/.claude/settings.json (user). Hook commands reference scripts in the source repo — copy those too.

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "write",
        "hooks": [
          {
            "type": "command",
            "command": "node scripts/hooks/guard-env-writes.mjs"
          }
        ]
      }
    ]
  }
}

Skills (7)

Hooks (5)

eventmatcherruns
PreToolUsewritenode scripts/hooks/guard-env-writes.mjs
PostFileSave\.(ts|tsx)$npx eslint --fix {{filePath}}
UserPromptSubmit*If this session is implementing Shelf Club, read .kiro/specs/reading-queue/requirements.md, design.md, and tasks.md before editing. Implement only the numbered task the user named.
PreTaskExec*Before this task, open the _Requirements_ ids on the task and the matching criteria in requirements.md or bugfix.md. Do not start a different task.
PostTaskExec*List each requirement id for the task you just finished and say whether the code satisfies it. Do not check the box for a criterion that is still missing. Stop.

Kiro (6 steering · 2 specs · 4 hook files)

Specs: duplicate-title-match, reading-queue (loaded on demand, not counted in context tax)

How Kiro files are scored: methodology.

Similar rigs

copied ✓