What is documenting-plans?

A guide for creating and managing PLAN documents: task lists that describe the work planned for one development session. It is part of STDD, or Spec and Test Driven Development.

Use it to break feature work into test and implementation tasks, track scope and priorities, and keep plans in the project's documentation structure.

It separates lasting requirements from the temporary steps needed to implement a particular change.

documenting-plans — Skill for Claude Code by careerchain-ys/stdd

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 careerchain-ys/stdd --skill documenting-plans

Clone the repo

git clone --depth 1 https://github.com/careerchain-ys/stdd

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/careerchain-ys/stdd/documenting-plans/github.svg)](https://agentmods.dev/skills/careerchain-ys/stdd/documenting-plans)

Your own site

<a href="https://agentmods.dev/skills/careerchain-ys/stdd/documenting-plans"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/documenting-plans/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/careerchain-ys/stdd/documenting-plans"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/documenting-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,034 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.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.02034
Opus 5.5	$0.00018	$0.00814
Sonnet 5.5	$0.00009	$0.00407
Haiku 4.5	$0.00005	$0.00203

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

Security

Grade A, and why

documenting-plans 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.

.agents/skills/documenting-plans/SKILL.md · 219 lines

How it starts

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

PLAN ドキュメントの作成・管理

STDD（Spec and Test Driven Development）方法論において、セッションごとの実装タスクを管理するPLANドキュメントを作成・管理します。

Quick Start

PLANドキュメントとは

当該セッションで行う実装のタスクを、実装可能な単位に分解したタスクリスト

エージェントは実際の作業をこのタスクリストに従って進めます。

目的

SSoT（Single Source of Truth）としてのSpecドキュメントと、フローのドキュメントを明確に分けるため

Specドキュメント: 要件・仕様の SSoT（常に最新の状態を維持）
PLANドキュメント: 当該セッションの作業計画

テンプレート

詳細なテンプレートは templates/plan.md を参照。

ドキュメント配置ルール

docs/<app>/<feature-path>/plans/[yyyy-mm-dd].md

例:

docs/<app.id>/projects/project-list/plans/2026-01-30.md
docs/<app.id>/profile/skills/plans/2026-01-30.md

作成タイミング

新規機能を実装する場合（Specドキュメントを新規作成する場合）

1. REQUIREMENTS.md作成
   ↓
2. TECH_DESIGN.md作成
   ↓
3. ステークホルダー/アーキテクトレビュー
   ↓
4. ★ PLANドキュメント作成
   - タスクはテスト・実装のみになる
   ↓
5. テスト作成 → 実装
   ↓
6. レビュー

既存機能に追加実装する場合（Specドキュメントが既に存在する場合）

1. ★ PLANドキュメント作成
   - タスクの一つとしてSpecドキュメントの更新が含まれる
   ↓
2. Specドキュメント更新（REQUIREMENTS.md、TECH_DESIGN.md）
   ↓
3. テスト・実装計画の更新に基づいてPLANドキュメントも更新
   ↓
4. テスト作成 → 実装
   ↓
5. レビュー

PLANドキュメントの構成

PLANドキュメントには以下のセクションを含める:

1. 実装スコープ

REQUIREMENTS.md / TECH_DESIGN.md のどの範囲を実装するか
P0/P1/P2 のどれを対象とするか

2. タスクリスト

テスト作成 → 実装の順序でタスクを分解:

Specドキュメント更新（既存機能の場合）
テスト作成（Red状態）: Unit → Integration → E2E
実装（Green状態）: テストに対応する実装
テスト実行・検証

3. ファイル構成

目的: 今回のセッションで作成・変更するファイルの一覧を明確にする

凡例:

（新規）: 新規作成するファイル
（既存修正）: 既存ファイルを修正
（既存維持）: 変更なし（参照のみ）

4. 実装詳細

各ファイルの実装方針を簡潔に記載:

ページコンポーネント: サーバー/クライアントコンポーネントの選択理由
Server Actions: 処理フローの概要
バリデーション: 主要なバリデーションルール
Domain層: Entity/Repository/Serviceの役割分担

注意: コード例は記載しない。詳細は実装ファイル自体を参照。

5. 実装時の注意事項

セッション中に把握した技術的な注意点を記録:

認証・セッションの制約
エラーハンドリングの方針
外部サービスとの連携方法

注意: コード例は記載しない。詳細は実装ファイル自体を参照。

6. 備考

セッション中に発生した課題や決定事項
次回セッションへの引き継ぎ事項

7. 既知の制限事項

現時点での制限
スコープ外の項目（REQUIREMENTS.mdの「Out of Scope」と連携）

セッション開始時の確認事項

STDDにおいて、エージェントは毎セッションでPLANドキュメント作成前に以下を開発者に確認すること:

1. 実装スコープの確認

Read the full file on GitHub · 219 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

templates/plan.md 6.7 KB

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.

2mo ago First seen · 219 lines · 46 tokens per session scan A ce248e9d6364

Subscribe to this mod's changes

documenting-plans is a skill published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 2,034 once invoked, about $0.0002 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.

Planning

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

systematic-debugging

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

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens