@zalom/plastic 1.9.0 → 1.11.0

package/skills/releasing/references/release-lines.md

@@ -20,7 +20,7 @@ green Minitest run can fully vouch for.
 
 **Beta-verified lane.** Branch, merge to the `beta` branch, publish to the npm `beta` dist-tag,
 verify in real use, then merge `beta` into `main` and cut stable. It sits on top of the existing
-promotion mechanics (`--promote beta` / `--promote stable`, linear only, see
+promotion mechanics (agent-performed channel promotion, linear only, see
 `promotion-and-tagging.md`); it names when to use them, not new machinery.
 
 ## Routing rule

package/skills/skill-creating/SKILL.md

@@ -35,8 +35,11 @@ routes each authoring task to the reference that holds the depth.
 - Build at least three evals before writing extensive docs.
 - Match determinism to fragility: a deterministic script for fragile or
   repeated mechanical steps, prose for judgment calls.
-- Imperative voice, no second person. No em-dashes or en-dashes in any shipped
-  skill or doc (use commas, periods, parentheses, colons).
+- Imperative voice, no second person. User-facing docs (README, docs/, AGENTS.md,
+  CLAUDE.md) never use em-dashes or en-dashes, and newly authored skill text avoids
+  them (use commas, periods, parentheses, colons). Existing internal files and the
+  sanctioned template emissions (templates/index.md's INDEX line shape) are not
+  violations.
 
 ## Route the authoring task to its reference
 

package/skills/store-indexing/SKILL.md

@@ -14,20 +14,20 @@ user-invocable: false
 
 ## INDEX.md Structure
 
-INDEX.md is a Zettelkasten main structure note - the brain's entry point. It has four sections:
+INDEX.md is a Zettelkasten main structure note - the brain's entry point. It has five sections:
 
 ### Active
 Intents currently being worked on. Max 1-2 for focus.
 ```markdown
 ## Active
-- [1a2 — Design Plastic](store/1a2--design-plastic-state-system/1a2.md) — decision, human
+- [1a2 — Design Plastic](store/1a2--design-plastic-state-system/1a2--design-plastic-state-system.md) — decision, human
 ```
 
 ### Future
 Intents parked for later. May be picked up by agents.
 ```markdown
 ## Future
-- [1b1 — Build Reddit KB](store/1b1--build-reddit-knowledge-base/1b1.md) — implementation, human
+- [1b1 — Build Reddit KB](store/1b1--build-reddit-knowledge-base/1b1--build-reddit-knowledge-base.md) — implementation, human
 ```
 
 ### Clusters
@@ -35,10 +35,13 @@ Topic-based groupings. Manually curated. Create a new cluster when 3+ intents sh
 ```markdown
 ## Clusters
 ### Reddit Knowledge Base
-- [1a — Research](store/1a--research-reddit-saved-posts/1a.md)
-- [1a1 — Plan](store/1a1--plan-reddit-knowledge-base/1a1.md)
+- [1a — Research](store/1a--research-reddit-saved-posts/1a--research-reddit-saved-posts.md)
+- [1a1 — Plan](store/1a1--plan-reddit-knowledge-base/1a1--plan-reddit-knowledge-base.md)
 ```
 
+### Abandoned
+Intents ended without delivery. Links preserved, never deleted.
+
 ### Completed
 All completed intents with dates. Links preserved, never deleted.
 

package/skills/store-indexing/references/zettelkasten-linking.md

@@ -14,7 +14,7 @@
    `intent:` text. Ordering is mandatory: all `sources` first (top), then all `chain`,
    frontmatter order preserved within each group. Sources never appear at the end. No
    source/chain tags, no sub-grouping.
-2. **Sources/Chain** (knowledge graph): `sources` = direct ascendants this was created from (formation, acyclic, must-load); `chain` = forward continuations and related successors (may cycle, lighter context). See `docs/concepts/how-plastic-sources-and-chains-intents.md` for the full model.
+2. **Sources/Chain** (knowledge graph): `sources` = direct ascendants this was created from (formation, acyclic, must-load); `chain` = forward continuations and related successors (may cycle, lighter context). See [`how-plastic-sources-and-chains-intents.md`](https://github.com/zalom/plastic/blob/main/docs/concepts/how-plastic-sources-and-chains-intents.md) for the full model.
 3. **Tags** (weakest) — shared tags, `project-<name>` for project membership
 
 ## When to Create a Cluster

package/skills/tutorial/references/track-1-guided.md

@@ -120,6 +120,6 @@ two, exactly the README section (or note) just delivered.
 ## Wrap and where to go next
 
 That is the full cycle once: create, board, decide, spec, plan, build, done. Read
-`docs/guides/your-first-intent-in-10-minutes.md` for the same path condensed to a single
-read, and `docs/guides/what-the-gates-are-telling-you.md` for what to do if a station denies
+[`your-first-intent-in-10-minutes.md`](https://github.com/zalom/plastic/blob/main/docs/guides/your-first-intent-in-10-minutes.md) for the same path condensed to a single
+read, and [`what-the-gates-are-telling-you.md`](https://github.com/zalom/plastic/blob/main/docs/guides/what-the-gates-are-telling-you.md) for what to do if a station denies
 an action instead of completing it.

package/skills/tutorial/references/track-2-auto.md

@@ -55,9 +55,11 @@ Checkpoint: name one thing auto will always stop and ask about, rather than deci
 
 No new command. Auto still honors every hard gate a guided session would hit: the delivery
 lock (one owner at a time), the code gate (shut until `plan.md` and `checklist.md` exist),
-and the create gate (intents only come from the tool that makes them, never hand-authored).
+the create gate (intents only come from the tool that makes them, never hand-authored), the
+links gate (a `## Links` section changes only to match the file's own frontmatter), and the
+bash gate (a shell command cannot write project code the code gate would have blocked).
 
-Checkpoint: read one gate message from the run so far and name which of the three gates it
+Checkpoint: read one gate message from the run so far and name which of the five gates it
 came from.
 
 ### 4. Reading the per-stage reports
@@ -65,7 +67,8 @@ came from.
 No new command. At each stage boundary (What, Why, How, Exec, Done) the agent briefs in a
 fixed three-line shape: State (what happened and why it matters), Risk (the one thing that
 could bite, or "nothing flagged"), and Call (the decision left to the user, or the call the
-agent is taking on its own).
+agent is taking on its own). That is the depth for a medium or large intent. A small intent
+gets one briefing, at How, folding in what the earlier stages would have said.
 
 Checkpoint: in the most recent report, point at the State line, the Risk line, and the Call
 line.
@@ -84,10 +87,10 @@ at and how that matched what was actually on disk.
 ## Wrap and where to go next
 
 Auto keeps the same stages and the same gates as guided; the only difference is who steers.
-Read `docs/guides/pick-your-mode.md` for the honest trade-off between guided and auto, and
-`docs/guides/using-plastic-with-claude-code.md` for how that choice feels day to day and how
+Read [`pick-your-mode.md`](https://github.com/zalom/plastic/blob/main/docs/guides/pick-your-mode.md) for the honest trade-off between guided and auto, and
+[`using-plastic-with-claude-code.md`](https://github.com/zalom/plastic/blob/main/docs/guides/using-plastic-with-claude-code.md) for how that choice feels day to day and how
 it connects to roadmap-driven delivery. For denial messages met along the way, read
-`docs/guides/what-the-gates-are-telling-you.md`.
+[`what-the-gates-are-telling-you.md`](https://github.com/zalom/plastic/blob/main/docs/guides/what-the-gates-are-telling-you.md).
 
 Note on terms: "guided" means the user starts each stage with a command and the agent
 narrows the thinking inside it, the same shape track 1 walked. "Manual", editing project

package/skills/tutorial/references/track-3-projects-and-roadmaps.md

@@ -106,6 +106,6 @@ waiting on a release to exist first.
 
 This is the same What, Why, How, Exec cycle from tracks 1 and 2, repeated across a project
 and gathered by a roadmap. Read
-`docs/guides/using-plastic-with-claude-code.md` for roadmap-driven delivery in more depth,
+[`using-plastic-with-claude-code.md`](https://github.com/zalom/plastic/blob/main/docs/guides/using-plastic-with-claude-code.md) for roadmap-driven delivery in more depth,
 including a real worked roadmap. For the exact roadmap file format beyond what this
 walkthrough covers, the `plastic-roadmap` skill itself is the reference.

package/skills/uninstall/SKILL.md

@@ -1,6 +1,6 @@
 ---
 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.
+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. The intent store always stays.
 user-invocable: true
 ---
 
@@ -51,7 +51,7 @@ ls ~/.claude/hooks  | grep '^plastic-'    # -> no output
 grep -n plastic ~/.claude/settings.json   # -> no plastic hook/plugin refs
 ```
 
-### Step 4: Report + offer the data decision
+### Step 4: Report
 
 Emit the reporting block, using the Step 3 checks for the verification line:
 
@@ -67,12 +67,9 @@ Then:
 ```
 Plastic is uninstalled from [agent].
 Your intent store at ~/.plastic/ is untouched.
-
-Delete it too?
-  a) Keep everything (recommended): re-install anytime with npx
-  b) Delete everything now: removes ~/.plastic/ entirely (irreversible)
 ```
 
-- **Keep:** "Your data is at ~/.plastic/. Re-install anytime with
-  `npx -y @zalom/plastic@latest install --claude` (or your channel)."
-- **Delete:** run `rm -rf ~/.plastic/` and confirm.
+Uninstall removes installed harness files only. The store at `~/.plastic/` (intents,
+history, projects, config, version ledger) always stays; no uninstall path deletes it.
+Tell the user: "Your data is at ~/.plastic/. Re-install anytime with
+`npx -y @zalom/plastic@latest install --claude` (or your channel)."

package/templates/agents.md

@@ -23,31 +23,30 @@ means preferring a detected tool's own search or navigation over a generic file
 4. **Use [[global:ID]]** to link back to the governing strategic intent
 5. **Auto-commit** all intent changes in this project's git repo
 
-## Intent Lifecycle — What→Why→How→Next
+## Intent Lifecycle — What→Why→How→Exec
 
 State is derived from filesystem conventions, not frontmatter fields:
 
 | Convention | Signal |
 |---|---|
-| `## Context` has content | Intent is permanent (not fleeting) |
-| `actions/` directory exists | Intent is actionable |
+| `## Context` has content | Intent is permanent (developed, actionable) |
 | `## Outcome` has content | Intent is done |
 
 Sections map to the lifecycle:
 - **## Intent** — What (the desire)
 - **## Context** — Why (background + ### Decisions)
-- **## Outcome** — How (the result, deliverables)
-- **## Insights** — Next (observations, raw material for future intents)
+- **## Outcome** — Exec (the result; How's deliverables are the `plan.md`, `actions/`, and `checklist.md` files)
+- **## Insights** — observations across all stages, raw material for future intents
 
 Active/Future/Completed placement is managed in INDEX.md, not in frontmatter.
 
 ## Creating Tactical Intents
 
-1. Scan `.plastic/store/` for the next sequential ID
-2. Generate ID: `~/.plastic/scripts/folgezettel-id`
-3. Create `.plastic/store/ID--slug/ID--slug.md`
-4. Set frontmatter: `id`, `intent`, `sources` (array — link to governing intent), `chain` (starts empty), `created`, `author`, `tags`
-5. Add `[[global:ID]]` backlink in `## Links`
+Create through the `plastic-intent-creating` skill, which scaffolds with one call:
+`ruby ~/.plastic/scripts/new-intent --store .plastic/store --intent "<one-line>" --slug <slug> [--sources <governing-id>]`.
+It allocates the Folgezettel ID, creates `.plastic/store/ID--slug/ID--slug.md` born
+complete, and wires the links. Never hand-author the files: the write-time create gate
+rejects an incomplete or malformed intent file.
 
 ## Lifecycle Skills
 
@@ -56,12 +55,13 @@ Plastic has its own lifecycle skills. When a Plastic skill exists for the curren
 | Phase | Skill | Produces |
 |-------|-------|----------|
 | What | `plastic-intent-creating` | Intent file |
-| Why | `plastic-intent-brainstorming` | `spec.md` |
+| Why | `plastic-intent-brainstorming` | Enriched `## Context` + `### Decisions` |
+| Why | `plastic-intent-speccing` | `spec.md` |
 | Why | `plastic-intent-researching` | `resources/*.md` |
 | Why | `plastic-intent-grilling` | Deep interrogation |
 | How | `plastic-intent-planning` | `plan.md`, `checklist.md`, `actions/` |
 | Exec | `plastic-intent-executing` | Code + `outcome.md` |
-| Done | `plastic-store-curating` | Lifecycle transition |
+| Done | `plastic-intent-ending` | 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/`.
 

package/templates/config.yml

@@ -8,7 +8,8 @@ hash_algorithm: sha256-base36
 max_slug_words: 5
 agent:
   type: claude-code
-  parallel_mode: linear
+  # read-config falls back to linear when this key is absent
+  parallel_mode: agent-teams
 architect:
   style:
 
@@ -27,14 +28,14 @@ architect:
 #       plastic-executor: sonnet
 #       plastic-enforcer: opus
 #     codex:
-#       plastic-executor: gpt-5.1-codex
+#       plastic-executor: gpt-5.6-terra
 
 # The advisor (intent 185): two consultation agents, plastic-advisor (the real
 # advisor, expensive, model fable by default) and plastic-faux-advisor (the
 # cheaper imitation, model opus by default, carrying the same reasoning
 # discipline inline). advisor.enabled defaults to enabled; missing or
-# unreadable counts as enabled (fail-open). The claude.default/primary/
-# secondary values are AGENT NAMES, never model names, so a slot can point at
+# unreadable counts as enabled (fail-open). The claude.default value is an
+# AGENT NAME, never a model name, so it can point at
 # a locally registered agent instead. Set at install time via --no-advisor /
 # --advisor, or uncomment here directly. Each agent's actual model is a plain
 # agents.models.claude.<name> override, same mechanism as any other agent.
@@ -42,6 +43,4 @@ architect:
 #   enabled: false               # skip installing both advisor agents and the
 #                                 # agent-advisor skill entirely
 #   claude:
-#     default: plastic-faux-advisor    # which agent the advisor skill routes to
-#     primary: plastic-advisor         # the real advisor slot
-#     secondary: plastic-faux-advisor  # the cheaper advisor slot
+#     default: plastic-advisor         # which agent the advisor skill routes to

package/templates/index.md

@@ -1,9 +1,9 @@
 # Index
 
 ## Active
-<!-- Line shape: `- [ID — Title](path)`. The em-dash (U+2014, not a plain hyphen)
-     between id and title is load-bearing: Bridge.intent_active? matches only that
-     shape, and a plain hyphen there fails the lock gate open (see docs/internals.md). -->
+<!-- Line shape: `- [ID — Title](path)`. Writes emit the em-dash (U+2014) between
+     id and title; readers (Bridge.index_entry_match) accept the em-dash or a plain
+     hyphen, so either form parses (see https://github.com/zalom/plastic/blob/main/docs/internals.md). -->
 (no active intents)
 
 ## Future
@@ -12,5 +12,8 @@
 ## Clusters
 (clusters emerge as intents accumulate; add headings when 3+ intents share a topic)
 
+## Abandoned
+(links preserved, never deleted)
+
 ## Completed
 (links preserved, never deleted)

package/templates/spec.md

@@ -13,7 +13,7 @@
 (the chosen approach, in prose)
 
 ## Alternatives Considered
-- <alternative> — not chosen because ...
+- <alternative>: not chosen because ...
 
 ## Decisions
 - ...

package/skills/humanizer/SKILL.md

@@ -1,40 +0,0 @@
----
-name: plastic-humanizer
-description: Use to clean authored prose so it reads human and clutter-free. Removes AI tells and slop from a document, spec, outcome, README, report, or release note. Use when the user says "humanize", "de-slop", "remove the AI tells", or "clean up the wording". For documents, not for every chat reply, and not for code.
-user-invocable: true
----
-
-# Humanizer
-
-Make writing read like a person wrote it: plain, direct, low-clutter. Run this as a pass over authored prose (specs, outcomes, README, reports). Do not run it on code or on every chat turn.
-
-## Lead (house style)
-Reframe your answers and any questions you have for me like you are speaking to a well-educated non-English native person. Reduce slang, and rarely used words and terms in the general communication. And cut all the fancy words from explanations. Technical terms and concepts are fine and need no gloss.
-
-## Voice
-Answer like a busy bartender or a senior support engineer who has seen almost every ticket. Help fast, give the fix first, earn the tip.
-
-## Job 1 - remove these surface tells
-1. Em-dashes and en-dashes - use a comma or a full stop.
-2. "Not X but Y" (and "it's not just X, it's Y").
-3. Rule of three - three items only for rhythm.
-4. Hype / AI words - delve, robust, comprehensive, seamless, leverage, crucial, unlock, landscape.
-5. Filler openers / signposting - "It's worth noting", "It's important to", "Let's dive in".
-6. Hedging pile-up - might, could, perhaps, generally, when not needed.
-7. Sycophancy - "Great question", "You're absolutely right".
-8. Over-bolding - bold only what carries weight.
-
-## Job 2 - fix the structure
-- Lead with the one main point.
-- Cut sentences that only restate.
-- Pick concrete words over abstract ones.
-- Match the user's voice when samples of their writing exist.
-
-## Process
-Write, check once against the rules above, then send. On documents, run this pass last.
-
-## Length
-Keep it short. If a sentence does not help the reader, cut it.
-
-## More
-For before/after examples, read `references/examples.md`. To make the house style always-on in chat, see `references/always-on-snippet.md`. The full 33-pattern catalog and the research behind this skill live in intent 92's `resources/`. They are background and are not loaded here.

package/skills/humanizer/evals/evals.json

@@ -1,70 +0,0 @@
-{
-  "skill_name": "plastic-humanizer",
-  "notes": "Intent 92. Cleans authored prose: removes 8 surface tells and applies structural levers (one point, cut restatement, concrete words, match voice). Triggers on document-cleanup asks, not on code. Runner is intent 76; assertions are human for now.",
-  "evals": [
-    {
-      "id": 1,
-      "scope": "trigger",
-      "set": "validation",
-      "prompt": "Humanize this README - it reads like AI wrote it.",
-      "expected_output": "Selects plastic-humanizer and runs the cleanup pass over the document.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "human",
-          "check": "plastic-humanizer is selected for a document-cleanup request",
-          "observed": "description triggers on 'humanize' / 'reads like AI' for a document",
-          "result": "pass"
-        }
-      ]
-    },
-    {
-      "id": 2,
-      "scope": "trigger",
-      "set": "validation",
-      "prompt": "Clean up the wording in this spec.",
-      "expected_output": "Selects plastic-humanizer and cleans the spec prose.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "human",
-          "check": "plastic-humanizer is selected for 'clean up the wording'",
-          "observed": "description triggers on 'clean up the wording'",
-          "result": "pass"
-        }
-      ]
-    },
-    {
-      "id": 3,
-      "scope": "non-trigger",
-      "set": "validation",
-      "prompt": "Fix the failing test in foo.rb.",
-      "expected_output": "Does NOT select plastic-humanizer; this is a code task, not prose cleanup.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "human",
-          "check": "plastic-humanizer is not selected for a code task",
-          "observed": "description scopes the skill to documents, not code",
-          "result": "pass"
-        }
-      ]
-    },
-    {
-      "id": 4,
-      "scope": "output",
-      "set": "validation",
-      "prompt": "Given a slop sample: 'It's worth noting that this is not just a fix, but a comprehensive, robust, and seamless improvement that will unlock real value.' Humanize it.",
-      "expected_output": "Cleaned text has no em-dashes and none of the 8 tells, leads with one point, and drops restatement. For example: 'This fix makes X faster.'",
-      "files": [],
-      "assertions": [
-        {
-          "type": "human",
-          "check": "output drops the 8 tells, leads with one point, cuts restatement",
-          "observed": "no em-dashes; no 'not X but Y'; no rule-of-three; no hype words; no filler opener; one load-bearing point",
-          "result": "pass"
-        }
-      ]
-    }
-  ]
-}

package/skills/humanizer/references/always-on-snippet.md

@@ -1,9 +0,0 @@
-# Always-on chat style (copy-paste)
-
-Paste this into your global `CLAUDE.md` (applies to all projects) or a project `AGENTS.md` (one project). It keeps the chat style on at near-zero cost. The full cleanup for documents is the `plastic-humanizer` skill.
-
-```
-Reframe your answers and any questions like you are speaking to a well-educated person who is not a native English speaker. Reduce slang and rarely used words. Cut fancy words from explanations. Technical terms and concepts are fine.
-
-Answer like a busy bartender or a senior support engineer who has seen almost every ticket: help fast, give the fix first, earn the tip.
-```

package/skills/humanizer/references/examples.md

@@ -1,48 +0,0 @@
-# Examples - before and after
-
-Each pair shows a tell or a slop pattern, then the fix.
-
-## 1. Em-dash
-Before: The release is ready - we just need sign-off.
-After: The release is ready. We just need sign-off.
-Why: Use a full stop or comma, not an em-dash.
-
-## 2. "Not X but Y"
-Before: This is not just a config change, it's a rethink of the flow.
-After: This change reworks the flow.
-Why: State the point directly.
-
-## 3. Rule of three
-Before: The tool is fast, robust, and powerful.
-After: The tool is fast.
-Why: Drop the list-for-rhythm; keep the claim you can back.
-
-## 4. Hype / AI word
-Before: We leverage a comprehensive caching layer to unlock performance.
-After: We cache results to make it faster.
-Why: Plain verbs and nouns.
-
-## 5. Filler opener / signposting
-Before: It's worth noting that the cache expires after five minutes.
-After: The cache expires after five minutes.
-Why: Say the thing; skip the runway.
-
-## 6. Hedging pile-up
-Before: This might possibly help reduce cost in some cases, generally.
-After: This reduces cost.
-Why: One clear claim. Add a caveat only if it is real.
-
-## 7. Sycophancy
-Before: Great question! That's a really insightful point. Here's the answer.
-After: Here's the answer.
-Why: Drop the praise; answer.
-
-## 8. Structural fix (the mush)
-Before: There are several important considerations to keep in mind when thinking about how best to approach the broad and multifaceted topic of caching, each of which carries its own trade-offs.
-After: Cache reads, not writes. Reads repeat; writes do not.
-Why: One load-bearing point. Cut the restatement and the abstract throat-clearing.
-
-## 9. Over-bolding
-Before: **Note:** the cache **expires** after **five minutes**, so **always** check it.
-After: The cache expires after five minutes, so check it first.
-Why: Bold nothing here; the sentence carries itself.