Create plan

Skill ComeOnOliver/skillshub/skills/aiskillstore/marketplace/davila7/create-plan

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install

npx -y skills add ComeOnOliver/skillshub --skill create-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.4 KB, 567 tokens by cl100k_base, as published. Nobody here has run it

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.

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).
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.
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).
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)

Gives 0 of the 12 instructions most plan spec skills give in 567 tokens

Counted across 1,099 of the 1,860 authors here whose files we hold, read 2026-08-07

ask one question at a timein 51 of 1099
Break plans into vertical slicesin 29 of 1099, across 11 files
Publish issues in dependency orderin 27 of 1099, across 9 files
Iterate until user approves the breakdownin 25 of 1099, across 7 files
Explore the repository to understand the codebase statein 24 of 1099, across 7 files
Use domain glossary vocabularyin 23 of 1099, across 5 files
Apply correct triage labels to published issuesin 23 of 1099, across 5 files
prefer AFK slices over HITLin 22 of 1099, across 7 files
write a specification before writing any codein 22 of 1099, across 14 files
Write failing tests before implementation codein 22 of 1099, across 20 files
ask clarifying questions until requirements are concretein 21 of 1099, across 13 files
Respect existing architecture decision recordsin 20 of 1099, across 5 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.