@zalom/plastic 1.1.1 → 1.1.3

package/skills/intent-planning/evals/evals.json

@@ -1,18 +1,18 @@
 {
   "skill_name": "plastic-intent-planning",
-  "notes": "Intent 164. New evals.json for the writing-plans skill: tier-shape enforcement (S/M inline vs L actions/) and the checklist FORM plus [ORCHESTRATOR] hard-gate item convention. All assertions are pending a real observed run per the plastic-evaluating-skills convention.",
+  "notes": "Intent 164, updated by 133a. Evals for the writing-plans skill: action-file enforcement at every tier (S/M consolidate the delivery into one real actions/ACTION_1.md, L writes one actions/ACTION_N.md per task) and the checklist FORM plus [ORCHESTRATOR] hard-gate item convention. All assertions are pending a real observed run per the plastic-evaluating-skills convention.",
   "evals": [
     {
       "id": 1,
       "scope": "behavior",
       "set": "train",
       "prompt": "spec.md is stamped Tier: M and describes a single subsystem change touching four files across two tasks. Write the plan.",
-      "expected_output": "Produces an inline plan-as-checklist: all tasks with rationale live directly in plan.md, and checklist.md mirrors the task list. No actions/ACTION_N.md files are created; the actions/ directory stays empty or absent.",
+      "expected_output": "Produces plan.md plus checklist.md plus at least one real actions/ACTION_N.md. At M the planner consolidates the whole delivery into a single actions/ACTION_1.md (it may split into a few files if that reads cleaner); the actions/ directory is never left empty or .gitkeep-only. checklist.md mirrors plan.md's task list.",
       "files": [],
       "assertions": [
         {
           "type": "code",
-          "check": "no files created under actions/ for this intent; checklist.md exists and mirrors plan.md's task list",
+          "check": "at least one real (non-empty, non-.gitkeep) file exists under actions/ for this intent; checklist.md exists and mirrors plan.md's task list",
           "result": "expect-pass"
         }
       ]
@@ -22,12 +22,12 @@
       "scope": "behavior",
       "set": "train",
       "prompt": "spec.md is stamped Tier: S and describes a single-file config change. Write the plan.",
-      "expected_output": "Produces an inline plan-as-checklist. No actions/ files are created, matching the S/M default.",
+      "expected_output": "Produces plan.md plus checklist.md plus one consolidated actions/ACTION_1.md carrying the whole ordered delivery (the steps plus the exact changes). The actions/ directory is never left empty or .gitkeep-only, matching the every-tier action-file rule.",
       "files": [],
       "assertions": [
         {
           "type": "code",
-          "check": "no files created under actions/ for this intent",
+          "check": "at least one real (non-empty, non-.gitkeep) actions/ACTION_N.md exists under actions/ for this intent; no empty or .gitkeep-only actions/ dir remains",
           "result": "expect-pass"
         }
       ]
@@ -61,6 +61,21 @@
           "result": "expect-pass"
         }
       ]
+    },
+    {
+      "id": 5,
+      "scope": "behavior",
+      "set": "validation",
+      "prompt": "spec.md is stamped Tier: S. A prior draft left actions/ with only a .gitkeep. Write the plan and its actions.",
+      "expected_output": "Writes at least one real actions/ACTION_1.md (non-empty, not the placeholder sentinel, not a .gitkeep) that consolidates the whole S-tier delivery. Leaving actions/ empty or .gitkeep-only is a plan failure that would block the How gate; the planner never does this at any tier.",
+      "files": [],
+      "assertions": [
+        {
+          "type": "code",
+          "check": "actions/ contains at least one real action file (non-empty *.md, first line not the placeholder sentinel); no .gitkeep-only or empty actions/ dir remains",
+          "result": "expect-pass"
+        }
+      ]
     }
   ]
 }

package/skills/intent-planning/references/plan-format.md

@@ -28,8 +28,9 @@ plan.md so the shape matches on the first pass.
 
 **Intent:** {id}: {name}
 
-**Tier:** S|M|L, copied from the spec's stamped `Tier:` line. S and M plans are
-inline plan-as-checklist (no `actions/`); L plans use `actions/ACTION_N.md`.
+**Tier:** S|M|L, copied from the spec's stamped `Tier:` line. Every tier produces at
+least one real `actions/ACTION_N.md`; S and M consolidate the delivery into one action
+file, L uses one `actions/ACTION_N.md` per task.
 
 ---
 ```
@@ -112,10 +113,13 @@ of tier (S, M, or L):
 
 ## actions/ACTION_N.md format
 
-L tier only. S and M plans skip this file type entirely; their tasks live
-inline in `plan.md` (see the parent SKILL.md's `## Tier shapes`).
+Every tier writes at least one real action file here (see the parent SKILL.md's
+`## Tier shapes`): S and M consolidate the whole delivery into a single
+`actions/ACTION_1.md`, L writes one file per task.
 
-One file per task. Each action is self-contained: a subagent can execute it without reading the plan.
+Each action is self-contained: a subagent (or a solo executor) can execute it without
+reading the plan. It carries the ordered steps to deliver the task plus the exact changes
+to make (for code, the anchor or `file:line` and the old/new text).
 
 ```markdown
 # Action {N}: {task title}

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

@@ -71,10 +71,11 @@ an answer given in station 3.
 
 Type `/plastic-intent-planning`.
 
-Artifact: `plan.md` and `checklist.md`. At the S tier used here, `actions/` stays empty and
-the task rationale lives inline in `plan.md` instead of separate action files; only the L
-tier (many independent tasks, dispatched in parallel) gets one `actions/ACTION_N.md` file
-per task. `checklist.md` follows a fixed form: tasks start under `## In Progress`, move to
+Artifact: `plan.md`, `checklist.md`, and at least one real `actions/ACTION_N.md`. At the S
+tier used here, the planner consolidates the whole delivery into a single
+`actions/ACTION_1.md` (the ordered steps plus the exact changes); the L tier (many
+independent tasks, dispatched in parallel) instead gets one `actions/ACTION_N.md` file per
+task. `checklist.md` follows a fixed form: tasks start under `## In Progress`, move to
 `## Completed` as they land, and a `## Session Log` table records what happened each session.
 A task that depends on an owner decision landing first (a destructive step, a structural
 ruling) gets an `[ORCHESTRATOR]` prefix and blocks every other item until that decision is