~ / rigs / JanSzewczyk / spec-driven-development

JanSzewczyk/spec-driven-development

Spec-Driven Development framework for Claude Code — slash commands take a feature from spec through clarify, plan and tasks, hand each self-contained task to your own implementation flow, and verify the result against the acceptance criteri

↗ GitHub ★ 0 MIT updated 2d ago project Claude Code Claude plugin
stack: TypeScript
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~3.8k tokens
Moderate · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

Copy this rig

$ git clone --depth 1 https://github.com/JanSzewczyk/spec-driven-development

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 JanSzewczyk/spec-driven-development/plugins/sdd/skills/analyze .claude/skills/analyze
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/capabilities .claude/skills/capabilities
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/clarify .claude/skills/clarify
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/constitution .claude/skills/constitution
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/doctor .claude/skills/doctor
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/implement .claude/skills/implement
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/plan .claude/skills/plan
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/retro .claude/skills/retro
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/review .claude/skills/review
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/spec .claude/skills/spec
$ npx degit JanSzewczyk/spec-driven-development/plugins/sdd/skills/tasks .claude/skills/tasks

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Skills (11)

Similar rigs

copied ✓