by juanandresgs
JAGS' batteries-included Claude Code SDLC config.
# Add to your Claude Code skills
git clone https://github.com/juanandresgs/claude-systemA batteries-included governance layer for Claude Code. Four specialized agents handle planning, implementation, verification, and git operations. Shell scripts enforce the rules at every lifecycle event, regardless of context window pressure.
Instructions guide. Hooks enforce.
~/.claude/
├── hooks/ # Hook scripts and shared libraries
├── agents/ # 4 agent definitions (Planner, Implementer, Tester, Guardian)
├── skills/ # 11 skills across 3 domains
├── commands/ # Slash commands (/compact, /backlog)
├── scripts/ # 7 utility scripts + lib/
├── observatory/ # Self-improving trace analysis
├── traces/ # Agent execution archive
├── tests/ # Hook validation suite
├── ARCHITECTURE.md # Definitive technical reference (18 sections)
├── CLAUDE.md # Session instructions (loaded every time)
└── settings.json # Hook registration + model config
Default Claude Code — you describe a feature and:
idea → code → commit → push → discover the mess
The model writes on main, skips tests, force-pushes, and forgets the plan once the context window fills up. Every session is a coin flip.
No comments yet. Be the first to share your thoughts!
With this system — the same feature request triggers a self-correcting pipeline:
┌─────────────────────────────────────────┐
│ You describe a feature │
└──────────────────┬──────────────────────┘
▼
┌──────────────────────────────────────────┐
│ Planner agent: │
│ 1a. Problem decomposition (evidence) │
│ 1b. User requirements (P0/P1/P2) │
│ 1c. Success metrics │
│ 2. Research gate → architecture │
│ → MASTER_PLAN.md + GitHub Issues │
└──────────────────┬───────────────────────┘
▼
┌──────────────────────────────────────────┐
│ Guardian agent creates isolated worktree │
└──────────────────┬───────────────────────┘
▼
┌────────────────────────────────────────────────┐
...