plan

Creates structured implementation plans through requirement interviews and codebase exploration.

4|Updated Sep 30, 2024
One-click install
npx skills add https://github.com/okm321/dotfiles --skill plan-okm321
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/okm321/dotfiles/tree/main/claude/skills/plan
Command: npx skills add https://github.com/okm321/dotfiles --skill plan-okm321

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into code without a plan leads to scope creep, missed edge cases, and rework. This Skill takes a raw task description and turns it into a structured, reviewable implementation plan before any code is written. ## Core Features & Use Cases - Scope Assessment: Automatically judges whether a task is large (3+ files or architectural decisions) or small, and adjusts the planning depth accordingly. - Targeted Interviews: For large-scope tasks, asks 1-3 focused questions about constraints, edge cases, and trade-offs instead of interrogating you endlessly. - Codebase Exploration: Delegates investigation to a sub-agent to find relevant files, existing patterns, and test structure without cluttering the main context. - Structured Plan Output: Produces a plan with overview, per-file changes, implementation order, test strategy, and risks, scoped to roughly 30 minutes of work. - Use Case: You want to add Google OAuth to your app. Run the skill, answer a couple of clarifying questions, and receive a phased plan that follows your codebase's existing conventions. ## Quick Start Ask the assistant to plan adding Google OAuth authentication to the application using the plan skill.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an implementation plan before writing code?▼

Invoke the plan skill with a task description, such as adding an API cache or normalizing a database schema. It assesses scope, asks clarifying questions for large tasks, explores the codebase, and outputs a structured plan with changes, order, and tests.

How does the plan skill decide when to ask clarifying questions?▼

It estimates whether the change touches three or more files or involves architectural decisions. Large-scope tasks trigger a short interview of one to three questions about constraints and trade-offs; small tasks skip straight to codebase exploration.

Does the plan skill modify code directly?▼

No. It only produces a structured plan covering overview, per-file changes, implementation order, test strategy, and risks. Code changes happen separately after you review and approve the plan.

What happens when a task is too large for one plan?▼

The skill splits oversized tasks into phases and details only the first phase. Plans are scoped to roughly 30 minutes of implementation work to keep each step reviewable and actionable.

Why does the plan skill use a sub-agent for codebase exploration?▼

Delegating exploration to a sub-agent keeps the main context window free of raw search results. Only the key findings about relevant files, existing patterns, and test structure are brought back for planning.