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

package/skills/uninstall/SKILL.md

@@ -1,48 +1,59 @@
 ---
-name: plastic:uninstall
-description: Use when the user wants to remove Plastic. Deregisters the plugin from the current agent (Claude Code, Cursor, etc.) and optionally deletes all data.
+name: plastic-uninstall
+description: 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.
 ---
 
 # Uninstall Plastic
 
-## Procedure
+The installer tracks every file it writes in a manifest, so uninstall is exact and
+leaves no orphans. Prefer running it through the CLI; this skill wraps the same
+underlying uninstaller and adds reporting + verification.
 
-### Step 1: Detect the current agent
+## Procedure
 
-Check environment variables to determine which agent is running:
-- `$CLAUDE_PLUGIN_ROOT` → Claude Code
-- `$CURSOR_PLUGIN_ROOT` → Cursor
-- Otherwise → unknown agent
+### Step 1: Run the uninstaller
 
-### Step 2: Deregister from the agent
+```bash
+npx @zalom/plastic@latest --uninstall --claude
+```
 
-**Claude Code:**
-- Remove `"plastic"` from `extraKnownMarketplaces` in `~/.claude/settings.json`
-- Remove `"plastic@plastic"` from `enabledPlugins` in `~/.claude/settings.json`
-- Announce: "Plastic deregistered from Claude Code."
+(Use `--codex` / `--hermes` / `--all` to target other agents. `bunx` works too.)
 
-**Other agents:** Provide manual instructions for their deregistration process.
+This removes, for the targeted agent:
+- all `~/.claude/skills/plastic-*/` skills
+- all `~/.claude/hooks/plastic-*` hooks (and restores any saved original statusline)
+- the `~/.claude/plastic/` state dir + manifest
+- any **legacy** plugin layout: `plugins/marketplaces/plastic`, `plugins/cache/plastic`,
+  the old nested `skills/plastic/`, and the `plastic@plastic` /
+  `extraKnownMarketplaces.plastic` / `known_marketplaces.json` registrations
 
-### Step 3: Offer the data decision
+### Step 2: Report removed vs left
 
-Present clearly:
+Relay the uninstaller's output to the user — what was **removed** and what was
+**left in place**:
+- **Left:** `~/.plastic/` (intent store, history, projects) and any non-Plastic
+  settings.json entries.
 
-```
-Plastic is deregistered from [agent name].
+### Step 3: Verify removal
 
-Your intent store at ~/.plastic/ is untouched.
+Tell the user to confirm:
 
-Would you like to delete your Plastic data now?
+```bash
+ls ~/.claude/skills | grep '^plastic-'    # → no output
+ls ~/.claude/hooks  | grep '^plastic-'    # → no output
+grep -n plastic ~/.claude/settings.json   # → no plastic hook/plugin refs
+```
 
-⚠️  WARNING: This permanently removes ALL intents, history,
-and any projects in ~/.plastic/projects/.
-This is irreversible.
+### Step 4: Offer the data decision
 
-a) Keep everything (recommended) — you can re-install Plastic later
-b) Delete everything now — removes ~/.plastic/ entirely
 ```
+Plastic is uninstalled from [agent].
+Your intent store at ~/.plastic/ is untouched.
 
