~ / rigs / petruseugene / full-development-cycle

petruseugene/full-development-cycle

dev-cycle: a Claude Code plugin that drives a feature from interview to merged PR with parallel subagents, review gates and a dashboard

↗ GitHub ★ 2 MIT updated 21d ago project Claude Code Claude plugin
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~987 tokens
Featherweight · 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/petruseugene/full-development-cycle

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 petruseugene/full-development-cycle/plugin/skills/architector .claude/skills/architector
$ npx degit petruseugene/full-development-cycle/plugin/skills/auto-tester .claude/skills/auto-tester
$ npx degit petruseugene/full-development-cycle/plugin/skills/backend-dev .claude/skills/backend-dev
$ npx degit petruseugene/full-development-cycle/plugin/skills/cli-fallback .claude/skills/cli-fallback
$ npx degit petruseugene/full-development-cycle/plugin/skills/code-reviewer .claude/skills/code-reviewer
$ npx degit petruseugene/full-development-cycle/plugin/skills/discovery .claude/skills/discovery
$ npx degit petruseugene/full-development-cycle/plugin/skills/frontend-dev .claude/skills/frontend-dev
$ npx degit petruseugene/full-development-cycle/plugin/skills/orchestrator .claude/skills/orchestrator
$ npx degit petruseugene/full-development-cycle/plugin/skills/plan-writer .claude/skills/plan-writer
$ npx degit petruseugene/full-development-cycle/plugin/skills/playbook .claude/skills/playbook
$ npx degit petruseugene/full-development-cycle/plugin/skills/security-reviewer .claude/skills/security-reviewer
$ npx degit petruseugene/full-development-cycle/plugin/skills/spec-writer .claude/skills/spec-writer
$ npx degit petruseugene/full-development-cycle/plugin/skills/using-dev-cycle .claude/skills/using-dev-cycle
$ npx degit petruseugene/full-development-cycle/plugin/skills/visual-tester .claude/skills/visual-tester
$ npx degit petruseugene/full-development-cycle/plugin/skills/wireframer .claude/skills/wireframer

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

Similar rigs

copied ✓