quick-plan
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
/plannerexpansion
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}:
---
title: "{Descriptive title}"
status: open
priority: {low|medium|high|critical}
created: {YYYY-MM-DD}
---
# {Plan Title}
## Summary
{1-2 sentences describing what this plan achieves}
## Motivation
{Why is this needed? What problem does it solve? 2-3 sentences.}
## Proposal
### Goals
- {Primary goal}
- {Secondary goal if applicable}
### Non-Goals
- {What this explicitly does NOT cover}
## Design
{High-level approach in 3-5 sentences or bullet points. Include key technical decisions if obvious.}
## Tasks
- [ ] {Task 1}
- [ ] {Task 2}
- [ ] {Task 3}
## Open Questions
- {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
| Guideline | Detail |
|---|---|
| Concise | Quick capture, not exhaustive planning |
| Priority inference | Blocking issues = high, nice-to-have = low |
| Task count | 3-7 tasks; more than 7 suggests /planner |
| Optional sections | Omit "Open Questions" if none exist |
| Time limit | Context gathering under 2 minutes |
More from ianphil/my-skills
astral-uv
>
11glab
GitLab CLI (glab) for merge requests, issues, and CI/CD pipelines. Use when working with GitLab repositories for MR creation/review, issue management, pipeline debugging, or any GitLab API operations. Triggers on GitLab URLs, mentions of "merge request" or "MR" (not "PR"), gitlab.com, or glab commands.
10ado
Azure DevOps CLI (az ado). Use for work items, PRs, pipelines, and backlog management. Triggers on: az ado, ADO, azure devops, work item, backlog, az boards, az repos, az pipelines.
1ainotes
This skill should be used when the user asks to "consolidate notes", "summarize ainotes", "clean up notes", "ainotes", or wants to consolidate accumulated agent observations into a compact summary.
1workiq
This skill should be used when the user asks to "install WorkIQ", "set up WorkIQ", "query my emails with AI", "connect AI to Microsoft 365", "query my meetings or documents", "use workiq ask", or wants to use natural language to search Microsoft 365 data (emails, meetings, Teams messages, documents, people) from an AI assistant.
1closer
This skill should be used when the user asks to "close feature", "archive feature", "complete feature N", "move feature to completed", or wants to move a finished feature to the _completed/ directory.
1