@zalom/plastic 1.0.0-alpha.15 → 1.0.0-alpha.17

package/skills/auto/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:auto
+name: plastic-auto
 description: >-
   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
@@ -12,10 +12,22 @@ Announce: "Taking over intent [ID] — [name] for autonomous delivery."
 
 ## Precondition
 
-An active intent MUST exist in INDEX.md. If none exists, refuse: "No active intent found. Create one first with /plastic:creating-intent."
+An active intent MUST exist in INDEX.md. If none exists, refuse: "No active intent found. Create one first with /plastic-creating-intent."
 
 If multiple active intents exist, ask the user which one to deliver (this is the only question auto asks).
 
+**Picking work when no intent is specified.** If the user says "auto" without naming an
+intent and none is active, consult the dashboard's machine-readable queue to choose the
+next dispatchable intent:
+
+```bash
+ruby ~/.plastic/scripts/dashboard.rb all --json
+```
+
+Work `dispatchable_queue` in `rank` order (these are `defer`/`research` dispositions —
+safe to deliver autonomously). Leave `human_only` and `next_big_thing` for the user — those
+are `drive`/`triage` items the human should lead. See the `plastic-dashboard` skill.
+
 ## Arm the Lifecycle Gate (do this FIRST)
 
 Immediately after selecting the intent — before any other work — arm auto mode. This
