Multi-agent ensemble planning with pl4n CLI. Use when discussing implementation plans, task planning, or when user mentions pl4n sessions. Knows pl4n CLI syntax and workflow.
/plugin marketplace add gbasin/pl4n/plugin install pl4n@pl4nThis skill inherits all available tools. When active, it can use any tool Claude has access to.
If the pl4n command is not available, install it first:
cd /path/to/pl4n/repo
bun install
Pl4n orchestrates multiple AI agents (Claude Code + OpenAI Codex) to create implementation plans through iterative refinement.
| Command | Purpose |
|---|---|
pl4n init "task" | Start new planning session (blocks until first turn complete) |
pl4n init --file spec.md | Start session from file (for large specs) |
pl4n status --session <id> | Check progress |
pl4n continue --session <id> | Start next turn after edits (blocks until complete) |
pl4n approve --session <id> | Lock plan as final |
pl4n list | List all sessions |
pl4n clean --session <id> | Remove session |
pl4n diff --session <id> | Show changes between turns |
| Command | Purpose |
|---|---|
/pl4n:plan | Interactive planning - choose interview, spec file, or paste |
/pl4n:continue <id> | Continue after editing turn file |
/pl4n:approve <id> | Lock plan as final |
/pl4n:status <id> | Check session status |
/pl4n:list | List all sessions |
init → [user edits] → continue → [user edits] → ... → approve
.pl4n/sessions/<id>/turns/NNN.mdinitializing - Session just createddrafting - Agents creating initial draftspeer_review - Agents reviewing each other's worksynthesizing - Combining into unified planuser_review - Waiting for human feedbackapproved - Plan locked and final## Questions
### Q1: [Question needing user input]
**Context:** Why this matters
**Answer:** [User fills this in]
## Summary
[2-3 sentence overview]
## Tasks
- [ ] **Task 1**: Description
- **Files:** `path/file.ts` (create|modify)
- **Rationale:** Why needed
- **Dependencies:** none | Task N
## Risks
- **Risk name** (severity: high|medium|low)
- **Mitigation:** How to address
## Alternatives Considered
- **Alternative**: Rejected because [reason]
.pl4n/sessions/swift-river/ # Human-friendly session ID
├── meta.yaml # Task, created_at
├── state.yaml # turn, phase, agent_plan_ids
├── input.md # Original task input
├── bold-peak.md # Agent's working plan (opaque name)
├── calm-forest.md # Another agent's plan
├── turns/
│ ├── 001.md # Turn 1 synthesis (user edits this)
│ └── 002.md # Turn 2
├── agents/
│ ├── opus/cli_session_id.txt
│ ├── codex/cli_session_id.txt
│ └── turn-001/
│ ├── opus-draft.md
│ └── opus-final.md
└── PLAN.md # Symlink to approved turn
Agents preserve context across turns:
--resume <session_id>codex resume <thread_id>First turn exploration (reading files, understanding patterns) is remembered in subsequent turns.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.