メニュー
Use when verifying or repairing an intent's savepoint ledger, when the user says "save" or "savepoint", or when a PreCompact hook fires. The ledger is written automatically by the gate hook at each lifecycle boundary; this skill only reads, verifies, and rebuilds it.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Wrap, finish, close, or mark an intent Done, delivered or abandoned. Use when completing or abandoning an intent, when a checklist reaches 100 percent and Exec is finished, or when asked to "wrap this up".
Autonomous intent delivery - agent takes over How and Exec. Use when user says "auto", "take it from here", "deliver this", or when brainstorming-grill-me concludes and user confirms autonomous execution. Requires an active intent in INDEX.md.
Use when diagnosing Plastic installation health, after updates, or when something seems broken. Runs checks and reports findings with fix options.
Use when updating Plastic. Runs the `update` verb, which reads the installed VERSION, derives its channel, queries npm dist-tags, and advances to the next version on that channel (or switches channel with a flag).
Use when merging a feature branch to main and tagging a release, bumping the version, or when the user says "release", "tag", or "ship it"
Use when completing or reviewing intents, reorganizing the index, or when the intent store needs maintenance. Examples: <example>Context: User has finished implementing a feature. user: "This intent is done, clean up the index" assistant: "I'll use the intent-curator to update the intent status and reorganize INDEX.md" <commentary>Intent lifecycle change triggers curator for index maintenance.</commentary></example> <example>Context: The intent store has grown and clusters need review. user: "Organize the intents" assistant: "I'll use the intent-curator to review clusters, flag orphans, and suggest connections" <commentary>Periodic maintenance of the Zettelkasten structure.</commentary></example>
| name | plastic-intent-savepoint |
| description | Use when verifying or repairing an intent's savepoint ledger, when the user says "save" or "savepoint", or when a PreCompact hook fires. The ledger is written automatically by the gate hook at each lifecycle boundary; this skill only reads, verifies, and rebuilds it. |
| user-invocable | false |
savepoint.md is a deterministic, append-only ledger of an intent's cycle steps, one line
per lifecycle milestone, newest at the bottom:
2026-06-16T14:02Z What 34--cycle-step-savepoints.md
2026-06-16T14:20Z Why spec.md created
2026-06-16T15:10Z How plan.md created
2026-06-16T15:11Z How checklist.md created
2026-06-16T16:40Z Exec outcome.md created
It is sugar on top of the conventions, not a source of truth. The gate hook
(hook-gate-check) writes each line automatically when a stage file is created, so there is
nothing to save by hand. State is always derivable from files-on-disk; the ledger just lets
a resuming agent read the cycle's succession from one glance (last line = where we are).
## Insights (append-only,
newest at the bottom); the byte history lives in git.Read the active store's INDEX.md and extract intents under ## Active.
savepoint.md. Confirm it exists and is non-empty.Bridge.derive_stage). If they disagree, or the file is missing/empty, the ledger has
drifted.Bridge.savepoint_phantom_lines(intent_dir) (pure, disk-only, no bridge or session
resolution; intent 134). It flags a line disk evidence contradicts: a file-landing milestone
whose file is absent or still a sentinel placeholder, a duplicate (stage, milestone) pair, or
a state line (How started / Exec started) whose stage prerequisites are absent. If it
returns any lines:
## Active): rebuild via step 3 below.## Completed/## Abandoned intent: REPORT the phantom lines and STOP. Do not
rewrite. Completed intents are immutable. A repair is available only under an explicit human
grant, following the 124a precedent: rebuild the file-landing skeleton (step 3), then
re-append the terminal Done <disposition> bookend with the disposition read from
outcome.md's disposition: frontmatter and the timestamp recovered from the merge commit or
the file's mtime, never invented.Reconstruct from the filesystem rather than hand-editing:
ruby -r ~/.plastic/scripts/lib/bridge -e \
'Bridge.rebuild_savepoint("<intent_dir>")'
This rewrites savepoint.md from the milestone files present (timestamps from mtimes),
in stage order. Safe to run anytime: the ledger is derived.
If a rebuild changed the ledger, commit it in the store repo:
cd <store-root> && git add . && git commit -m "chore: rebuild savepoint ledger — [intent]"
Never push ~/.plastic/.
references/context-management.md for the full save/continue protocol and how the
resume flow consumes the ledger.