concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Concise Planning
- Goal
- Workflow
- 1. Scan Context
- 2. Minimal Interaction
- 3. Generate Plan
- Plan Template
- Checklist Guidelines
Turn a user request into a single, actionable plan with atomic steps. Read README.md, docs, and relevant code files. Identify constraints (language, frameworks, tests). Ask at most 1–2 questions and only if truly blocking. Make reasonable assumptions for non-blocking unknowns. 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. Atomic: Each step should be a single logical unit of work. Verb-first: "Add...", "Refactor...", "Verify...". Concrete: Name specific files or modules when possible.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/productivity/concise-planning/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:39.633Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.