plan

Generate structured software development plans with multi-option comparisons and documentation folders.

3|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/alpoxdev/claude-code --skill plan-alpoxdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/alpoxdev/claude-code/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/alpoxdev/claude-code --skill plan-alpoxdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to planning software features by framing options, analyzing trade-offs, and generating ready-to-use documentation folders. It helps teams decide between approaches like feature additions, architecture changes, and refactors, while ensuring a clear, auditable plan.

Core Features & Use Cases

  • Structured option generation: produces 2-3 viable options with pros/cons and impact analysis.
  • Parallel document generation: creates OVERVIEW, OPTIONS, IMPLEMENTATION, RISKS, and REFERENCES in a dedicated folder, ready for review.
  • Guided workflow: enforces a sequential planning process and prepares a ready-to-execute plan in .claude/plan/00.[feature]/ with a consistent naming scheme.
  • Use cases: planning a new authentication flow, a UI redesign, or a database migration, with an auditable trail.

Quick Start

Start by invoking the plan skill for your feature, e.g., /plan user authentication redesign, and review the generated plan folder at .claude/plan/00.[feature] before proceeding.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan software features with multiple options and trade-off analysis?▼

Planning software features with multiple options is done by generating 2-3 viable approaches with pros/cons and impact analysis. The Skill automates this by producing structured documentation including OVERVIEW, OPTIONS, IMPLEMENTATION, RISKS, and REFERENCES reports in a dedicated folder.

What's the best way to document an architecture change before implementation?▼

Documenting an architecture change is best handled through a guided workflow that creates an auditable trail. It enforces a sequential planning process and generates a ready-to-execute plan in a dedicated folder with a consistent naming scheme for review.

Can I use this for database migration planning and refactoring tasks?▼

Yes, you can use it for database migration planning and refactoring tasks. It supports scenarios like feature additions, architecture changes, and refactors by guiding authors through analysis and providing multi-option comparisons for these software development projects.

How do I generate structured implementation and risk documentation for a new authentication flow?▼

Generating structured implementation and risk documentation for a new authentication flow is done by invoking the planning workflow. It creates parallel documents including IMPLEMENTATION and RISKS reports automatically in a dedicated folder for your feature.

Does this planning workflow require any specific dependencies or components?▼

No, this planning workflow does not require any specific dependencies or components to function. It operates independently to automate option exploration and generate structured plans and documentation for software development projects.

When should I not use automated option exploration for software development projects?▼

Automated option exploration should be avoided when a simple, single-solution task requires no trade-off analysis or multi-option comparison. It is designed for complex scenarios like architecture changes and refactors that benefit from structured, documented workflows.