Menu
Plan how to build it. Decompose specs into milestones with dependencies and risk mitigations. Run after /spec.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/rjmurillo/ai-agents --skill planThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Define what to build. Transform a problem into testable requirements with acceptance criteria.
Validate and complete session logs before commit. Auto-populates session end evidence (commit SHA, lint results, memory updates) and runs validation. Use when finishing a session, before committing, or when session validation fails. Do NOT use to create a new session log (use session-init) or to repair a session protocol failure reported by CI (use session-log-fixer).
Create protocol-compliant JSON session logs with verification-based enforcement. Autonomous operation with auto-incremented session numbers and objective derivation from git state. Use when starting any new session. Use when you say "start a session", "create the session log". Do NOT use for mid-session protocol checks (use session), or to complete and validate a log at the end of a session (use session-end).
Based on SOC occupation classification
| name | plan |
| description | Plan how to build it. Decompose specs into milestones with dependencies and risk mitigations. Run after /spec. |
| argument-hint | spec-output-or-issue-number |
| allowed-tools | Task, Skill, Read, Write, Glob, Grep |
| user-invocable | true |
Plan: the problem statement from the conversation (under Copilot CLI the skill tool takes no argument vector, so state it in your message)
If the problem statement from the conversation (under Copilot CLI the skill tool takes no argument vector, so state it in your message) is empty, check for recent /spec output in the conversation. If none found, ask the user what to plan.
Planning a spec that was never gated manufactures work. If there is no /spec output for this work (no requirement, no design, no testable acceptance criteria), do not decompose it into milestones yet. Run /spec first: it applies the front-gate (the six forcing questions, the front-gate-before-pipeline pattern) and confirms a named blocked user, a documented status quo, and a concrete observation before any downstream step runs. Return here once the spec exists. Skip this only when the user explicitly asks to plan an ungated idea and accepts that trade-off.
agent_type: "project-toolkit:milestone-planner": You are a project planner. Break the spec into milestones with clear exit criteria. Each milestone is independently shippable. Sequence by dependencies. Flag parallel opportunities.agent_type: "project-toolkit:task-decomposer": You are a work breakdown specialist. Decompose each milestone into atomic tasks. Each task is independently verifiable with a clear done definition. Size by complexity (S/M/L), not time.skill: "execution-plans" to persist the plan as a versioned artifact.agent_type: "project-toolkit:analyst": You are a risk analyst. Run a pre-mortem on this plan. What fails first? What dependencies are fragile? What assumptions are untested?agent_type: "project-toolkit:critic": You are a plan reviewer. Validate: is scope complete? Can tasks execute in the stated sequence? Are estimates credible? Is anything missing?Structured plan: