From the author
Use when a user commits to a direction and asks to plan, brief, research, or operationalize it; or wants to enumerate designs, configurations, scenarios, and paths, audit a supplied plan, tune the review flow, or a plan-mode enforcement hook intercepts a plan review, or lock a greenfield architecture and interfaces. Modes: score, breakdown, shape, visual, storm (subject, dimensions, bounds), review (audit or tune), waterfall (brief, constraints, existing paths). Not for four-phase review: use autoplan.
Install
npx skills add OutlineDriven/outline-driven-development --skill plan -a claude-code
Installs to .claude/skills/plan/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- plan-modeCodeAlive-AI/ai-driven-developmentUse this skill when the user asks to plan, design, scope, estimate, or implement a feature, bug fix, refactor, migration, integration, API change, UI change, or other project modification. Enforces a planning gate before editing code — investigate project context, analyze the task, surface ambiguities, contradictions, risks, dependencies, and blockers, ask focused questions, produce an evidence-based step-by-step plan, and implement only after explicit user approval. Not for trivial one-line edits, pure questions about the codebase, or changes the user has already reviewed and approved for direct implementation.Planning★ 166
- autopilotOutlineDriven/outline-driven-developmentUse when a human has an approved delivery plan and wants the full chain run under phase gates. Not for planning, open-ended debugging, or single-step execution: use work directly.Planning★ 54
- architectaiskillstore/marketplaceDesign systems, plan implementations, review architecture decisions - Use when you need to plan a complex feature, design system architecture, or make high-level technical decisions.Planning★ 444
- autoplanOutlineDriven/outline-driven-developmentUse when the user runs /autoplan on a plan or idea. Reviews, amends, and derives task IDs with a final human approval gate. Not for remote, credential, publish, deploy, or irreversible changes.DevOps★ 54
- turboplantobihagemann/turboAnalyze task complexity and route to a mode by artifact: direct fix for clear-scope changes, or a plan file when the approach needs to be written down. Use when the user asks to "turboplan", "run turboplan", "plan this task", "turbo plan mode", "plan and implement", or "use turboplan instead of plan mode".Writing★ 416
- implementation-planningcbrock84/headcountTurns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.Planning★ 2.1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in