Quick Plan

Create a lightweight plan document for: $ARGUMENTS

Overview

This skill creates concise plan documents in backlog/plans/ using the standard template. Suitable for:

• Capturing ideas quickly before context is lost
• Scoping small-to-medium features
• Creating starting points for later /planner expansion

For complex features requiring full analysis, spec, research, and TDD task breakdown, use /planner instead.

Workflow

Step 1: Generate Filename

Create filename using today's date and a slug derived from the input:

• Format: YYYYMMDD-short-description.md
• Example: 20260127-add-user-authentication.md

Step 2: Gather Context (Optional)

When input references existing code or systems:

• Briefly scan relevant files to understand current state
• Note obvious constraints or dependencies

Limit context gathering to under 2 minutes. Extensive research indicates /planner may be more appropriate.

Step 3: Create Plan

Create the plan file at backlog/plans/{filename}:

markdown
1---
2title: "{Descriptive title}"
3status: open
4priority: {low|medium|high|critical}
5created: {YYYY-MM-DD}
6---
7
8# {Plan Title}
9
10## Summary
11
12{1-2 sentences describing what this plan achieves}
13
14## Motivation
15
16{Why is this needed? What problem does it solve? 2-3 sentences.}
17
18## Proposal
19
20### Goals
21
22- {Primary goal}
23- {Secondary goal if applicable}
24
25### Non-Goals
26
27- {What this explicitly does NOT cover}
28
29## Design
30
31{High-level approach in 3-5 sentences or bullet points. Include key technical decisions if obvious.}
32
33## Tasks
34
35- [ ] {Task 1}
36- [ ] {Task 2}
37- [ ] {Task 3}
38
39## Open Questions
40
41- {Any uncertainties requiring resolution}

Step 4: Output Summary

After creating the plan:

Created: backlog/plans/{filename}

{title}
Priority: {priority}
Tasks: {count}

Next steps:
- Review and refine the plan
- Adjust priority if needed
- Expand with /planner if complexity warrants
- Or start implementation directly for simple plans

Guidelines