Agent skill

Give Plan

by avibebuilder in avibebuilder/claude-prime

A skill your agent uses when the user wants a written, reviewable plan or spec produced before coding starts.

MITAuto-check passedAgent Workflows

Install Give Plan

skills CLI
$ npx skills add avibebuilder/claude-prime --skill give-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install avibebuilder/claude-prime give-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/give-plan .claude/skills/give-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
give-plan
GitHub stars
120
Token cost
~911 tokens
SKILL.md length
376 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user wants a written, reviewable plan or spec produced before coding starts.

  • Works in 5 steps: Clarify the planning goal → Ground in evidence → Choose the right altitude → …
  • The user wants a written
  • SKILL.md covers Core contract, Process, Boundaries and Request
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Give Plan is an agent skill from avibebuilder/claude-prime. Use when the user wants a written, reviewable plan or spec produced before coding starts. Triggers on: mapping out changes without implementing, thinking through risks of upgrades or migrations, evaluating approaches before committing to one, writing specs for team review, phasing work into stages, or any request that explicitly defers coding ('don't implement yet', 'before we build'). The distinguishing signal is that the user wants a plan artifact — not implementation, not a conversational answer. MUST…

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Planning. The repository describes itself as: You've heard Claude Code can do amazing things. Skills, hooks, agents, memory systems — but who has time to figure all that out? Claude Prime sets it up for you in one command. The licence is MIT.

When your agent uses it

  • The user wants a written
  • Reviewable plan
  • Spec produced before coding starts
  • : mapping out changes without implementing

Example prompts

  • “t implement yet”
  • “before we build”
  • “/give-plan”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Clarify the planning goal
  2. Ground in evidence
  3. Choose the right altitude
  4. Write the plan (right-size the artifact)
  5. Present and stop

What it can do on your machine

Read from SKILL.md and the folder at commit 80bcfa4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Give Plan loads about 911 tokens when it runs. Until then it costs about 150 tokens; SKILL.md has 376 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~150
When it runs · the whole SKILL.md, loaded when a task matches
~911

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from avibebuilder/claude-prime at commit 80bcfa4, republished under its MIT licence (© avibebuilder). 376 words, ~911 tokens.

Download SKILL.mdSave it as .claude/skills/give-plan/SKILL.md (or your agent's skills folder).
name
give-plan
description
Use when the user wants a written, reviewable plan or spec produced before coding starts. Triggers on: mapping out changes without implementing, thinking through risks of upgrades or migrations, evaluating approaches before committing to one, writing specs for team review, phasing work into stages, or any request that explicitly defers coding ('don't implement yet', 'before we build'). The distinguishing signal is that the user wants a plan artifact — not implementation, not a conversational answer. MUST activates inside Claude's native plan mode to have a better planning behavior.
argument-hint
what-to-plan

ultrathink

Core contract

Figure out the right approach, write a plan the user can inspect, and stop. Planning is not approval to implement — wait for explicit go-ahead before writing any code.

  • Clarify only what would materially change the plan.
  • Read the codebase before making claims. Distinguish confirmed facts, inferences, and unknowns — never hide uncertainty.
  • Optimize for reviewability over momentum.

If already in native plan mode, this skill shapes how to plan; plan mode provides the workflow structure and must follow this skill guidelines.

Process

Check conversation context and skip completed steps.

1. Clarify the planning goal

What kind of plan? Scoped implementation, phased feature, migration/rollout, architecture decision, or spec artifact. Ask only the questions that matter.

2. Ground in evidence

Read relevant files and search the codebase before proposing changes. Be explicit about what's confirmed from code vs. inferred vs. unknown.

3. Choose the right altitude
  • Small change → concise plan with touchpoints and validation
  • Multi-file feature → phased plan with dependencies
  • Architecture choice → options, tradeoffs, recommendation
  • Migration / rollout → sequencing, rollback, validation checkpoints

Don't force every request into the same template.

4. Write the plan (right-size the artifact)

Match artifact to plan size — don't force plans/*.md on small scoped changes.

  • Inline prose — small single-file tweaks, quick scoped edits, brief decisions. Present the plan in the response and stop.
  • plans/YYYYMMDDHHMMSS-{plan-name}.md — multi-file features, migrations, architecture decisions, anything that benefits from review or history.
  • plans/YYYYMMDDHHMMSS-{plan-name}/plan.md + phase files — large multi-phase work where each phase warrants independent reading/editing.

Use date +%Y%m%d%H%M%S for timestamps.

A strong plan covers: problem summary, recommended approach, phases/workstreams, affected files/modules/systems, dependencies and sequencing, validation strategy, risks and mitigations, assumptions and open questions, non-goals when useful.

Show full SKILL.md (104 more words)Show less
5. Present and stop

Summarize the recommendation, call out risks/assumptions/unknowns, clarify what needs user confirmation, then wait. Do not drift into coding.

Boundaries

  • Prose, not code — describe what changes in prose (name the file, the concept); never include executable syntax (function bodies, JSX, SQL, migration scripts, shell commands). "Illustrative" snippets are still implementation code.
  • Right-sized artifacts — don't force heavyweight structure onto small work; don't leave plans so abstract they name no touchpoints or validation path.
  • Every plan needs a validation path — how will you know the implementation succeeded?
  • Name concrete files, interfaces, and systems where possible. Surface tradeoffs instead of hiding them.

Request

<request>$ARGUMENTS</request>

© avibebuilder, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/give-plan of avibebuilder/claude-prime.

Open the folder on GitHubat commit 80bcfa4

Compare with similar skills

Give Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Give Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Give Plan this skillavibebuilder/claude-prime120—~911Automated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills103k6 repos~3.8kAutomated safety check: PassMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec71k1 repos~4.5kAutomated safety check: PassMIT
Writing Plansgeeksblabla/stateofdev.ma16357 repos~661Automated safety check: PassNone
Subagent Driven DevelopmentAsvarox/allkaraoke26138 repos~1.2kAutomated safety check: PassNone

Similar skills

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    103k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    71k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed
  • Writing Plans

    geeksblabla/stateofdev.ma

    A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…

    163 GitHub starsUsed in 57 repos~661 tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 38 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Planning With Files

    jd-opensource/JoySafeter

    Implements Manus-style file-based planning for complex tasks.

    313 GitHub starsUsed in 19 repos~1.8k tokens
    Agent WorkflowsAuto-check: notes

More from avibebuilder/claude-prime

All 19 skills in this repo
  • Diagnose

    avibebuilder/claude-prime

    Investigate unexpected behavior and mysterious bugs. An agent skill from avibebuilder/claude-prime.

    120 GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Frontend Design

    avibebuilder/claude-prime

    Builds distinctive, production-grade UIs that avoid generic AI aesthetics.

    120 GitHub stars~2.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Media Processor

    avibebuilder/claude-prime

    Specialized visual and multimedia processing tools. An agent skill from avibebuilder/claude-prime.

    120 GitHub stars~1.2k tokensUpdated 4 mo ago
    Auto-check: notes
  • Skill Creator

    avibebuilder/claude-prime

    A skill your agent uses when the user wants to work on a Claude Code skill file (SKILL.md): writing one from scratch, testing whether an existing one works well, running evals or benchmarks…

    120 GitHub stars~8.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Self Evolve

    avibebuilder/claude-prime

    The single config quality skill. An agent skill from avibebuilder/claude-prime.

    120 GitHub stars~1.9k tokensUpdated 4 mo ago
    Auto-check passed
  • Cook

    avibebuilder/claude-prime

    Implement, build, create, or add any feature, endpoint, page, component, or functionality.

    120 GitHub stars~970 tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Give Plan

What does Give Plan do?

A skill your agent uses when the user wants a written, reviewable plan or spec produced before coding starts. Give Plan is an agent skill from avibebuilder/claude-prime. Use when the user wants a written, reviewable plan or spec produced before coding starts.

When should I use Give Plan?

Give Plan fits situations like: the user wants a written; reviewable plan; spec produced before coding starts; : mapping out changes without implementing.

How do I install Give Plan in Claude Code?

Run `npx skills add avibebuilder/claude-prime --skill give-plan -a claude-code`. Or copy the skill folder (.claude/skills/give-plan in avibebuilder/claude-prime) into .claude/skills/give-plan in your project. Claude Code loads it when a task matches its description.

How do I install Give Plan in Codex?

Run `npx skills add avibebuilder/claude-prime --skill give-plan -a codex`. Or copy the skill folder (.claude/skills/give-plan in avibebuilder/claude-prime) into .agents/skills/give-plan in your project. Codex loads it when a task matches its description.

Can I use Give Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avibebuilder/claude-prime --skill give-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/give-plan, .gemini/skills/give-plan, .github/skills/give-plan and .opencode/skills/give-plan in your project.

What does Give Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Give Plan is instructions for the agent only.

Does Give Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Give Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Give Plan use?

Give Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Give Plan use?

About 911 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Give Plan?

Skills that share tags, products or a category with Give Plan: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 103k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Give Plan?

avibebuilder (a GitHub organization) maintains it in avibebuilder/claude-prime, which has 120 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on May 16, 2026.

Source: avibebuilder/claude-prime on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.