my-claude

English | 한국어 | 日本語 | 中文 | Deutsch | Français

Looking for Codex CLI? → my-codex — same orchestration in native TOML format

---

---

Installation

For Humans

git clone --depth 1 https://github.com/sehoon787/my-claude.git /tmp/my-claude
bash /tmp/my-claude/install.sh
rm -rf /tmp/my-claude

Or install as a Claude Code plugin first, then run the companion installer:

# Inside a Claude Code session:
/plugin marketplace add sehoon787/my-claude
/plugin install my-claude@my-claude

# Then install companion tools:
git clone --depth 1 https://github.com/sehoon787/my-claude.git /tmp/my-claude
bash /tmp/my-claude/install.sh
rm -rf /tmp/my-claude

For AI Agents

Read https://raw.githubusercontent.com/sehoon787/my-claude/main/AI-INSTALL.md and follow every step.

---

How Boss Works

Boss is the meta-orchestrator at the core of my-claude. It never writes code — it discovers, classifies, matches, delegates, and verifies.

User Request
     │
     ▼
┌─────────────────────────────────────────────┐
│  Phase 0 · DISCOVERY                        │
│  Scan agents, skills, MCP, hooks at runtime │
│  → Build live capability registry           │
└──────────────────────┬──────────────────────┘
                       ▼
┌─────────────────────────────────────────────┐
│  Phase 1 · INTENT GATE                      │
│  Classify: trivial | build | refactor |     │
│  mid-sized | architecture | research | ...  │
│  → Counter-propose skill if better fit      │
└──────────────────────┬──────────────────────┘
                       ▼
┌─────────────────────────────────────────────┐
│  Phase 2 · CAPABILITY MATCHING              │
│  P0: gstack skill (if installed)            │
│  P1: Exact skill match                      │
│  P2: Specialist agent (200+)               │
│  P3: Multi-agent orchestration              │
│  P4: General-purpose fallback               │
└──────────────────────┬──────────────────────┘
                       ▼
┌─────────────────────────────────────────────┐
│  Phase 3 · DELEGATION                       │
│  6-section structured prompt to specialist  │
│  TASK / OUTCOME / TOOLS / DO / DON'T / CTX  │
└──────────────────────┬──────────────────────┘
                       ▼
┌─────────────────────────────────────────────┐
│  Phase 4 · VERIFICATION                     │
│  Read changed files independently           │
│  Run tests, lint, build                     │
│  Cross-reference with original intent       │
│  → Retry up to 3× on failure               │
└─────────────────────────────────────────────┘

Priority Routing

Boss cascades every request through a priority chain until the best match is found:

Priority	Match Type	When	Example
P1	Skill match	Task maps to a self-contained skill	"merge PDFs" → pdf skill
P2	Specialist agent	Domain-specific agent exists	"security audit" → Security Engineer
P3a	Boss direct	2-4 independent agents	"fix 3 bugs" → parallel spawn
P3b	Sub-orchestrator	Complex multi-step workflow	"refactor + test" → Sisyphus
P3c	Agent Teams	Peer-to-peer communication needed	"implement + review" → Review Chain
P4	Fallback	No specialist matches	"explain this" → general agent

Model Routing

Complexity	Model	Used For
Deep analysis, architecture	Opus	Boss, Oracle, Sisyphus
Standard implementation	Sonnet	executor, debugger, security-reviewer
Quick lookup, exploration	Haiku	explore, simple advisory

3-Phase Sprint Workflow

For end-to-end feature implementation, Boss orchestrates a structured sprint: