~ / rigs / arjay07 / spec-mode-claude-code

arjay07/spec-mode-claude-code

Structured spec-driven development workflow for Claude Code (similar to Kiro IDE) with phase-gated requirements, design, and implementation

↗ GitHub ★ 1 no license updated 12mo ago project Claude Code
field: unknown workflow: Planning & specsFrontend & design
share on X
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
CONTEXT TAX · EVERY TURN
~326 tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit arjay07/spec-mode-claude-code/agents ./rig-spec-mode-claude-code/agents
$ npx degit arjay07/spec-mode-claude-code/commands ./rig-spec-mode-claude-code/commands

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.

$ curl -fsSL --create-dirs -o .claude/agents/spec-design.md https://raw.githubusercontent.com/arjay07/spec-mode-claude-code/main/agents/spec-design.md
$ curl -fsSL --create-dirs -o .claude/agents/spec-executor.md https://raw.githubusercontent.com/arjay07/spec-mode-claude-code/main/agents/spec-executor.md
$ curl -fsSL --create-dirs -o .claude/agents/spec-requirements.md https://raw.githubusercontent.com/arjay07/spec-mode-claude-code/main/agents/spec-requirements.md
$ curl -fsSL --create-dirs -o .claude/agents/spec-tasks.md https://raw.githubusercontent.com/arjay07/spec-mode-claude-code/main/agents/spec-tasks.md

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 *)"
    ]
  }
}

Subagents (4)

spec-design
model: sonnet
Use this agent to create a technical design document based on existing requirements. REQUIRES requirements.md to exist first. Creates design.md with architecture, data structures, and implementation d
spec-executor
model: opus
Use this agent to execute a specific task from a spec's tasks.md file. Specify the spec name and task number. The agent reads the requirements, design, and tasks, implements the specified task, then m
spec-requirements
model: sonnet
Use this agent to create requirements and user stories for a new feature. The agent gathers requirements through questions and produces a structured requirements.md file in .claude/specs/<spec-name>/.
spec-tasks
model: sonnet
Use this agent to create an implementation task checklist from a design document. REQUIRES design.md to exist first. Creates tasks.md with numbered, sequential tasks that can be executed one-by-one. U

Slash commands (2)

/spec-exec/spec-mode

Similar rigs

copied ✓