-### Step 4: Execute user's choice
+Delete it too?
+  a) Keep everything (recommended) — re-install anytime with npx
+  b) Delete everything now — removes ~/.plastic/ entirely (irreversible)
+```
 
-- **Keep:** Done. Tell the user: "Your data is at ~/.plastic/. Re-install anytime with `/plastic:install`."
-- **Delete:** Run `rm -rf ~/.plastic/` and confirm: "Plastic data deleted."
+- **Keep:** "Your data is at ~/.plastic/. Re-install anytime with `npx @zalom/plastic@latest --claude`."
+- **Delete:** run `rm -rf ~/.plastic/` and confirm.

package/skills/update/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:update
+name: plastic-update
 description: Use when updating Plastic. Queries npm for available versions across all channels, presents options interactively, or accepts --alpha/--beta/--latest flags for direct update.
 ---
 
@@ -111,7 +111,7 @@ Recommendation: run /clear for a clean session with all new conventions loaded.
 
 ### Step 6: Run health check
 
-Invoke `plastic:doctor` to verify the installation is healthy after the update.
+Invoke `plastic-doctor` to verify the installation is healthy after the update.
 
 If all checks pass, show: **"Health check: all clear."**
 

package/skills/writing-instructions/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: writing-instructions
+name: plastic-writing-instructions
 description: >
   Write or restructure agent instructions, conventions files, and SKILL.md
   content using progressive disclosure and the agentskills.io specification.
@@ -122,7 +122,7 @@ Run through this checklist:
 - [ ] No explaining what the agent already knows
 
 For structured evaluation beyond this checklist (paired evals, pass rate
-tracking, regression testing), use `plastic:evaluating-skills`.
+tracking, regression testing), use `plastic-evaluating-skills`.
 
 ## Gotchas
 

package/skills/writing-plans/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic:writing-plans
+name: plastic-writing-plans
 description: "Write implementation plans from a spec. Produces plan.md, checklist.md, and actions/ in the active intent directory."
 ---
 
@@ -18,9 +18,9 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
 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}/`
-4. **Read spec:** Load `{intent_dir}/spec.md`. If no spec exists → refuse: "No spec found. Run /plastic:brainstorming first."
+4. **Read spec:** Load `{intent_dir}/spec.md`. If no spec exists → refuse: "No spec found. Run /plastic-brainstorming first."
 
 All artifacts go to the intent directory. Never write to external paths.
 
@@ -55,7 +55,7 @@ This structure informs the task decomposition. Each task should produce self-con
 ```markdown
 # [Feature Name] Implementation Plan
 
-> **For agentic workers:** Use `plastic:executing-plan` to implement this plan task-by-task.
+> **For agentic workers:** Use `plastic-executing-plan` to implement this plan task-by-task.
 
 **Goal:** [One sentence describing what this builds]
 
@@ -180,4 +180,4 @@ cd {store_root} && git add . && git commit -m "docs: plan for intent {id} — {n
 
 ## Execution Handoff
 
-Plan complete. Invoke `plastic:executing-plan` to begin execution.
+Plan complete. Invoke `plastic-executing-plan` to begin execution.

package/templates/agents.md

@@ -47,13 +47,13 @@ Plastic has its own lifecycle skills. When a Plastic skill exists for the curren
 
 | Phase | Skill | Produces |
 |-------|-------|----------|
-| What | `plastic:creating-intent` | Intent file |
-| Why | `plastic:brainstorming` | `spec.md` |
-| Why | `plastic:research` | `resources/*.md` |
-| Why | `plastic:brainstorming-grill-me` | Deep interrogation |
-| How | `plastic:writing-plans` | `plan.md`, `checklist.md`, `actions/` |
-| Exec | `plastic:executing-plan` | Code + `outcome.md` |
-| Done | `plastic:intent-curator` | Lifecycle transition |
+| What | `plastic-creating-intent` | Intent file |
+| Why | `plastic-brainstorming` | `spec.md` |
+| Why | `plastic-research` | `resources/*.md` |
+| Why | `plastic-brainstorming-grill-me` | Deep interrogation |
+| How | `plastic-writing-plans` | `plan.md`, `checklist.md`, `actions/` |
+| Exec | `plastic-executing-plan` | Code + `outcome.md` |
+| Done | `plastic-intent-curator` | Lifecycle transition |
 
 **Artifact convention:** ALL lifecycle artifacts go to the active intent directory (`store/{id}--{slug}/`). Never write specs to `docs/superpowers/specs/` or plans to `docs/superpowers/plans/`.