Chapters of Plastic doctrine used by more than one skill: the knowledge graph, lifecycle and savepoints, tiers and dispatch, gates and enforcement, locks and worktrees, completion, maintenance, and roadmaps. Read a chapter when its trigger applies to the work in front of you.
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…
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.
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…
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…
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…
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.
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-- .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…
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".
Use when you have a written implementation plan to execute. Default mode is subagent-driven (at L a fresh subagent per task with two-stage review, at S and M one executor dispatch for the whole consolidated action). Fallback mode is inline execution for environments without subagent support. If…
Deep brainstorming that interviews the user relentlessly about a plan or design until reaching shared understanding. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Pair with plastic-intent-brainstorming for quick ideation and use grill-me for thorough interrogation. If…
Use when creating connections between intents, the user says "link" or "connect", or when discovering that two intents are related. Manages sources, chain, and cross-reference links.
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".
Write implementation plans from a spec. Produces plan.md, checklist.md, and at least one real actions/ACTIONN.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.
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…
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…
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…
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…
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…