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

/create-plan

@053feb2
Run it yourself

Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/create-plan

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈26 tokens for metadata: the name and description. ≈568 when used: this file.

Description uses 1.3% 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 ≈105 characters, or 1.3%.

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.

Create Plan

Goal

Turn a user prompt into a single, actionable plan delivered in the final assistant message.

Minimal workflow

Throughout the entire workflow, operate in read-only mode. Do not write or update files.

  1. Scan context quickly

    • Read README.md and any obvious docs (docs/, CONTRIBUTING.md, ARCHITECTURE.md).
    • Skim relevant files (the ones most likely touched).
    • Identify constraints (language, frameworks, CI/test commands, deployment shape).
  2. Ask follow-ups only if blocking

    • Ask at most 1–2 questions.
    • Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
    • If unsure but not blocked, make a reasonable assumption and proceed.
  3. Create a plan using the template below

    • Start with 1 short paragraph describing the intent and approach.
    • Clearly call out what is in scope and what is not in scope in short.
    • Then provide a small checklist of action items (default 6–10 items).
      • Each checklist item should be a concrete action and, when helpful, mention files/commands.
      • Make items atomic and ordered: discovery → changes → tests → rollout.
      • Verb-first: "Add…", "Refactor…", "Verify…", "Ship…".
    • Include at least one item for tests/validation and one for edge cases/risk when applicable.
    • If there are unknowns, include a tiny Open questions section (max 3).
  4. Do not preface the plan with meta explanations; output only the plan as per template

Plan template (follow exactly)

# Plan

<1–3 sentences: what we're doing, why, and the high-level approach.>

## Scope
- In:
- Out:

## Action items
[ ] <Step 1>
[ ] <Step 2>
[ ] <Step 3>
[ ] <Step 4>
[ ] <Step 5>
[ ] <Step 6>

## Open questions
- <Question 1>
- <Question 2>
- <Question 3>

Checklist item guidance

Good checklist items:

  • Point to likely files/modules: src/..., app/..., services/...
  • Name concrete validation: "Run npm test", "Add unit tests for X"
  • Include safe rollout when relevant: feature flag, migration plan, rollback note

Avoid:

  • Vague steps ("handle backend", "do auth")
  • Too many micro-steps
  • Writing code snippets (keep the plan implementation-agnostic)

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 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is a planning tool that helps the agent generate structured project plans by reading existing documentation and source files. It operates in a read-only mode and lacks capabilities to execute code, write files, or access the network, making it safe for general use.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

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 11 months ago
metadata
{
  "short-description": "Create a plan"
}

README badge

README badge for davila7/claude-code-templates/create-plan