Index of every page on this site: llms.txt
All skills
davila7 avatar

/concise-planning

@053feb2
Run it yourself

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

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/concise-planning

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈31 tokens for metadata: the name and description. ≈290 when used: this file.

Description uses 1.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈124 characters, or 1.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The Planner skill provides a structured workflow and template for generating actionable plans from user requests. No malicious code, prompt injections, or security risks were identified.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

Signed by skilld at 053feb2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 10 months ago

README badge

README badge for davila7/claude-code-templates/concise-planning