completely:plan

completely:plan is a skill for Claude Code from 23ag1/completely. It costs 96 tokens per session (813 once invoked), scanned A, original, MIT.

A planning tool that breaks a feature or project into small tasks and stores the plan directly in Beads, a task-tracking system. It uses questions, alternatives, dependencies, worker instructions, and a checklist of outcomes.

In plain words
What is it for?
Use it to plan a feature or project in Beads, create an epic and worker tasks, arrange dependency waves, and define how each task will be checked.
Why use it?
It turns a broad goal into ordered, testable work without requiring a separate planning file. It makes task ownership, required context, dependencies, and human review points explicit.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the completely plugin — 8 skills, 1 agent, 3 hooks shipped together

Good fit Use it to plan a feature or project in Beads, create an epic and worker tasks, arrange dependency waves, and define how each task will be checked.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/23ag1/completely/plan
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add 23ag1/completely --skill plan
Clone the repo
git clone --depth 1 https://github.com/23ag1/completely

Made for: Claude Code.

Or install completely, the plugin that ships this one along with the rest of its 8 skills, 1 agent, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for completely:plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/23ag1/completely/plan/github.svg)](https://agentmods.dev/skills/23ag1/completely/plan)
Your own site
<a href="https://agentmods.dev/skills/23ag1/completely/plan"><img src="https://agentmods.dev/badge/skills/23ag1/completely/plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for completely:plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/23ag1/completely/plan"><img src="https://agentmods.dev/badge/skills/23ag1/completely/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00096 $0.00813
Opus 5.5 $0.00038 $0.00325
Sonnet 5.5 $0.00019 $0.00163
Haiku 4.5 $0.00010 $0.00081

Measured 2mo ago against content hash 865b48bdae39, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

completely:plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/skills/plan/SKILL.md · 41 lines

How it starts

The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan into Beads directly. Do NOT write a PLAN.md / STATE.md — the plan lives in Beads.

Method (GSD methodology, Beads-first)

  1. Discover (socratic). Ask clarifying questions ONE at a time until the goal is unambiguous; offer 2–3 approaches with trade-offs; confirm scope. If a spec is already frozen, read it instead.
  2. Decompose into atomic tasks (2–5 min each). Each task MUST carry the worker-contract: title (imperative), acceptance (observable/testable), design (approach/why), write_zone (exact files/globs), verify (the proof command), deps (other task keys). ~2–3 tasks per unit; split if a unit exceeds ~5 tasks or ~10 files (context budget). Also fill the context fields — the engine consumes them directly:
    • read_context — the exact files/interfaces the worker must READ first but won't edit (contracts, schemas, neighbouring patterns). Injected verbatim into the worker's dispatch header, so a fresh context reads exactly this instead of guessing or scanning the tree.
    • must_haves — the goal-backward checklist {truths, artifacts, key_links} the default-FAIL evaluator grades against at VERIFY. No must_haves ⇒ the evaluator has only the acceptance line.
    • requirements — requirement IDs this task covers (traceability), when the phase has them.
  3. Checkpoints. Where a human must verify/decide, add {key,title,after,how}; make downstream tasks depend on cp:<key> so the wave blocks until the human closes it.
  4. Self-check (goal-backward, GSD plan-checker's 7 dimensions). Before applying, verify: requirement coverage · task completeness (acceptance+verify present) · dependencies acyclic · artifacts wired together (not isolated) · scope within context budget · acceptance is user-observable · honors the user's frozen decisions. Fix gaps — don't apply a plan that won't reach the goal.
  5. Apply. Emit the plan as JSON and pipe it to the materializer: cat <<'PLAN' | cmpl plan-apply … PLAN. It creates the epic + tasks + deps + checkpoints + a bd swarm (native waves). Then show bd ready and bd swarm status.

Read the full file on GitHub · 41 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 41 lines · 96 tokens per session scan A 865b48bdae39

Subscribe to this mod's changes

completely:plan is a skill published in the GitHub repository 23ag1/completely (6 stars, last pushed 4mo ago), licensed MIT. It adds 96 tokens to every session and 813 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

scout-ask

Use when the working directory is a Scout vault (it has knowledge-base/ and action-items/) and the user asks about the state of a project, initiative, person, decision, meeting or open thread ("where are we on X", "what's going on with Y", "who is Z", "what's on my plate"), or what Scout knows about a topic. Do not…

Raven-Scout/Scout · 131 tokens

scout-briefing

Launch a Scout morning briefing session as a background process. Auto-detects mode (morning briefing, consolidation, or weekend briefing) from the current time and day.

Raven-Scout/Scout · 40 tokens

scout-dream

Launch a Scout dreaming session as a background process. Processes feedback, does KB deep work, and works on wishlist items.

Raven-Scout/Scout · 29 tokens

tackle-issue

Start-of-work triage in this monorepo. Trigger on: a GitHub issue number ("tackle issue 99", "work on #42", bare #N), pasted proposal/spec text ("investigate this", "pressure-test this", "scope this"), or picker phrasing ("tackle the next issue", "what should I work on"). Read-only investigation that tries to falsify…

gtapps/claude-code-hermit · 149 tokens

hermit-scribe

File a GitHub issue or post a comment on an existing issue via a GitHub App bot identity. Use when the operator says "file as a GH issue", "open an issue for PROP-NNN", "report this to the tracker", "add a comment to issue.

gtapps/claude-code-hermit · 60 tokens

stale-proposals

Audit this repository's local proposal queue for stale entries: proposals still marked proposed, deferred, or accepted even though the work already shipped, plus old proposals whose subject has become inert. Reconcile proposals against plugin changelogs and first-parent Git history, automatically resolve only…

gtapps/claude-code-hermit · 140 tokens