plan-capture

plan-capture is a skill for Claude Code, Codex from SpillwaveSolutions/wiki_ticket_sdd. It costs 63 tokens per session (711 once invoked), scanned A, original, MIT.

A workflow for turning an approved development plan into a saved plan document and tracked work items. Work items are recorded tasks that can be followed through the project.

In plain words
What is it for?
Use it after plan approval to create the plan file, add its tasks to the work log, refresh roadmap and search indexes, and update the publish manifest.
Why use it?
It keeps an agreed plan visible in the roadmap and task list, so planned work is not lost when planning ends.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/spillwavesolutions/wiki_ticket_sdd/plan-capture
Any agent
npx skills add SpillwaveSolutions/wiki_ticket_sdd --skill plan-capture
Clone the repo
git clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sdd

Made for: Claude Code, Codex.

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 plan-capture

README.md
[![agentmods](https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/plan-capture.svg)](https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/plan-capture)
Your own site
<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/plan-capture"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/plan-capture.svg" alt="Measured on agentmods" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 711 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00063 $0.00711
Opus 5 $0.00032 $0.00356
Sonnet 5 $0.00013 $0.00142
Haiku 4.5 $0.00006 $0.00071

Measured yesterday against content hash d3a84f9c5213, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-capture 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 yesterday.

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.

.claude/skills/plan-capture/SKILL.md · 57 lines

What it actually says

Plan capture

  1. Write the approved plan as markdown. It MUST contain a ## Tasks section:

    ## Tasks
    
    - [ ] (P1) Task title
      One to three plain sentences under the checkbox become the task's
      ticket body — written for a junior dev or a PM (spec §13.4):
      what and why, no ULIDs.
      - [ ] Subtask of the task above
    

    Priority token (P0)(P3) optional, default P2. Every task gets a description line — a marker-only ticket body is a policy violation (§13.4). Plan-level prose (the why) goes in other sections and is preserved verbatim in the plan doc.

    Captured items are kind:feature by design — a plan's tasks deliver planned value. If a captured task is really a defect, retag it after capture: bin/worklog update <ulid> --kind bug.

  2. Save it to a temp file and run:

    bin/worklog plan-capture --slug <kebab-slug> --title "<plan title>" \
        --body "<epic description a junior dev/PM can read>" --file <tempfile>
    
  3. Run bin/worklog roadmap-render, then bin/worklog ia-index (refreshes sidecars, inventory, rendered Home/Sidebar/indexes, and the publish manifest so the new plan is navigable), then commit docs/plans/, docs/roadmap.md, docs/.index/, and .work/todo.jsonl together.

  4. Publish in the background — but only what bin/worklog triggers plan-capture lists. Spawn ONE background subagent (Agent tool with run_in_background) whose prompt is: run those actions (ticket-sync skill flow for the newly created items; wiki-publish for the new plan doc, key plan/<slug>), and report counts. An empty list means skip publishing. Continue implementing immediately — do NOT wait for the subagent; fold its result in when the notification arrives. If background agents are unavailable in the harness, run the listed publishes inline after the first implementation commit instead — visibility may lag but never blocks. Whichever way it runs, the publishing step ends by re-running bin/worklog ia-index and committing docs/.index/: publishing writes each page's live wiki location back into the ledger, which leaves the generated inventory stale, and the IA gates are hard — the next commit fails otherwise. One pass converges, because a wiki location is not part of the render hash.

Never append to .work/*.jsonl directly (invariant 15.4). Never overwrite an existing plan (invariant 15.8) — a changed design gets a NEW plan that supersedes the old one.

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. yesterday Changed d3a84f9c5213
  2. 5d ago First seen · 57 lines · 63 tokens per session scan A b41eae5058f2

Subscribe to this mod's changes

plan-capture is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 711 once invoked, about $0.0003 per session on Opus 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens