@zalom/plastic 1.10.0 → 1.11.0

package/README.md

@@ -139,7 +139,7 @@ Walk this once in
 | Intent | `plastic-continuing`, `plastic-intent-creating`, `plastic-intent-starting`, `plastic-intent-brainstorming`, `plastic-intent-grilling`, `plastic-intent-speccing`, `plastic-intent-planning`, `plastic-intent-executing`, `plastic-intent-ending`, `plastic-intent-continuing`, `plastic-intent-researching` |
 | Project and delivery | `plastic-project-creating`, `plastic-project-continuing`, `plastic-roadmap`, `plastic-roadmap-continuing`, `plastic-releasing` |
 | Skill | `plastic-skill-creating`, `plastic-skill-evaluating` |
-| Product | `plastic-install`, `plastic-update`, `plastic-uninstall`, `plastic-rollback`, `plastic-doctor`, `plastic-humanizer` |
+| Product | `plastic-install`, `plastic-update`, `plastic-uninstall`, `plastic-rollback`, `plastic-doctor` |
 
 See [`docs/guides/index.md`](docs/guides/index.md) for task-oriented walkthroughs.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zalom/plastic",
-  "version": "1.10.0",
+  "version": "1.11.0",
   "description": "Intent-driven idea development system for AI coding agents",
   "type": "module",
   "bin": {

package/skills/auto/references/human-report-contract.md

@@ -57,11 +57,9 @@ CONSUMES the intent 74 report to WRITE the human briefing defined here. The two
 
 ## Brevity: point, don't repeat
 
-Surface rules (no em-dashes, plain words, no filler openers, and so on) are owned by the
-shipped `plastic-humanizer` skill and the always-on plain-language layer. This contract does not
-re-list that catalog. It restates only the hard bans as one line: no em-dashes, no "not X but Y",
-no rule of three, no hype words, no sycophancy, no over-bolding. Apply `plastic-humanizer` and the
-always-on layer for everything else.
+Surface rules are owned by the `writing-style` skill. This contract does not restate them, in full
+or in summary. It defines the report's shape only: what to say, in what order, and when to stop.
+Apply the `writing-style` skill for the wording.
 
 ## Emission: guided vs auto
 

package/skills/conventions/references/tiers-and-dispatch.md

@@ -130,6 +130,6 @@ succession at a glance (last line = where we are).
 In auto mode the orchestrator briefs the human at every lifecycle stage boundary in a fixed,
 impact-first shape (the EM-to-CTO report contract): State, then Risk, then Call. This is the
 depth at M and L; at S the briefing fires once, at How. It leads with
-what changed and why it matters, names one risk, and leaves the decision to the human. Separately,
-the `plastic-humanizer` skill cleans authored prose (specs, outcomes, READMEs, release notes) of
-AI tells and slop; it is for documents, not for every reply.
+what changed and why it matters, names one risk, and leaves the decision to the human. Wording
+rules for the briefing, and for authored prose such as specs, outcomes, READMEs, and release
+notes, are owned by the `writing-style` skill, not by this contract.

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.