planning

Converts a development request into an executable, dependency-ordered implementation plan artifact.

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/blauwtje/exo --skill planning-blauwtje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/blauwtje/exo/tree/main/skills/planning
Command: npx skills add https://github.com/blauwtje/exo --skill planning-blauwtje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning a vague request into working code often fails because the plan restates intent and pushes discovery onto whoever executes it. This Skill produces a plan a fresh session with zero context can execute: verified file paths, complete code per step, and a Run/Expected pair proving every change. ## Core Features & Use Cases - Dependency-ordered task planning: Draws order edges between tasks, splits shared write targets, and sizes each task to one commit with a Plan-task trailer. - Repository-grounded discovery: Builds a repository map of tracked files and exported symbols via repo-map.mjs, delegating deeper search to an explorer agent so the session context stays clean. - Plan validation: Runs plan-check.mjs against the finished plan to catch missing Commit blocks, git add mismatches, steps without Run/Expected, placeholders, and oversized tasks. - Use Case: Given an issue number or a shaped brief, produce a deliverable plan under docs/plans/ with full code for each step, so another session or a cheaper model can paste and run it without deciding anything. ## Quick Start Ask the AI to plan the work for a specific outcome, spec path, or issue number, for example: plan the implementation of issue 42 as a deliverable plan another session can execute.

Frequently Asked Questions about planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an implementation plan another developer or AI session can execute?▼

Restate the goal, map the repository with repo-map.mjs, verify every path and symbol, then write dependency-ordered tasks where each step shows the complete resulting code plus a Run command and Expected result. Finish with plan-check.mjs to validate the artifact.

When should I create a plan instead of editing code directly?▼

Plan when a read-only planning mode is active, a plan is explicitly requested, another session runs the work, or the edits have two or more order dependencies. Same-session work with at most one dependency, one-file edits, and git-only work skip planning.

Does the planning skill work outside a git repository?▼

Yes, but the repository map is unavailable: repo-map.mjs prints a single no map line and discovery starts from the explorer dispatch instead. The plan itself can still name a non-git folder with a git init instruction in its Plan basis section.

Why does plan-check.mjs reject my plan file?▼

It reports a missing Commit block, a git add line that does not match the Files list, a code step without Run or Expected lines, TODO or ellipsis placeholders, or a task exceeding 250 code lines or 4 files. Repair each printed line and rerun it.

What are the limitations of delegating discovery during planning?▼

Only discovery is delegated, to the exo:explorer agent; design, task ordering, and the artifact itself stay in the planning session. Direct reading is capped at eight file ranges before the plan is first written, with the rest routed to the explorer.