workflows:plan

Create a plan for a new project or initiative

Introduction

Note: The current year is 2026. Use this when dating plans and searching for recent documentation.

The follow-on options at the end of this command call /deepen-plan and /technical_review, and the refine option loads the document-review skill. This kit ships none of the three. If one is not installed, skip that option, offer the rest, and say so rather than stopping.

Transform project descriptions, campaign briefs, or initiative ideas into well-structured markdown plans that follow project conventions and best practices. This command provides flexible detail levels to match your needs.

Project Description

<feature_description> #$ARGUMENTS </feature_description>

If the project description above is empty, ask the user: "What would you like to plan? Please describe the project, campaign, initiative, or improvement you have in mind."

Do not proceed until you have a clear project description from the user.

0. Idea Refinement

Check for brainstorm output first:

Before asking questions, look for recent brainstorm documents in docs/brainstorms/ that match this project:

ls -la docs/brainstorms/*.md 2>/dev/null | head -10

Relevance criteria: A brainstorm is relevant if:

• The topic (from filename or YAML frontmatter) semantically matches the project description
• Created within the last 14 days
• If multiple candidates match, use the most recent one

If a relevant brainstorm exists:

1. Read the brainstorm document thoroughly - every section matters
2. Announce: "Found brainstorm from [date]: [topic]. Using as foundation for planning."
3. Extract and carry forward ALL of the following into the plan:
   • Key decisions and their rationale
   • Chosen approach and why alternatives were rejected
   • Constraints and requirements discovered during brainstorming
   • Open questions (flag these for resolution during planning)
   • Success criteria and scope boundaries
   • Any specific tool choices, targeting decisions, or channel strategies discussed
4. Skip the idea refinement questions below - the brainstorm already answered WHAT to build
5. Use brainstorm content as the primary input to research and planning phases
6. Critical: The brainstorm is the origin document. Throughout the plan, reference specific decisions with (see brainstorm: docs/brainstorms/<filename>) when carrying forward conclusions. Do not paraphrase decisions in a way that loses their original context - link back to the source.
7. Do not omit brainstorm content - if the brainstorm discussed it, the plan must address it (even if briefly). Scan each brainstorm section before finalizing the plan to verify nothing was dropped.