@@ -86,7 +98,7 @@ If the plan calls for creating a new project (the intent is an implementation in
 1. Determine project path from `~/.plastic/config.yml` `project_roots` or from intent context
 2. **Confirm path with user** — this is the ONE human interaction during auto delivery:
    > "Creating project `<slug>` at `<path>`. Confirm path, or provide alternative."
-3. Invoke `plastic:creating-project` skill
+3. Invoke `plastic-creating-project` skill
 4. The global intent is now Completed (creating-project handles this)
 5. The tactical mirror in the project store becomes the active intent
 6. Continue execution from the project directory using the tactical intent
@@ -94,7 +106,7 @@ If the plan calls for creating a new project (the intent is an implementation in
 ## Exec Phase
 
 1. If `superpowers:subagent-driven-development` or `superpowers:executing-plans` is available, delegate execution to it
-2. Otherwise invoke `plastic:executing-plan`
+2. Otherwise invoke `plastic-executing-plan`
 3. Execute actions from checklist sequentially
 4. Check off items in `checklist.md` as completed
 5. Append observations to `## Insights` with `(autonomous)` marker
@@ -143,9 +155,9 @@ During initial project creation, all decisions are non-destructive by definition
         - `fix_and_retry` — attempt to fix the failure, re-run verify (max 2 retries)
         - `stop` — write `savepoint.md` with current state, notify user: "Verify failed — savepoint written.", **STOP**
         - `manual` — notify user: "Verify failed: [summary]. Resolve manually."
-   5. If `release.on_green` has items, invoke `plastic:releasing` to handle them (tag, changelog, publish, etc.). Do NOT duplicate release logic — delegate entirely.
+   5. If `release.on_green` has items, invoke `plastic-releasing` to handle them (tag, changelog, publish, etc.). Do NOT duplicate release logic — delegate entirely.
 5. Review `## Insights` for observations that should spawn future intents. If any:
-   - Create them (using `plastic:creating-intent` conventions)
+   - Create them (using `plastic-creating-intent` conventions)
    - Update `chain` in the current intent's frontmatter
 6. Move intent from `## Active` to `## Completed` in INDEX.md (with today's date)
 7. Auto-commit: `cd <store-root> && git add . && git commit -m "feat: deliver intent <ID> — <name>"`

package/skills/auto/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "plastic:auto",
+  "skill_name": "plastic-auto",
   "notes": "Intent 27. Scopes: description triggering (1-8) and behavior/output quality (9). Assertions written after observing Step-3 runs (one clean subagent router per case).",
   "results": {
     "triggering": { "cases": 8, "passed": 8, "pass_at_1": 1.0, "run": "2026-06-10, one subagent per case" },
@@ -9,73 +9,73 @@
     {
       "id": 1, "scope": "triggering", "set": "train",
       "prompt": "auto",
-      "expected_output": "Activates plastic:auto (the bare 'auto' keyword is the documented trigger).",
+      "expected_output": "Activates plastic-auto (the bare 'auto' keyword is the documented trigger).",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic:auto", "observed": "plastic:auto", "result": "pass" }
+        { "type": "code", "check": "router CHOICE == plastic-auto", "observed": "plastic-auto", "result": "pass" }
       ]
     },
     {
       "id": 2, "scope": "triggering", "set": "train",
       "prompt": "take it from here and deliver intent 27 end to end",
-      "expected_output": "Activates plastic:auto (autonomous delivery of an active intent).",
+      "expected_output": "Activates plastic-auto (autonomous delivery of an active intent).",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic:auto", "observed": "plastic:auto", "result": "pass" }
+        { "type": "code", "check": "router CHOICE == plastic-auto", "observed": "plastic-auto", "result": "pass" }
       ]
     },
     {
       "id": 3, "scope": "triggering", "set": "validation",
       "prompt": "go fully autonomous on the active intent, don't ask me questions",
-      "expected_output": "Activates plastic:auto.",
+      "expected_output": "Activates plastic-auto.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic:auto", "observed": "plastic:auto", "result": "pass" }
+        { "type": "code", "check": "router CHOICE == plastic-auto", "observed": "plastic-auto", "result": "pass" }
       ]
     },
     {
       "id": 4, "scope": "triggering", "set": "train",
       "prompt": "deliver this intent for me",
-      "expected_output": "Activates plastic:auto.",
+      "expected_output": "Activates plastic-auto.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic:auto", "observed": "plastic:auto", "result": "pass" }
+        { "type": "code", "check": "router CHOICE == plastic-auto", "observed": "plastic-auto", "result": "pass" }
       ]
     },
     {
       "id": 5, "scope": "triggering", "set": "train",
       "prompt": "set up a hook to automatically format the file on every save",
-      "expected_output": "Does NOT activate plastic:auto. Near-miss: shares 'auto*' but is a settings/hooks task (update-config).",
+      "expected_output": "Does NOT activate plastic-auto. Near-miss: shares 'auto*' but is a settings/hooks task (update-config).",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE != plastic:auto", "observed": "update-config", "result": "pass" }
+        { "type": "code", "check": "router CHOICE != plastic-auto", "observed": "update-config", "result": "pass" }
       ]
     },
     {
       "id": 6, "scope": "triggering", "set": "validation",
       "prompt": "deliver the built package to the dist directory",
-      "expected_output": "Does NOT activate plastic:auto. Near-miss: shares 'deliver' but is a build/file task.",
+      "expected_output": "Does NOT activate plastic-auto. Near-miss: shares 'deliver' but is a build/file task.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE != plastic:auto", "observed": "none", "result": "pass" }
+        { "type": "code", "check": "router CHOICE != plastic-auto", "observed": "none", "result": "pass" }
       ]
     },
     {
       "id": 7, "scope": "triggering", "set": "train",
       "prompt": "create a new intent for the dashboard idea",
-      "expected_output": "Does NOT activate plastic:auto; activates plastic:creating-intent.",
+      "expected_output": "Does NOT activate plastic-auto; activates plastic-creating-intent.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE != plastic:auto", "observed": "plastic:creating-intent", "result": "pass" }
+        { "type": "code", "check": "router CHOICE != plastic-auto", "observed": "plastic-creating-intent", "result": "pass" }
       ]
     },
     {
       "id": 8, "scope": "triggering", "set": "validation",
       "prompt": "what's the status of my active intents?",
-      "expected_output": "Does NOT activate plastic:auto; this is a read/continuing/managing-index query.",
+      "expected_output": "Does NOT activate plastic-auto; this is a read/continuing/managing-index query.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE != plastic:auto", "observed": "plastic:managing-index", "result": "pass" }
+        { "type": "code", "check": "router CHOICE != plastic-auto", "observed": "plastic-managing-index", "result": "pass" }
       ]
     },
     {

package/skills/auto/references/agent-architecture.md

@@ -37,7 +37,7 @@ Rules:
 
 Human owns What and Why for human-initiated intents. Agent assists (research,
 exploration) but human drives until handoff. When Why is complete — or human
-triggers `plastic:auto` — the agent takes over How and Exec autonomously.
+triggers `plastic-auto` — the agent takes over How and Exec autonomously.
 
 - **Safe-by-default:** Agent always prefers non-destructive routes (rename vs
   delete, additive migrations, backups before changes). Destructive actions on

package/skills/brainstorming/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:brainstorming
+name: plastic-brainstorming
 description: "Explore intent requirements and design before implementation. Produces spec.md in the active intent directory."
 ---
 
@@ -20,7 +20,7 @@ Do NOT invoke any implementation skill, write any code, scaffold any project, or
 Before proceeding, resolve the active intent:
 
 1. **Detect store:** Read `~/.plastic/projects.yml`, match CWD against registered project paths. If match → project store at `~/.plastic/projects/{slug}/store/`. If no match → global store at `~/.plastic/store/`.
-2. **Find active intent:** Read `INDEX.md` from the detected store. Look under `## Active`. If exactly one → use it. If multiple → ask which. If none → refuse: "No active intent. Create one first with /plastic:creating-intent"
+2. **Find active intent:** Read `INDEX.md` from the detected store. Look under `## Active`. If exactly one → use it. If multiple → ask which. If none → refuse: "No active intent. Create one first with /plastic-creating-intent"
 3. **Resolve intent directory:** `{store}/store/{id}--{slug}/`
 
 All artifacts go to the intent directory. Never write to external paths.
@@ -40,7 +40,7 @@ You MUST create a task for each of these items and complete them in order:
 5. **Write spec** — save to `{intent_dir}/spec.md` and commit to store repo
 6. **Spec self-review** — placeholder scan, consistency, scope, ambiguity
 7. **User reviews written spec** — ask user to review before proceeding
-8. **Transition to planning** — invoke `plastic:writing-plans`
+8. **Transition to planning** — invoke `plastic-writing-plans`
 
 ## Process Flow
 
@@ -54,7 +54,7 @@ digraph brainstorming {
     "Write spec" [shape=box];
     "Spec self-review\n(fix inline)" [shape=box];
     "User reviews spec?" [shape=diamond];
-    "Invoke plastic:writing-plans" [shape=doublecircle];
+    "Invoke plastic-writing-plans" [shape=doublecircle];
 
     "Explore project context" -> "Ask clarifying questions";
     "Ask clarifying questions" -> "Propose 2-3 approaches";
@@ -65,11 +65,11 @@ digraph brainstorming {
     "Write spec" -> "Spec self-review\n(fix inline)";
     "Spec self-review\n(fix inline)" -> "User reviews spec?";
     "User reviews spec?" -> "Write spec" [label="changes requested"];
-    "User reviews spec?" -> "Invoke plastic:writing-plans" [label="approved"];
+    "User reviews spec?" -> "Invoke plastic-writing-plans" [label="approved"];
 }
 ```
 
-**The terminal state is invoking `plastic:writing-plans`.** Do NOT invoke any other implementation skill. The ONLY skill you invoke after brainstorming is `plastic:writing-plans`.
+**The terminal state is invoking `plastic-writing-plans`.** Do NOT invoke any other implementation skill. The ONLY skill you invoke after brainstorming is `plastic-writing-plans`.
 
 ## The Process
 
@@ -130,8 +130,8 @@ After the spec review loop passes, ask the user to review the written spec befor
 Wait for the user's response. If they request changes, make them and re-run the spec review loop. Only proceed once the user approves.
 
 **Implementation:**
-- Invoke `plastic:writing-plans` to create the implementation plan
-- Do NOT invoke any other skill. `plastic:writing-plans` is the next step.
+- Invoke `plastic-writing-plans` to create the implementation plan
+- Do NOT invoke any other skill. `plastic-writing-plans` is the next step.
 
 ## Key Principles
 

package/skills/brainstorming-grill-me/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:brainstorming-grill-me
+name: plastic-brainstorming-grill-me
 description: >-
   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".
@@ -83,18 +83,18 @@ If ALL items pass, offer autonomous delivery:
 >
 > Want to grill more, or should I go autonomous?"
 
-- If human says go → invoke `plastic:auto`
+- If human says go → invoke `plastic-auto`
 - If human says grill more → continue grilling (reset to step 2)
 - If human says neither (wants to drive manually) → proceed as before (offer planning)
 
 This offer replaces the final question in Close Out ("Ready to plan implementation, or do you want another pass?"). The new options are:
-1. Go autonomous (`plastic:auto`)
+1. Go autonomous (`plastic-auto`)
 2. Grill more (continue interrogation)
 3. Plan manually (invoke `superpowers:writing-plans` or proceed with human-driven planning)
 
 ## Relationship to superpowers:brainstorming
 
-| | superpowers:brainstorming | plastic:brainstorming-grill-me |
+| | superpowers:brainstorming | plastic-brainstorming-grill-me |
 |---|---|---|
 | Speed | Quick (5-10 min) | Thorough (20-45 min) |
 | Depth | Surface-level exploration | Exhaustive decision tree |
@@ -102,4 +102,4 @@ This offer replaces the final question in Close Out ("Ready to plan implementati
 | Output | Initial spec | Battle-tested spec with all branches resolved |
 | Style | Collaborative, exploratory | Interrogative, relentless |
 
-Use `superpowers:brainstorming` to generate ideas. Use `plastic:brainstorming-grill-me` to pressure-test them.
+Use `superpowers:brainstorming` to generate ideas. Use `plastic-brainstorming-grill-me` to pressure-test them.

package/skills/continuing/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:continuing
+name: plastic-continuing
 description: Use when the user says "continue" after a /clear, or when resuming work in a new session. Reads intent state from global store (~/.plastic/) or local store, offers active intents first, then future intents, and surfaces stale intents for triage.
 ---
 
@@ -14,10 +14,22 @@ description: Use when the user says "continue" after a /clear, or when resuming
 
 1. Check `~/.plastic/INDEX.md` → global mode
 2. 
-3. If neither exists → announce "No Plastic store found. Run /plastic:install."
+3. If neither exists → announce "No Plastic store found. Run /plastic-install."
 
 ## Workflow
 
+### 0. Render the dashboard (overview)
+For the "where are we / what's next" overview, run the deterministic dashboard and show
+its output verbatim instead of hand-summarizing intents:
+
+```bash
+ruby ~/.plastic/scripts/dashboard.rb continue
+```
+
+This is the uniform, model-agnostic cockpit (active + last touched, then the Value×Effort
+matrix). Then continue with the steps below to actually resume a specific intent. See the
+`plastic-dashboard` skill for how to read the matrix.
+
 ### 1. Read INDEX.md
 Read the INDEX.md from the active store. Extract intents under `## Active` and `## Future`.
 
@@ -68,7 +80,7 @@ Last autonomous action: [last (autonomous) insight entry]
 Next step: [from checklist or savepoint]
 ```
 
-**Then:** Continue autonomous execution by invoking `plastic:auto`. The auto skill will pick up from the current lifecycle stage (it reads filesystem state to determine where to resume).
+**Then:** Continue autonomous execution by invoking `plastic-auto`. The auto skill will pick up from the current lifecycle stage (it reads filesystem state to determine where to resume).
 
 If NOT found — resume normally as described in step 3.
 
@@ -91,7 +103,7 @@ Stale future intents (no action taken):
      - implement: agent builds it
      - research: agent investigates feasibility
      - ideate: agent explores the problem space
-  d) Auto — go fully autonomous (invokes plastic:auto — agent delivers the intent end-to-end)
+  d) Auto — go fully autonomous (invokes plastic-auto — agent delivers the intent end-to-end)
 ```
 
 Auto-commit all triage changes.

package/skills/creating-intent/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:creating-intent
+name: plastic-creating-intent
 description: 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.
 ---
 

package/skills/creating-project/SKILL.md

@@ -1,8 +1,8 @@
 ---
-name: plastic:creating-project
+name: plastic-creating-project
 description: >-
   Create a new project from an implementation intent. Sets up project directory,
-  git init, AGENTS.md with founding intent decisions, plastic:install --local,
+  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.
 ---
@@ -31,9 +31,9 @@ cd <project_root>/<slug>
 git init
 ```
 
-### 3. Run `plastic:install --local`
+### 3. Run `plastic-install --local`
 
-Invoke `plastic:install --local` in the project directory. This creates:
+Invoke `plastic-install --local` in the project directory. This creates:
 ```
 .plastic/
 ├── store/

package/skills/dashboard/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: plastic-dashboard
+description: 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 a deterministic Value×Effort work cockpit across the global store and all projects, and emits a machine-readable queue that auto mode consumes.
+---
+
+# Dashboard — Plastic Work Cockpit
+
+A deterministic, template-driven overview of the intent store(s). It answers three
+questions at a glance — **where we are** (active + last touched), **where we go next**
+(a Value×Effort matrix), and **how to conduct it** (a disposition verb per intent) — and
+emits a JSON manifest that `plastic-auto` reads to pick the next dispatchable intent.
+
+The script does the rendering. The LLM is **never** in the rendering path: same store
+state → byte-identical output, regardless of model. Do not hand-summarize intents when
+this skill applies — run the script and show its output verbatim.
+
+## When to Use
+
+- User invokes `/plastic-dashboard`
+- User asks "where are we", "what's next", "what should I work on", "show me the intents"
+- `plastic-continuing` embeds the `continue` view on resume
+- `plastic-auto` reads `--json` to choose the next dispatchable intent
+
+## Procedure
+
+### Step 1 — Run the script
+
+```bash
+ruby ~/.plastic/scripts/dashboard.rb [continue|project <slug>|all] [--json]
+```
+
+| Mode | Shows |
+|------|-------|
+| `continue` (default) | Cross-scope: active + last touched, then the Value×Effort matrix for all scopes |
+| `project <slug>` | One project: active line + its Value×Effort matrix |
+| `all` | Per-scope roll-up summary |
+| `--json` | The auto-mode manifest (any mode); machine-readable, not for humans |
+
+The script is **read-only**. Print its stdout verbatim — do not reformat, re-sort, or
+re-summarize. That is what keeps the output uniform.
+
+### Step 2 — Read the matrix
+
+```
+                 small effort          big effort
+   high value    QUICK WIN             ★ NEXT BIG THING
+   low value     DEFER → agent         TRIAGE / question
+   (type=research/exploration → RESEARCH band, regardless of quadrant)
+```
+
+Disposition verbs: `▸ drive` (human leads), `⇢ defer` (agent knocks off),
+`⊙ research` (research/explore agent), `⚑ triage` (human review / maybe abandon).
+Flags: `⇡ unblocked` (a dependency just completed), `(Nd)` stale age.
+
+### Step 3 — Act on it
+
+- **★ Next big thing** and `▸ drive` / `⚑ triage` items → the human leads (brainstorm → plan → exec).
+- `⇢ defer` and `⊙ research` items → dispatchable to agents.
+- In auto mode, read `--json` and work `dispatchable_queue` in `rank` order; leave
+  `human_only` for the user.
+
+## JSON contract
+
+```json
+{ "generated_for": "auto-mode", "scope": "<scope|all>",
+  "next_big_thing": "<id|null>",
+  "dispatchable_queue": [ {"id","scope","disposition","type","value","effort","flags","rank"} ],
+  "human_only": ["<id>", "..."] }
+```
+
+## How classification works (deterministic)
+
+- **Effort** — small for `research`/`exploration`/`bugfix`, for already-scoped intents
+  (plan/checklist exists), or deep refinement branches; big otherwise.
+- **Value** — high only for an explicit `value: high` frontmatter field, or a
+  human-authored root intent that has spawned follow-on work (`chain` non-empty); low otherwise.
+- **Override** — a `value: high|normal|low` field in an intent's frontmatter wins. This is
+  the only place model judgment enters, and only as pre-stamped data (never at render time).
+
+## Eval
+
+This skill's eval is **render the template**: run the engine against the test fixture
+store and assert byte-identical text + JSON output against the golden snapshots in
+`test/fixtures/dashboard/`. See `test/dashboard_test.rb`. If output drifts from the
+golden files without an intentional template change, the skill is broken.
+
+## Notes
+
+- Clusters (Zettelkasten grouping in INDEX.md) are intentionally **not** rendered — they
+  are orthogonal to "what to work on next."
+- Glyphs are monochrome Unicode (no emoji); they render in standard terminal emulators.
+- This is additive: it changes no core lifecycle, gate, or cycle logic.

package/skills/doctor/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:doctor
+name: plastic-doctor
 description: Use when diagnosing Plastic installation health, after updates, or when something seems broken. Runs checks and reports findings with fix options.
 ---
 
@@ -7,8 +7,8 @@ description: Use when diagnosing Plastic installation health, after updates, or
 
 ## When to Use
 
-- User invokes `/plastic:doctor`
-- After `plastic:update` completes (automatically)
+- User invokes `/plastic-doctor`
+- After `plastic-update` completes (automatically)
 - When hooks aren't firing, skills aren't loading, or something seems broken
 - When the user says "check plastic", "diagnose", "what's wrong with plastic"
 
@@ -95,7 +95,7 @@ Show the updated results.
 
 ## Post-Update Mode
 
-When invoked from `plastic:update` (not directly by the user):
+When invoked from `plastic-update` (not directly by the user):
 
 1. Run the diagnostic script as in Step 1.
 2. If all checks pass: show a single line — **"Health check: all clear."**

package/skills/evaluating-skills/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: evaluating-skills
+name: plastic-evaluating-skills
 description: >
   Evaluate Plastic skills for correctness, convention compliance, and
   progressive disclosure. Use when testing whether a skill produces good

package/skills/executing-plan/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:executing-plan
+name: plastic-executing-plan
 description: 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.
 ---
 

package/skills/install/SKILL.md

@@ -1,10 +1,28 @@
 ---
-name: plastic:install
-description: Use when initializing Plastic globally (~/.plastic/) or locally in a project. Accepts channel flags (--alpha, --beta, --latest) to select release channel. Default is --latest (stable). Global install is recommended — creates the global intent store as a git-backed repository. Local install creates .plastic/ in the current project for testing.
+name: plastic-install
+description: 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. Default is --latest (stable). Global install is recommended — creates the global intent store as a git-backed repository. Local install creates .plastic/ in the current project for testing.
 ---
 
 # Install Plastic
 
+> **Recommended path:** for a first install, run `npx @zalom/plastic@latest --claude`
+> in your shell (or `bunx @zalom/plastic@latest --claude` if you use Bun). This skill
+> exists to **re-install or repair** an existing setup from inside the agent, and to
+> drive interactive global configuration. Whenever this skill performs an install or
+> re-install, it **runs `/plastic-doctor` afterward** and reports the result.
+
+## Re-install / repair
+
+If Plastic is already installed but something is broken (skills missing, hooks not
+firing, leftover legacy plugin), re-run the installer — it is idempotent, prunes
+files that no longer ship, and removes any legacy plugin/marketplace layout:
+
+```bash
+npx @zalom/plastic@latest --claude     # or @beta / @alpha to match your channel
+```
+
+Then **run `/plastic-doctor`** and report what it found.
+
 ## Channel Flags
 
 | Flag | Behavior |
@@ -33,14 +51,14 @@ The installed version and channel are recorded in `~/.plastic/VERSION`.
 
 ### Global Install (default, recommended)
 
-Run `/plastic:install` with no arguments.
+Run `/plastic-install` with no arguments.
 
 #### Procedure
 
 **Step 1: Check for existing installation**
 
 Check if `~/.plastic/INDEX.md` exists.
-- If yes: announce "Plastic is already installed at ~/.plastic/. Run `/plastic:update` to sync core files."
+- If yes: announce "Plastic is already installed at ~/.plastic/. Run `/plastic-update` to sync core files."
 - If no: proceed with fresh install.
 
 **Step 2: Create ~/.plastic/ as a git repo**
@@ -130,13 +148,19 @@ Update `config.yml` with any additional roots.
 
 Auto-commit the config change.
 
-**Step 4: Announce**
+**Step 4: Verify with doctor**
+
+Run `/plastic-doctor` and report the result. Resolve any fixable findings before
+announcing success.
+
+**Step 5: Announce**
 
-> "Plastic installed globally at ~/.plastic/. Create your first intent with `/plastic:creating-intent`."
+> "Plastic installed globally at ~/.plastic/. Health check: [doctor summary].
+> Create your first intent with `/plastic-creating-intent`."
 
 ### Local Install (testing/legacy)
 
-Run `/plastic:install --local`.
+Run `/plastic-install --local`.
 
 #### Procedure
 
@@ -155,4 +179,4 @@ Run `/plastic:install --local`.
 
 **Step 4:** Commit in project: `git add .plastic/ && git commit -m "chore: initialize Plastic local store"`
 
-**Step 5:** Announce: "Plastic initialized locally. This is a testing/legacy mode. Consider `/plastic:install` for global mode."
+**Step 5:** Announce: "Plastic initialized locally. This is a testing/legacy mode. Consider `/plastic-install` for global mode."

package/skills/intent-curator/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:intent-curator
+name: plastic-intent-curator
 description: |
   Use when completing or reviewing intents, reorganizing the index,
   or when the intent store needs maintenance. Examples:
@@ -15,7 +15,7 @@ description: |
 
 # Intent Curator
 
-Dispatches to the `plastic:intent-curator` agent for intent store maintenance.
+Dispatches to the `plastic-intent-curator` agent for intent store maintenance.
 
 ## When to Use
 - Completing or reviewing intents
@@ -25,7 +25,7 @@ Dispatches to the `plastic:intent-curator` agent for intent store maintenance.
 
 ## Workflow
 
-Invoke the `plastic:intent-curator` agent via the Agent tool with `subagent_type: "plastic:intent-curator"`. Pass the user's request as the prompt, including:
+Invoke the `plastic-intent-curator` agent via the Agent tool with `subagent_type: "plastic-intent-curator"`. Pass the user's request as the prompt, including:
 
 1. **What to do** — complete intent, reorganize, triage stale, etc.
 2. **Which store** — global (`~/.plastic/`) or project (`.plastic/store/`)

package/skills/linking-intents/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:linking-intents
+name: plastic-linking-intents
 description: 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.
 ---
 

package/skills/managing-index/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:managing-index
+name: plastic-managing-index
 description: 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.
 ---
 

package/skills/releasing/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:releasing
+name: plastic-releasing
 description: 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"
 ---
 
@@ -197,8 +197,8 @@ A release IS a delivery. The active intent that drove this work must be complete
 To promote a release across channels, use `--promote`:
 
 ```bash
-plastic:releasing --promote beta    # promotes current alpha → beta
-plastic:releasing --promote stable  # promotes current beta → stable
+plastic-releasing --promote beta    # promotes current alpha → beta
+plastic-releasing --promote stable  # promotes current beta → stable
 ```
 
 **Promotion rules:**

package/skills/research/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:research
+name: plastic-research
 description: "Research a topic for the active intent. Agent decides shallow vs deep based on scope. Produces reports in the intent's resources/ directory."
 ---
 
@@ -14,7 +14,7 @@ Investigate a topic related to the active intent. Choose the right depth, produc
 Before proceeding, resolve the active intent:
 
 1. **Detect store:** Read `~/.plastic/projects.yml`, match CWD against registered project paths. If match → project store at `~/.plastic/projects/{slug}/store/`. If no match → global store at `~/.plastic/store/`.
-2. **Find active intent:** Read `INDEX.md` from the detected store. Look under `## Active`. If exactly one → use it. If multiple → ask which. If none → refuse: "No active intent. Create one first with /plastic:creating-intent"
+2. **Find active intent:** Read `INDEX.md` from the detected store. Look under `## Active`. If exactly one → use it. If multiple → ask which. If none → refuse: "No active intent. Create one first with /plastic-creating-intent"
 3. **Resolve intent directory:** `{store}/store/{id}--{slug}/`
 
 ## Depth Decision

package/skills/savepoint/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:savepoint
+name: plastic-savepoint
 description: Use when context is being compacted (PreCompact hook), user says "save" or "savepoint", or before ending a session. Saves the active intent's state so work can resume after /clear.
 ---