~ / rigs / licorsy / ai-assisted-sdd-template

licorsy/ai-assisted-sdd-template

AI-assisted, Spec-Driven Development template — governance, roadmap, and agent workflows for Claude Code

↗ GitHub ★ 0 MIT-0 updated 2mo ago project Claude CodeCodex
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~2.1k tokens
Moderate · median rig: 2.3k · breakdown
GUARDRAILS
1/5
No YOLO mode · details

Copy this rig

# review before running: this installs third-party code
$ npx degit licorsy/ai-assisted-sdd-template/.claude ./rig-ai-assisted-sdd-template  # inspect, then merge into .claude/

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/adversarial-reviewer.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/.claude/agents/adversarial-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/doc-consistency-reviewer.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/.claude/agents/doc-consistency-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/orchestrator-reviewer.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/.claude/agents/orchestrator-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/tool-hunter.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/.claude/agents/tool-hunter.md
$ curl -fsSL --create-dirs -o .claude/agents/adversarial.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/agents/adversarial.md
$ curl -fsSL --create-dirs -o .claude/agents/doc-consistency.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/agents/doc-consistency.md
$ curl -fsSL --create-dirs -o .claude/agents/init.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/agents/init.md
$ curl -fsSL --create-dirs -o .claude/agents/orchestrator.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/agents/orchestrator.md
$ curl -fsSL --create-dirs -o .claude/agents/phase-reviewer.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/agents/phase-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/tool-discovery.md https://raw.githubusercontent.com/licorsy/ai-assisted-sdd-template/main/agents/tool-discovery.md

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

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

Subagents (10)

adversarial-reviewer
model: opus
Stress-tests the merit of a spec or plan before implementation locks in - fragile assumptions, error states, persistent data, external contracts, new dependencies. Use before closing Phase 3 - Designi
doc-consistency-reviewer
model: opus
Audits the entire current living-document set (not one phase) for cross-document semantic inconsistency, broken traceability, redundancy, and ambiguity - including status-vs-body drift. Use on demand,
orchestrator-reviewer
model: opus
Independently reviews a completed roadmap phase's Acceptance Criteria/Done, Expected Result, and Generated Artifacts against docs/strategy/roadmap.md. Use proactively before closing Phase 3 - Designin
tool-hunter
model: opus
Searches for existing, vetted solutions before something gets built from scratch, in one of two modes — (a) Claude Code tools (Agents, Skills, Hooks, MCP servers, Commands) that could help produce a r
adversarialStress-test the merit of a spec or plan before implementation locks in: interrogate assumptions, error states, persistent data, external contracts, and new dependencies, and output numbered findings w
doc-consistencyAudit the entire current living-document set - not one phase - for cross-document semantic inconsistency, broken traceability, unnecessary redundancy, and textual ambiguity, using directed search over
initIdempotent project bootstrap for a repository created from this template: detect greenfield vs. brownfield and confirm with the human, scaffold only the missing Phase 0 artifacts (status, ADR template
orchestratorOrchestrate the creation and evolution of a software product or platform as a generic AI-assisted development system, with human-in-the-loop control, living documentation, persistent memory, path sele
phase-reviewerIndependently review, test, and validate a completed roadmap phase's Acceptance Criteria / Done, Expected Result, and Generated Artifacts against the business software development roadmap, without reu
tool-discoveryTwo-mode prior-art search before building from scratch: Mode A finds Claude Code tools (Agents, Skills, Hooks, MCP servers, Commands) for the catalog, Mode B finds product frameworks/libraries/service

Slash commands (2)

/orchestrator/template-init

Plugins (2)

git-governance@git-governancedocs-governance@docs-governance

Similar rigs

copied ✓