@zalom/plastic 1.1.4 → 1.1.5

package/PLASTIC.md

@@ -10,6 +10,7 @@ See `PLASTIC-reference.md` for reference material: read it on demand, it is not
 
 A directory in the store containing `{ID}--{slug}.md` and optional supporting files.
 It represents a desire: something a human or agent wants to accomplish, explore, or understand.
+The unit of work in Plastic is always an intent, never a ticket.
 
 ```
 store/

package/README.md

@@ -44,7 +44,7 @@ Plastic makes that thinking legible, resumable, and useful later.
 
 **Plastic is built for an AI-native developer, technical founder, or
 independent builder who works across multiple sessions, has ideas before
-they have tickets, and feels the cost of losing reasoning between agents,
+they have intents, and feels the cost of losing reasoning between agents,
 contexts, and days.**
 
 ## What it solves?

package/package.json

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

package/skills/roadmap/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plastic-roadmap
-description: Use when the user wants to plan a delivery batch, order waves of intents, ship a batch of tickets 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 status tracking.
+description: 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 status tracking.
 user-invocable: true
 ---
 

package/skills/roadmap-continuing/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   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 wave that was shipping, including an
   indirect ask that never names a roadmap directly (for example "where did that batch of
-  tickets land"). This is the roadmap route of plastic-continuing: it finds the tier's
+  intents land"). This is the roadmap route of plastic-continuing: it finds the tier's
   mid-flight roadmap, presents its state, then asks how to proceed exactly once.
 user-invocable: true
 ---

package/skills/roadmap-continuing/evals/evals.json

@@ -26,7 +26,7 @@
     },
     {
       "id": 3, "scope": "triggering", "set": "validation",
-      "prompt": "where did that batch of tickets land",
+      "prompt": "where did that batch of intents land",
       "expected_output": "Activates plastic-roadmap-continuing (indirect trigger: a roadmap-resume request that never names 'roadmap' or 'continue').",
       "files": [],
       "assertions": [