What is archive-shipped-plans?

A workflow for moving completed plan files from a project’s main plans folder into a done folder and updating references to their new locations. It checks the related GitHub pull requests, which are proposed code changes, to confirm that plans were actually merged.

It is for archiving finished implementation plans, verifying their pull requests were merged, updating references, and preparing the changes in a new branch and pull request.

It keeps project planning folders tidy and prevents links from pointing to plans that have been moved.

How receptron/mulmoclaude configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to receptron/mulmoclaude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/receptron/mulmoclaude/main/.claude/skills/archive-shipped-plans/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/receptron/mulmoclaude

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/receptron/mulmoclaude/archive-shipped-plans/github.svg)](https://agentmods.dev/skills/receptron/mulmoclaude/archive-shipped-plans)

Your own site

<a href="https://agentmods.dev/skills/receptron/mulmoclaude/archive-shipped-plans"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/archive-shipped-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/receptron/mulmoclaude/archive-shipped-plans"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/archive-shipped-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,825 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00087	$0.02825
Opus 5.5	$0.00035	$0.01130
Sonnet 5.5	$0.00017	$0.00565
Haiku 4.5	$0.00009	$0.00282

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

Security

Grade A, and why

archive-shipped-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 1mo 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.

.claude/skills/archive-shipped-plans/SKILL.md · 167 lines

How it starts

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

Archive Shipped Plans

plans/ 直下のマージ済み plan ファイルを plans/done/ に移し、コード/docs/他 plan 内の plans/<name>.md 参照を全て plans/done/<name>.md に更新して PR にまとめる skill。

各 plan に対応する PR が merge 済みか / いつ merge されたか は LLM の知識・推測ではなく必ず gh pr view <num> --json mergedAt で実値を取得して判定する (LLM の日付推測は高確率で間違う)。

Defaults

repo: receptron/mulmoclaude
branch: chore/archive-shipped-plans-N (N は連番、既存があればインクリメント)
対象: plans/ 直下の *.md のみ (plans/done/, plans/decisions/, plans/i18n-audit/, plans/log-audit/ は除外)

Workflow

Step 1 — 直前 archival からの差分把握

直近の archival PR (gh pr list --search "archive plans" --state merged) を確認し、その後にマージされた PR の plan が今回の対象。

gh pr list --repo receptron/mulmoclaude --search "archive plans in:title" --state merged --limit 5 --json number,title,mergedAt

Step 2 — plan 一覧を triage

ls plans/*.md で全ファイルを列挙し、各々について done/active を判定する。

完了日と PR 番号は LLM 推測禁止。必ず以下のコマンドで実値を取得:

# ファイル名に番号 (例: feat-xxx-731.md) があるなら直接 PR を当てる
gh pr view <num> --repo receptron/mulmoclaude --json number,title,mergedAt,headRefName,body

# 番号がないなら slug 検索
gh pr list --repo receptron/mulmoclaude --search "<slug> in:title" --state all --json number,title,mergedAt,state --limit 5

ファイル名末尾の番号 (例: -731, -465) は GitHub Issue/PR 番号のはず。それを起点に検索すると速い。

Step 3 — 多 phase plan / scope drift の精査

「PR がマージされた = plan の全範囲が完了」とは限らない。本文を Read して以下を確認:

ステータス節: **Status**: ... not yet implemented などが冒頭にあれば即 active
Phase 構造: Phase 1/2/3 がある plan は、各 phase の実装状況をファイル/コード単位の証拠で個別確認:
- acceptance criteria のチェックリスト (例: 各 phase 末尾の - [ ] ... 節) を本文から抽出
- 各項目に対応する実体 (実装ファイル / docs / package / CHANGELOG エントリ等) が repo に存在するか ls / grep で確認
- 例: feat-plugin-sdk-rollout.md は Phase 2 acceptance に docs/plugin-development.md exists があるので ls docs/plugin-development.md で実体確認 → 不在なら active
- 例: feat-scheduler-phase3.md はタイトル通り Phase 3 限定 plan で OK
- 関連 issue が closed でも、acceptance 項目が repo 上で確認できないものは active 維持。「umbrella issue closed = 全 phase done」と機械的に判定するのは禁止 — issue は administrative に閉じることが多い
Non-goals 節: feat-agent-cancel-button.md の "(#731, partial)" は plan のスコープ限定の意味であって、plan 自体は完了
docs: PR は plan のみ merge の可能性: gh pr view <num> --json title でタイトルが "docs: plan for ..." なら plan を入れただけ。実装ファイルが存在するか追加チェックすること
- 例: test-top-page-regression-e2e.md (PR #672) → e2e/ に該当 spec が無く、active のまま

Read the full file on GitHub · 167 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.

1mo ago First seen · 167 lines · 87 tokens per session scan A 93b391c63a1e

Subscribe to this mod's changes

archive-shipped-plans is a skill published in the GitHub repository receptron/mulmoclaude (386 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 2,825 once invoked, about $0.0003 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-30.

Claude Code Git and workflow Project management ai-agents ai-assistant ai-native chat-ui claude

mulmoclaude: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Archive Shipped Plans

Defaults

Workflow

Step 1 — 直前 archival からの差分把握

Step 2 — plan 一覧を triage

Step 3 — 多 phase plan / scope drift の精査

What this file has done since we first saw it

Other skills, from other repositories

add-github

engineer-bot-ops

linear-cli

nav-pilot

gh-issues

github