메뉴
Inspect, repair, release, or reclaim an intent's delivery lock. Use when a lock-gate deny names /plastic-lock, when resuming interrupted work after a crash, reboot, or /tmp wipe, when a lock reads held or stale, or when the user says "fix the lock", "who holds the lock", or "reclaim the lock".
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-locking |
| description | Inspect, repair, release, or reclaim an intent's delivery lock. Use when a lock-gate deny names /plastic-lock, when resuming interrupted work after a crash, reboot, or /tmp wipe, when a lock reads held or stale, or when the user says "fix the lock", "who holds the lock", or "reclaim the lock". |
| user-invocable | false |
Command-only wrapper around ~/.plastic/scripts/plastic-lock. The durable
delivery lock is a delivery.lock file in the intent directory: ownership is
session-keyed, liveness is a lease (the owner's hooks refresh the file mtime;
stale means the heartbeat is older than the TTL). The /tmp bridge is only a
cache; the lock file wins every disagreement.
Run from the project (the intent resolves from this session's bridge), or pass
--intent-dir explicitly:
| Verb | What it does | When |
|---|---|---|
who | Print a compact owner, heartbeat, claim, and delegate view from durable files only | Safe human inspection; requires --intent-dir |
status | Report the lock file, bridge cache, freshness, agreement | Always safe; run first |
fix | Idempotent repair: rebuild lock + bridge from disk truth for THIS session. Never touches a fresh foreign lock | Interrupted work, corrupted state, /tmp wiped, legacy pid locks |
release | Owner clears the lock | Ending or abandoning a boarding |
reclaim | Explicit takeover of a STALE lock; appends an audit line to savepoint.md | The owner is gone and the lease expired |
delegate | Owner registers a subagent session and optional provenance, or marks it finished/failed | Auto-mode orchestration |
ruby ~/.plastic/scripts/plastic-lock status
ruby ~/.plastic/scripts/plastic-lock who --intent-dir <store>/<id>--<slug>
ruby ~/.plastic/scripts/plastic-lock fix --intent-dir <store>/<id>--<slug>
ruby ~/.plastic/scripts/plastic-lock reclaim --intent-dir <store>/<id>--<slug>
ruby ~/.plastic/scripts/plastic-lock delegate --delegate <subagent-session-id> \
--harness codex --agent plastic-executor --model <model> --thread <thread-id>
ruby ~/.plastic/scripts/plastic-lock delegate --delegate <subagent-session-id> --status finished
When the current controller knows its provenance, fix and reclaim accept
--harness, --agent, --model, --thread, and --mode auto|guided.
Provenance is descriptive; the session remains the authorization identity.
fix exits non-zero when another session holds a FRESH lock: back off, do
not retry in a loop. status shows the owner.who is strictly read-only. It reads delivery.lock, its mtime, and claim
files; it never reads or repairs a bridge, searches transcripts, heartbeats,
or writes. Missing legacy provenance displays as Unknown rather than being
inferred.delivery.lock file mtime is the sole heartbeat and freshness truth.
Provenance timestamps do not replace it.finished or
failed. Terminal status is observational and does not remove the delegate
session from the authorization list. Finished and failed activity history is
bounded to the 20 most recent terminal entries.reclaim refuses a fresh lock. There is no silent reclaim anywhere; every
takeover is audited in the intent's savepoint.md./plastic-intent-starting, which calls the same repair internally.