New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Plan Write

by besimple-oss in besimple-oss/broccoli

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

MITAuto-check passedAgent Workflows

Install Plan Write

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

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

GitHub CLI
$ gh skill install besimple-oss/broccoli plan-write --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-write .claude/skills/plan-write && 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-write
GitHub stars
286
Token cost
~721 tokens
SKILL.md length
269 words
Files
3 (incl. scripts, references)
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Open references/prompts/plan-output.md. → Provide your sketch/notes/requirements… → Ensure the prompt writes a new file… → …
  • You already have a sketch/requirements and want a plan doc before coding
  • SKILL.md covers Preconditions, Expected runtime, Workflow — Option A (external… and Workflow — Option B (inline,…
  • Runs Python scripts from its folder; calls git, python3 and claude

What it does

Plan Write is an agent skill from besimple-oss/broccoli. Write a detailed, self-contained implementation plan to a new Markdown file under plan/. Use when you already have a sketch/requirements and want a plan doc before coding.

Its SKILL.md is about 720 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-output.md` and `scripts/run_plan_write.py`).

It sits in Agent Workflows, covering Planning. 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 already have a sketch/requirements and want a plan doc before coding
  • Tasks that involve Planning

Example prompts

  • “/plan-write”

Requirements

  • Python 3

Workflow steps

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

  1. Open references/prompts/plan-output.md.
  2. Provide your sketch/notes/requirements as $ARGUMENTS.
  3. Ensure the prompt writes a new file under plan/ (kebab-case; do not overwrite).
  4. In your response, clearly state the final path you wrote (for example: plan/.md).

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 Write loads about 721 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 269 words of instructions outside code blocks.

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

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). 269 words, ~721 tokens.

Download SKILL.mdSave it as .claude/skills/plan-write/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
plan-write
description
Write a detailed, self-contained implementation plan to a new Markdown file under plan/. Use when you already have a sketch/requirements and want a plan doc before coding.

Write Plan Doc

Preconditions

  • Confirm you are in the intended repo: git rev-parse --show-toplevel
  • Do not start implementation in this skill; only write/update the plan document.
  • Plan critique is a separate step (use plan-critique-loop); plan-write does not run critique internally.

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.

Workflow — Option A (external script, preferred)

Run the plan-write 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_WRITE_SKILL_DIR="$(resolve_skill_dir plan-write)"
python3 "$PLAN_WRITE_SKILL_DIR/scripts/run_plan_write.py" sketch/<generated-name>.md

Flags:

  • --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 high reasoning effort.
  • When using Codex, the script always runs with --sandbox danger-full-access, -a never, and --search so it can do bounded official-doc research when “latest” matters.

The first positional argument can be a sketch file path (for example under sketch/) or raw sketch text. The script prints the created plan doc path to stdout on success.

Workflow — Option B (inline, legacy)

  1. Open references/prompts/plan-output.md.
  2. Provide your sketch/notes/requirements as $ARGUMENTS.
  3. Ensure the prompt writes a new file under plan/ (kebab-case; do not overwrite).
  4. In your response, clearly state the final path you wrote (for example: plan/<generated-name>.md).

© 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-write of besimple-oss/broccoli.

  • SKILL.md
  • references/prompts/plan-output.md
  • scripts/run_plan_write.py

Open the folder on GitHubat commit 6cad3b9

Compare with similar skills

Plan Write 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 Write compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plan Write this skillbesimple-oss/broccoli286—~721Automated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills102k6 repos~3.8kAutomated safety check: PassMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec71k1 repos~4.5kAutomated safety check: PassMIT
Writing Plansgeeksblabla/stateofdev.ma16356 repos~661Automated safety check: PassNone
Subagent Driven DevelopmentAsvarox/allkaraoke26137 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.

    102k 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 56 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 37 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 18 repos~1.8k tokens
    Agent WorkflowsAuto-check: notes

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.

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

    286 GitHub stars~1.4k tokensUpdated 5 mo ago
    Auto-check passed

  • Plan Sketch

    besimple-oss/broccoli

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

    286 GitHub stars~1.4k 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.

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

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

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

Categories

Questions about Plan Write

What does Plan Write do?

Write a detailed, self-contained implementation plan to a new Markdown file under plan/. Plan Write is an agent skill from besimple-oss/broccoli. Write a detailed, self-contained implementation plan to a new Markdown file under plan/.

When should I use Plan Write?

Plan Write fits situations like: you already have a sketch/requirements and want a plan doc before coding; tasks that involve Planning.

How do I install Plan Write in Claude Code?

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

How do I install Plan Write in Codex?

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

Can I use Plan Write 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-write -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-write, .gemini/skills/plan-write, .github/skills/plan-write and .opencode/skills/plan-write in your project.

What does Plan Write need to run?

Going by SKILL.md and its folder, Plan Write 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 Write 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 Write 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 Write use?

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

About 721 tokens (SKILL.md is roughly 2.9k 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 504 tokens, read only when the agent opens those files.

What are the alternatives to Plan Write?

Skills that share tags, products or a category with Plan Write: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 102k 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 Plan Write?

besimple-oss (a GitHub organization) maintains it in besimple-oss/broccoli, which has 286 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.