~ / rigs / Codoop / codoop-flow

Codoop/codoop-flow

Turn "AI writes code" into a ticket pipeline with guardrails: product design → ticket design → agent-driven implementation with deterministic verification.

↗ GitHub ★ 5 MIT updated 9d ago project Claude Code Claude plugin
stack: Python
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~891 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 Codoop/codoop-flow/skills ./rig-codoop-flow/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 Codoop/codoop-flow/skills/codoop-discover .claude/skills/codoop-discover
$ npx degit Codoop/codoop-flow/skills/codoop-execute .claude/skills/codoop-execute
$ npx degit Codoop/codoop-flow/skills/codoop-init .claude/skills/codoop-init
$ npx degit Codoop/codoop-flow/skills/codoop-ticket .claude/skills/codoop-ticket
$ npx degit Codoop/codoop-flow/skills/codoop-ux-walkthrough .claude/skills/codoop-ux-walkthrough
$ npx degit Codoop/codoop-flow/skills/debugging-and-error-recovery .claude/skills/debugging-and-error-recovery
$ npx degit Codoop/codoop-flow/skills/definition-of-done .claude/skills/definition-of-done
$ npx degit Codoop/codoop-flow/skills/grilling .claude/skills/grilling
$ npx degit Codoop/codoop-flow/skills/incremental-implementation .claude/skills/incremental-implementation
$ npx degit Codoop/codoop-flow/skills/planning-and-task-breakdown .claude/skills/planning-and-task-breakdown
$ npx degit Codoop/codoop-flow/skills/spec-driven-development .claude/skills/spec-driven-development
$ npx degit Codoop/codoop-flow/skills/test-driven-development .claude/skills/test-driven-development

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 (12)

Similar rigs

copied ✓