Concise Planning
SkillProductivityConcise-planning is a skill that turns a request for a coding task into a clear, actionable, and atomic checklist. When a user asks for a plan, the agent produces a short, step-by-step list it can follow while doing the work.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent that supports loading skills.
Then ask your AI: use the Concise Planning skill
What your AI can do with it
- Generates a clear, actionable checklist for a coding task
- Breaks a plan into atomic, step-by-step items
- Produces a checklist the agent can follow during implementation
Getting started
- Have an agent that supports loading skills.
- Add the concise-planning skill to the agent's available skills.
- Ask the agent to plan a coding task, and it will use the skill to produce a checklist.
What this skill tells your AI
The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/productivity/concise-planning/SKILL.md and read by ahel’s review.
Goal
Turn a user request into a single, actionable plan with atomic steps.
Workflow
1. Scan Context
- Read
README.md, docs, and relevant code files. - Identify constraints (language, frameworks, tests).
2. Minimal Interaction
- Ask at most 1–2 questions and only if truly blocking.
- Make reasonable assumptions for non-blocking unknowns.
3. Generate Plan
Use the following structure:
- Approach: 1-3 sentences on what and why.
- Scope: Bullet points for "In" and "Out".
- Action Items: A list of 6-10 atomic, ordered tasks (Verb-first).
- Validation: At least one item for testing.
Plan Template
# Plan
<High-level approach>
## Scope
- In:
- Out:
## Action Items
[ ] <Step 1: Discovery>
[ ] <Step 2: Implementation>
[ ] <Step 3: Implementation>
[ ] <Step 4: Validation/Testing>
[ ] <Step 5: Rollout/Commit>
## Open Questions
- <Question 1 (max 3)>
Checklist Guidelines
- Atomic: Each step should be a single logical unit of work.
- Verb-first: "Add...", "Refactor...", "Verify...".
- Concrete: Name specific files or modules when possible.
Signals
- GitHub stars
- 32k
- Forks
- 4k
- Last commit
- Sep 2026
Questions
- When should this skill be used?
- Use it when a user asks for a plan for a coding task, so the agent generates a clear, actionable, and atomic checklist.
- What does the output look like?
- A short, step-by-step checklist with atomic items that the agent can follow while completing the coding task.
Advanced
- Item type
- skill
- Key
concise-planning-davila7- Source
- github.com/davila7/claude-code-templates