plastic

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>

Board a session onto an intent: take the lock FIRST, confirm savepoint state, ask auto or guided ONCE, then resume at the latest delivered station and run the cycle to Done. Use on `continuing --intent {id}`, when a new intent is registered and the user asks to work it, or when the user picks an intent to work. Requires the intent in INDEX `## Active`.

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".

Use when the user wants an overview of intents, asks "where are we", "what's next", "what should I work on", "show the dashboard", or invokes /plastic-dashboard. Renders the intent store(s) as Markdown prose, the global board as a narrative of work done, each project board as a short summary plus its most-valuable next work, and emits a machine-readable queue that auto mode consumes.

Use when the user wants to land on the project board, asks "what should I work on" in this project, or wants active intents plus the most-valuable next work surfaced. This is the default route of plastic-continuing for a bare "continue" with no specific intent or roadmap named. It presents state and stops without asking how to proceed - that single mode question lives in plastic-intent-starting, once the user names a specific intent to work.

Teach a new user how Plastic works through one of three hands-on tracks: deliver a first intent stage by stage, hand delivery to the agent in auto mode, or grow a founding intent into a small project with a roadmap. Use when the user says "tutorial", "teach me Plastic", "walk me through Plastic", "how do I use Plastic", or asks what Plastic can actually do before trying it on real work.

Use when initializing Plastic globally (~/.plastic/) or locally in a project, or to re-install/repair a broken installation. Accepts channel flags (--alpha, --beta, --latest) to select release channel. First install defaults to --latest (stable); reinstalls match the already-installed channel. Global install is recommended: it creates the global intent store as a git-backed repository. Local install creates .plastic/ in the current project for testing.

Use when new work begins, the user expresses a new goal, says "new intent", or no active intent exists for the current task. Creates intents in the global store (~/.plastic/store/) or in a project's store (~/.plastic/projects/{slug}/store/) depending on context.

Create a new project from an implementation intent. Sets up project directory, git init, AGENTS.md with founding intent decisions, plastic-install --local, tactical mirror, projects.yml registration, and framework scaffolding. Use when an implementation intent spawns a project, or manually by user.

Use when the user wants to continue or resume a roadmap, pick up a mid-flight delivery batch, asks "where is the roadmap", or wants to resume the batch that was shipping, including an indirect ask that never names a roadmap directly (for example "where did that batch of intents land"). This is the roadmap route of plastic-continuing: it finds the tier's mid-flight roadmap, presents its state, then asks how to proceed exactly once.

Use when the user wants to plan a delivery batch, order waves of intents, ship a batch of intents in one go, track a named collection of intents toward a goal, or asks for a "roadmap". Creates and maintains a roadmap file, a delivery-side collection of intents (the counterpart to a release), separate from INDEX.md status tracking.

Consult the advisor for expensive reasoning: one-way doors, plans, adversarial review of a plan or conclusion before an irreversible step, a deadlock after two failed attempts, or ranking several plausible options. Use when the user asks for a second opinion, a hard design decision, an architecture review, help breaking a deadlock, or says "ask the advisor". Also sets which advisor is the default when asked ("make Fable my advisor", "switch my advisor", "use the real advisor").

Use when the user hits a Plastic quirk, bug, or feature idea in a project and wants to report it back to the Plastic project. Builds a sanitized report file and a prefilled GitHub issue URL the user reviews and submits. Only the user sends.

Deliberately trips bare-pointer via a bullet-list boundary leak regression.

Deliberately trips bare-pointer via a paragraph-level keyword leak regression.

Deliberately trips the bare-pointer check with a routing-free mention.

Deliberately trips the body-budget line sub-check only, staying under the token budget.

Deliberately trips the body-budget token sub-check while staying under 500 lines.

Deliberately trips the references-depth check with a nested file.

Deliberately trips the frontmatter-validity name sub-check (bug shape from intent 158).

Deliberately trips the orphan-files check with an unrouted reference file.

Deliberately trips the frontmatter-validity user-invocable sub-check (field missing).

Use when doing X: like this, an unquoted colon that breaks strict YAML.safe_load.

A fully compliant fixture skill used to prove SkillLint's green path.

Write implementation plans from a spec. Produces plan.md, checklist.md, and at least one real actions/ACTION_N.md (every tier) in the active intent directory.

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.

Evaluate Plastic skills for correctness, convention compliance, and progressive disclosure. Use when testing whether a skill produces good outputs, verifying convention compliance after changes, running evals against skills or instructions, creating evals for a new or updated skill, checking if a description triggers correctly, or assessing whether a skill is still needed. Also use when the user says "evaluate", "test the skill", "run evals", "check conventions", or "write evals".

Use when the user says "continue", "resume", or "pick up where we left off", starts a new session and wants to keep going, asks "what should I work on", or asks a where-was-I question that never says "continue" (for example "where was I"). This is the front door for resuming work: it dispatches to plastic-intent-continuing (a specific intent named to resume), plastic-project-continuing (the default, general board landing), or plastic-roadmap-continuing (a roadmap or delivery batch named to resume).

Use when a specific intent is named to resume, by id or by description, or on `continuing --intent {id}`. Reads that intent's savepoint ledger and hands off to plastic-intent-starting. The general "continue" / new-session triggers belong to the plastic-continuing router, not here, so a bare "continue" does not settle on this skill directly. Boot (health check, core context, version, statusline) is owned by the SessionStart hook, not this skill. Does not drive work autonomously (that is plastic-auto).

Use when the user wants to remove Plastic from an agent. Runs the manifest-driven uninstaller (removes skills, hooks, statusline, and any legacy plugin layout), reports exactly what was removed and what was left behind, then gives verification steps. Optionally deletes the intent store.

Use when you have a written implementation plan to execute. Default mode is subagent-driven (dispatches fresh subagent per task with two-stage review). Fallback mode is inline execution for environments without subagent support. If superpowers:subagent-driven-development or superpowers:executing-plans are available, delegates to them.

Explore intent requirements and design before implementation, through conversational prose questions asked one at a time (no multiple-choice chips), persisting each owner ruling immediately as an insight. Produces the enriched Why (Context and Decisions) in the active intent directory; hands off to /plastic-intent-speccing for spec.md.

Use after creating, completing, or abandoning intents, when the user says "index" or "organize", or when INDEX.md needs maintenance. Curates the INDEX.md structure note.

Consolidate the enriched Why (`## Context`, `### Decisions`, `## Insights`) into `spec.md` through a deterministic, judgment-free numbered sequence. Use when the user types the command to turn the brainstorm into a spec, asks to "write the spec", "spec this intent", "consolidate into spec.md", or the active intent is at Why with enough Decisions on record to close it out. Also fires on an indirect request that never names spec.md, such as "turn what we just discussed into the contract the planner builds from." Distinct from `plastic-intent-brainstorming` (the exploration that produces the enriched Why, upstream of this skill) and `plastic-intent-planning` (turns an existing spec.md into plan.md for How, downstream of this skill).

What-stage context deposit at intent activation: run QMD discovery over the intent's chain/sources and related parked intents, and write findings to resources/discovery--<slug>.md for the Why stage to consume. Use when an intent is activated (moved from Future to Active), after the lock is armed, under it, and before Why begins. Never writes the intent file itself.