Skip to main content
Business & Productivitydavila7

concise-planning

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

Stars
27,674
Source
davila7/claude-code-templates
Updated
2026-05-30
Slug
davila7--claude-code-templates--concise-planning
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/davila7/claude-code-templates/HEAD/cli-tool/components/skills/productivity/concise-planning/SKILL.md -o .claude/skills/concise-planning.md

Drops the SKILL.md into .claude/skills/concise-planning.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Concise Planning

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.