Agent skill

Plan Sketch

by besimple-oss in besimple-oss/broccoli

Do bounded research (official docs first) and produce a high-level implementation sketch in sketch/<generated-name.md.

MITAuto-check passedDevelopment

Install Plan Sketch

skills CLI
$ npx skills add besimple-oss/broccoli --skill plan-sketch -a claude-code

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

GitHub CLI
$ gh skill install besimple-oss/broccoli plan-sketch --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/besimple-oss/broccoli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/prompt-templates/skills/plan-sketch .claude/skills/plan-sketch && 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
plan-sketch
GitHub stars
285
Token cost
~1.4k tokens
SKILL.md length
629 words
Files
3 (incl. scripts, references)
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Do bounded research (official docs first) and produce a high-level implementation sketch in sketch/<generated-name.md.

  • Works in 3 steps: A sketch markdown file (usually under… → A small, parseable Questions for user… → A machine-readable JSON Questions block…
  • You want an approach and step ordering before implementation
  • SKILL.md covers Preconditions, Output contract (required), Expected runtime and Workflow — Option A (external…, plus 1 more section
  • Runs Python scripts from its folder; calls git, python3 and claude

What it does

Plan Sketch is an agent skill from besimple-oss/broccoli. Do bounded research (official docs first) and produce a high-level implementation sketch in sketch/<generated-name.md. Use when you want an approach and step ordering before implementation.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/prompts/plan-sketch.md` and `scripts/run_plan_sketch.py`).

It sits in Development. The repository describes itself as: Broccoli turns Linear tickets into shipped PRs — powered by Claude and Codex, running on your own Google Cloud or Blaxel containers. The licence is MIT.

When your agent uses it

  • You want an approach and step ordering before implementation

Example prompts

  • “/plan-sketch”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. A sketch markdown file (usually under sketch/, or an explicit --output path if provided).
  2. A small, parseable Questions for user block in the subagent's stdout output so wrapper skills can ask the user without reading the sketch…
  3. A machine-readable JSON Questions block in stdout so wrapper skills can parse choices programmatically.

What it can do on your machine

Read from SKILL.md and the folder at commit 6cad3b9. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • python3
    • claude

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Plan Sketch loads about 1.4k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 629 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from besimple-oss/broccoli at commit 6cad3b9, republished under its MIT licence (© besimple-oss). 629 words, ~1,401 tokens.

Download SKILL.mdSave it as .claude/skills/plan-sketch/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
plan-sketch
description
Do bounded research (official docs first) and produce a high-level implementation sketch in `sketch/<generated-name>.md`. Use when you want an approach and step ordering before implementation.

Plan Sketch

Preconditions

  • Confirm you are in the intended repo: git rev-parse --show-toplevel
  • Confirm whether web browsing is allowed.
    • If browsing is blocked by sandbox/approvals, ask the user to enable/approve it.
    • If the user says "no web browsing", proceed but clearly label assumptions where "latest" matters.

Output contract (required)

plan-sketch must produce:

  1. A sketch markdown file (usually under sketch/, or an explicit --output path if provided).
  2. A small, parseable Questions for user block in the subagent's stdout output so wrapper skills can ask the user without reading the sketch content into context.
  3. A machine-readable JSON Questions block in stdout so wrapper skills can parse choices programmatically.

The Questions block must cover:

  • Any open questions / unknowns that change the plan materially.
  • Any assumptions that should be confirmed.
  • Any high-level approach forks (architecture, APIs, rollout/testing strategy, migrations).
  • If there are multiple viable implementation approaches, include an explicit choose an approach question so the user picks one before planning.

Format requirements (strict):

  • Do not print the sketch content in the response.
  • Print the sketch path (single line) and then print a Questions block bracketed by markers:
    • BEGIN_USER_QUESTIONS
    • END_USER_QUESTIONS
  • In the Questions block:
    • Start with a short instruction telling the user to answer in one batch by label/number.
    • Present all decision-steering questions at once.
    • Number questions as 1), 2), ... (not bullets).
    • For each question, include 2–4 mutually exclusive options.
    • Label options as 1a), 1b), 1c) ... (letters per question), and make the labels easy to copy/paste.
    • Put the recommended option first and include a 1-sentence rationale on the same line.
    • End the block with a single-line summary of recommended picks in the format:
      • Recommended picks (copy/paste): 1a, 2b, 3a
    • If there are no meaningful open questions, include at least 1 explicit confirmation question with options.
  • After the text Questions block, print a JSON Questions block bracketed by markers:
    • BEGIN_USER_QUESTIONS_JSON
    • END_USER_QUESTIONS_JSON
  • The JSON block must be valid JSON and include:
    • questions: array of objects with id (number or string) and options.
    • Each options entry includes label (e.g., 1a) and text.
    • Optional: recommended boolean on options and recommended_picks array at the top level.

Expected runtime

Typically runs 15–45 minutes. Callers should allow the full --timeout (default 3600s) before interrupting.

If you use --progress-log, do not tail -f it into the main context unless you must debug; prefer checking progress via log line counts (for example: wc -l <progress-log>) and/or the heartbeat counters.

Show full SKILL.md (231 more words)Show less

Workflow — Option A (external script, preferred)

Run the sketch as a standalone CLI invocation:

bash
resolve_skill_dir() {
  local name="$1"
  local repo_root=""
  repo_root="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"

  local candidates=(
    "$repo_root/.agents/skills/$name"
    "$repo_root/.claude/skills/$name"
    "$HOME/.agents/skills/$name"
    "$HOME/.codex/skills/$name"
    "$HOME/.claude/skills/$name"
  )

  for d in "${candidates[@]}"; do
    if [[ -d "$d" ]]; then
      echo "$d"
      return 0
    fi
  done

  echo "Error: skill '$name' not found in repo-scoped or user-scoped skill dirs." >&2
  return 1
}

PLAN_SKETCH_SKILL_DIR="$(resolve_skill_dir plan-sketch)"
python3 "$PLAN_SKETCH_SKILL_DIR/scripts/run_plan_sketch.py" "user's rough idea"

Flags:

  • --idea-file PATH — use a file as the idea input (useful for large/multiline inputs)
  • --output PATH — optional explicit sketch output path (default: model generates sketch/<meaningful-name>.md)
  • --cli codex|claude — override auto-detected CLI
  • --model MODEL — pass a specific model to the CLI
  • --reasoning-effort LEVEL — pass explicit reasoning effort (vhigh aliases to xhigh)
  • --timeout N — CLI invocation timeout in seconds (default: 3600)
  • --progress-log PATH — optional path to append streamed subagent output
  • --heartbeat-seconds N — heartbeat cadence in seconds (0 disables)

Default behavior:

  • When using Codex and no overrides are provided, the script uses --model gpt-5.2 with xhigh reasoning effort.
  • When using Codex, the script always runs with --sandbox danger-full-access and -a never.
  • When using Codex, the script enables live web search (--search) so it can do bounded research for unstable facts.
  • When using Claude, the script runs non-interactive with --dangerously-skip-permissions.

The script prints the output file path to stdout on success.

Workflow — Option B (inline, legacy)

  1. Open references/prompts/plan-sketch.md.
  2. Execute it using the user's rough idea as $ARGUMENTS.
  3. Do bounded web research (official docs first) for unstable facts:
    • Current CLI/tooling behavior, deprecations, APIs, pricing, supported flags, version constraints.
    • Avoid searching any secrets/PII/proprietary code. Use generic queries (vendor + product + version + error message class).
  4. Write a new sketch file under sketch/ with a meaningful kebab-case filename and report the final path.

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

Files

SKILL.md and 2 other files (scripts, references) in prompt-templates/skills/plan-sketch of besimple-oss/broccoli.

  • SKILL.md
  • references/prompts/plan-sketch.md
  • scripts/run_plan_sketch.py

Open the folder on GitHubat commit 6cad3b9

Compare with similar skills

Plan Sketch 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.

Plan Sketch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plan Sketch this skillbesimple-oss/broccoli285—~1.4kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from besimple-oss/broccoli

All 10 skills in this repo
  • Broccoli Oss GCP Deploy

    besimple-oss/broccoli

    Deploy this repository to a new Google Cloud project using the repo's existing Cloud Run, Cloud Run Jobs, Cloud SQL, Secret Manager, and Artifact Registry scripts.

    285 GitHub stars~4.1k tokensUpdated 5 mo ago
    Auto-check passed
  • Plan Critique Loop

    besimple-oss/broccoli

    Critique and revise an existing plan doc up to 3 iterations, using accept/reject triage and stopping early when no important feedback remains.

    285 GitHub stars~1.4k tokensUpdated 5 mo ago
    Auto-check passed
  • Plan Write

    besimple-oss/broccoli

    Write a detailed, self-contained implementation plan to a new Markdown file under plan/.

    285 GitHub stars~721 tokensUpdated 5 mo ago
    Auto-check passed
  • Claude Simplify Wrapper

    besimple-oss/broccoli

    Run Claude's built-in /simplify skill on BASESHA..HEAD, validate checks, and commit.

    285 GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check passed
  • Code Review Loop

    besimple-oss/broccoli

    Iterative review+fix loop for BASESHA..HEAD: generate findings, apply accepted fixes, run checks, commit, and re-review up to 3 iterations or until clean.

    285 GitHub stars~1.6k tokensUpdated 5 mo ago
    Auto-check passed
  • Dedup

    besimple-oss/broccoli

    Dedupe-only pass for BASESHA..HEAD: remove duplicate code introduced by the diff or reuse existing shared utils; applies changes + commits.

    285 GitHub stars~1.5k tokensUpdated 5 mo ago
    Auto-check passed

Categories

Questions about Plan Sketch

What does Plan Sketch do?

Do bounded research (official docs first) and produce a high-level implementation sketch in sketch/<generated-name.md. Plan Sketch is an agent skill from besimple-oss/broccoli.md.

When should I use Plan Sketch?

Plan Sketch fits situations like: you want an approach and step ordering before implementation.

How do I install Plan Sketch in Claude Code?

Run `npx skills add besimple-oss/broccoli --skill plan-sketch -a claude-code`. Or copy the skill folder (prompt-templates/skills/plan-sketch in besimple-oss/broccoli) into .claude/skills/plan-sketch in your project. Claude Code loads it when a task matches its description.

How do I install Plan Sketch in Codex?

Run `npx skills add besimple-oss/broccoli --skill plan-sketch -a codex`. Or copy the skill folder (prompt-templates/skills/plan-sketch in besimple-oss/broccoli) into .agents/skills/plan-sketch in your project. Codex loads it when a task matches its description.

Can I use Plan Sketch 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 besimple-oss/broccoli --skill plan-sketch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-sketch, .gemini/skills/plan-sketch, .github/skills/plan-sketch and .opencode/skills/plan-sketch in your project.

What does Plan Sketch need to run?

Going by SKILL.md and its folder, Plan Sketch needs Python for the scripts in its folder and the command-line tools its instructions call (git, python3 and claude). Our summary lists: Python 3.

Does Plan Sketch access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Plan Sketch 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Plan Sketch use?

Plan Sketch 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 Plan Sketch use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 907 tokens, read only when the agent opens those files.

What are the alternatives to Plan Sketch?

Skills that share tags, products or a category with Plan Sketch: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan Sketch?

besimple-oss (a GitHub organization) maintains it in besimple-oss/broccoli, which has 285 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on April 26, 2026.

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