create-plan

Generate a Markdown plan with scope, action items, and open questions.

223|23|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/ReinaMacCredy/maestro --skill create-plan-reinamaccredy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/ReinaMacCredy/maestro/tree/main/skills/create-plan
Command: npx skills add https://github.com/ReinaMacCredy/maestro --skill create-plan-reinamaccredy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts user prompts into a single, actionable plan that guides coding tasks to completion.

Core Features & Use Cases

  • One-paragraph plan summary: Clear, actionable direction.
  • Scope in/out: Explicit boundaries and exclusions.
  • Action items: 6–10 atomic steps ready for execution.
  • Tests/validation & edge cases: Built-in checks and risk notes.
  • Open questions: Capture unknowns to resolve later.

Quick Start

Plan a coding task by saying "plan for feature X"; the assistant will return a ready-to-execute plan.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I turn a coding task into an actionable plan?

Generate an actionable plan by describing your coding task or feature request. The plan outputs a structured Markdown format with a summary, scope boundaries, six atomic action items, validation steps, and open questions—ready to execute immediately.

What should a good project plan include?

A complete plan defines scope (what's in and out), breaks work into six discrete action items, identifies tests and edge cases, and lists unresolved questions. This structure ensures nothing is overlooked and execution can begin without ambiguity.

How do I scope a feature to avoid scope creep?

Scope planning explicitly lists what the feature includes and excludes upfront. By defining boundaries before execution, you prevent unplanned work from derailing timelines and keep action items focused on the core deliverable.

Can I use planning to identify risks before coding starts?

Yes. The planning process surfaces edge cases, validation requirements, and open questions before implementation begins, letting you flag dependencies, unknowns, and constraints that could block progress.

What's the difference between a plan and a to-do list?

A plan includes context: why the work matters, what's in scope, what tests validate success, and what remains unknown. A to-do list is just tasks. Plans prevent misaligned execution and rework.