pl4n
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.
What this skill does
# Pl4n Planning Workflow ## Setup (if pl4n command not found) If the `pl4n` command is not available, install it first: ```bash cd /path/to/pl4n/repo bun install ``` Pl4n orchestrates multiple AI agents (Claude Code + OpenAI Codex) to create implementation plans through iterative refinement. ## Quick Reference | 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 | ## Slash Commands | 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 | ## Workflow ``` init → [user edits] → continue → [user edits] → ... → approve ``` 1. **init**: Creates session, runs first turn (blocks until complete) 2. **User edits**: Human reviews `.pl4n/sessions/<id>/turns/NNN.md` 3. **continue**: Starts next turn, runs agents (blocks until complete) 4. **approve**: Locks plan, creates PLAN.md symlink ## Session Phases - `initializing` - Session just created - `drafting` - Agents creating initial drafts - `peer_review` - Agents reviewing each other's work - `synthesizing` - Combining into unified plan - `user_review` - Waiting for human feedback - `approved` - Plan locked and final ## Plan File Format ```markdown ## 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] ``` ## Session File Structure ``` .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 ``` ## Session Continuation Agents preserve context across turns: - Claude Code: `--resume <session_id>` - Codex: `codex resume <thread_id>` First turn exploration (reading files, understanding patterns) is remembered in subsequent turns.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.