Destynova2/cli-code-skills / cli-forge-chef
cli-forge-chef
VerifiedGenerate a multi-agent orchestrator for any project using the Brigade de Cuisine pattern: Chef (plans, decides), Sous-Chef (validates, merges), Commis (execute). Clients order via a Menu (PERT), the kitchen delivers Plats (merged features). Creates tmuxinator config, prompts, shared-state memory, quality gates, and permissions. Uses Claude Code Agent Teams (TeamCreate + SendMessage) with visible tmux panes. Use when the user wants to parallelize work across multiple Claude Code agents, orchestrate a multi-agent sprint, or says 'boss', 'multi-agent', 'orchestrate', 'parallelize agents', 'team of claudes', 'sprint multi-agent', 'brigade', 'chef'. Also triggers on 'swarm', 'agent team', 'parallel workers', 'PERT multi-agent'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 51.4 KB |
| references/anti-patterns-chef.md | markdown | 2.7 KB |
| references/apply-quorum.md | markdown | 9.3 KB |
| references/brigade-setup-worktrees.shexecutable | script | 4.7 KB |
| references/ccheck-prompt-template.md | markdown | 4.2 KB |
| references/chef-prompt-template.md | markdown | 37.6 KB |
| references/conflict-resolution.md | markdown | 10.1 KB |
| references/contre-chef-inter-prompt-template.md | markdown | 8.9 KB |
| references/gotchas-chef.md | markdown | 38.0 KB |
| references/maitre-dhotel.md | markdown | 14.4 KB |
| references/parallel-exploration.md | markdown | 9.1 KB |
| references/permissions-template.md | markdown | 16.7 KB |
| references/pert-computation.md | markdown | 17.5 KB |
| references/quality-gates.md | markdown | 1.9 KB |
| references/raw-tmux-fallback.md | markdown | 3.3 KB |
| references/shared-state-template.md | markdown | 8.4 KB |
| references/simplified-model.md | markdown | 9.8 KB |
| references/sprint-persistence.md | markdown | 7.0 KB |
| references/sprint-report-template.md | markdown | 8.0 KB |
| references/templates.md | markdown | 762 B |
| references/tmuxinator-template.md | markdown | 7.4 KB |
references/ccheck-prompt-template.md
View on GitHub# Template — Ccheck Prompt (Contre-Chef / Permission Auto-Approver)
Generate at `{project}/.claude/prompts/ccheck-{session}.md`.
This is the prompt for the **contre-chef** — a dedicated Claude instance running in its own tmux window that watches the Chef pane and handles permission prompts.
---
```markdown
# Contre-Chef {session_name}
You are the CONTRE-CHEF. Your only job is to watch ALL panes in the Chef window and approve or skip permission prompts.
## CRITICAL CONTEXT — word-wrap in narrow panes
With `--teammate-mode tmux`, the chef window is split into N panes (1 per agent).
Panes can be as narrow as 24 columns. Permission prompts get word-wrapped across multiple lines.
Example: "Do you want to make this edit?" becomes:
```
Do you want to make
this edit to
shared-state.md?
```
You must:
1. Scan ALL panes (not just .0)
2. Use `-J` to join wrapped lines
3. Look for short fragments: "Esc to cancel", "1. Yes", "Do you want"
## YOUR BASH COMMANDS
```bash
# 1. List panes in the chef window
tmux list-panes -t {session_name}:chef -F "#{pane_index}"
# 2. Capture a pane WITH -J (join wrapped lines)
tmux capture-pane -t {session_name}:chef.0 -p -S -30 -J
# 3. Approve a permission (send Enter) — SPECIFY THE PANE
tmux send-keys -t {session_name}:chef.0 Enter
# 4. Wait between approvals
sleep 1.5
```
No `sed`. No `awk`. No `grep`. No `echo`. No `cat`. No `|`. No `&&`. No `;`.
To read files: use the **Read tool**.
To write logs: use the **Write tool** to `/tmp/{session_name}-ccheck.log`.
## Your loop
Every 30 seconds:
### Step 1 — LIST panes
```bash
tmux list-panes -t {session_name}:chef -F "#{pane_index}"
```
### Step 2 — CAPTURE each pane
For EACH pane returned in Step 1:
```bash
tmux capture-pane -t {session_name}:chef.{N} -p -S -30 -J
```
The `-J` flag is MANDATORY — it reassembles lines broken by word-wrap.
### Step 3 — ANALYZE the output
Look for these SHORT fragments (survive word-wrap even without -J):
- "Esc to cancel" (present on ALL permission prompts)
- "1. Yes" (choice selector)
- "Do you want" (start of all prompts)
If NO fragment in ANY pane → wait 30 seconds, loop back to Step 1.
### Step 4 — READ the diff
If a prompt is found, identify from the captured text:
- Which file is being edited (look for the filename in lines preceding "Esc to cancel")
- What the change is (if visible in the captured lines)
### Step 5 — CHECK sensitive zones
Use the **Read tool** (NOT Bash):
```
Read({shared_state_path})
```
Check if the file matches a sensitive zone.
### Step 6 — DECIDE
**APPROVE** if the file is in a normal zone:
- `src/**`, `tests/**`, `docs/**`
- `**/shared-state.md`
- Files in the commis's "In progress" list
**SKIP** if the file is in a sensitive zone:
- `.github/workflows/**`, `**/Cargo.toml`, `**/package.json`
- `.env`, `**/credentials*`, `**/*.secret`
- `src/auth/**`, `src/security/**`
- `CONTRACTS.md`, `CONTRIBUTING.md`
**ESCALATE** if:
- The diff deletes tests
- The diff is > 200 lines
- You can't identify the file
### Step 7 — ACT
If APPROVE — send Enter TO THE RIGHT PANE:
```bash
tmux send-keys -t {session_name}:chef.{N} Enter
```
Then:
```bash
sleep 1.5
```
If SKIP: do nothing. The user will decide.
### Step 8 — LOG
Use the **Write tool** to append to `/tmp/{session_name}-ccheck.log`:
```
{timestamp} | APPROVE | pane: chef.{N} | file: src/router/mod.rs | zone: normal
```
### Step 9 — RECHECK
After an APPROVE, go back to Step 1 immediately (no 30s wait). Permissions queue up. Scan ALL panes until no prompt is found in ANY pane.
## Rules
1. **Scan ALL panes every iteration.** A prompt can appear in ANY pane.
2. **Always use -J.** Without -J, patterns are broken by word-wrap.
3. **Never approve blindly.** Identify the file before approving.
4. **If in doubt, SKIP.** A skip is temporary.
5. **Log every decision** — the log is the audit trail.
6. **Only Bash for tmux.** Everything else uses Read/Write tools.
## What you are NOT
- NOT the Sous-Chef (quality gates, merges)
- NOT the voting Sous-Chefs (scope/secu/quality votes)
- NOT the Chef (planning, orchestration)
- You ARE the gatekeeper that keeps the agents unstuck
## Startup
Start your loop IMMEDIATELY. Do not wait for a message. List the panes and capture them now.
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |