@zalom/plastic 1.1.0 → 1.1.2

package/skills/intent-continuing/SKILL.md

@@ -1,61 +1,42 @@
 ---
 name: plastic-intent-continuing
-description: 'Use when the user says "continue", "resume", or "pick up where we left off", or when starting a new session. Continues work with the latest project context: lands on the right dashboard, then presents choices. Boot (health check, core context, version, statusline) is owned by the SessionStart hook, not this skill. Does not drive work autonomously (that is plastic-auto).'
+description: >-
+  Use when a specific intent is named to resume, by id or by description, or on `continuing
+  --intent {id}`. Reads that intent's savepoint ledger and hands off to plastic-intent-starting.
+  The general "continue" / new-session triggers belong to the plastic-continuing router, not
+  here, so a bare "continue" does not settle on this skill directly. Boot (health check, core
+  context, version, statusline) is owned by the SessionStart hook, not this skill. Does not
+  drive work autonomously (that is plastic-auto).
 user-invocable: true
 ---
 
-# Continuing
+# Continuing (intent route)
 
-`plastic-intent-continuing` continues work. It presents the latest state via the dashboard and offers
-choices, then stops. It does NOT execute work autonomously (that is `plastic-auto`) and does
-NOT render the dashboard itself (it only invokes it).
+`plastic-intent-continuing` is the intent route of `plastic-continuing`. It resumes ONE
+specific intent by its savepoint ledger, then hands off to `plastic-intent-starting`. It does
+NOT land on a dashboard and does NOT execute work autonomously (that is `plastic-auto`); both
+of those are other routes' jobs.
 
 **Boot is not this skill's job.** The `hook-session-start` hook already runs by construction on
 every session start: it runs the core health check (`doctor --core`), primes `PLASTIC.md` +
-store/project state, and prints the `Plastic Core loaded — v{version}` banner. The
+store/project state, and prints the `Plastic Core loaded - v{version}` banner. The
 `plastic-statusline` hook sets the statusline. So by the time this skill runs, core is loaded
 and healthy (or the banner already warned otherwise). This skill picks up from there and
-continues work. This is the seam future continue-flags build on (see [[39]]).
+resumes the named intent. This is the seam future continue-flags build on (see [[39]]).
 
 ## When to Use
-- UserPromptSubmit hook detects "continue" (automatic)
-- User says "continue", "resume", or "pick up where we left off"
-- Starting a new session and you want to resume work with the latest context
+- A specific intent is named to resume, by id or by description
+- `continuing --intent {id}`
 
 ## Determine Store
 
-1. **Global store** — `~/.plastic/INDEX.md` exists → global mode.
-2. **Local store** — a project store under `~/.plastic/projects/{slug}/` whose registered
+1. **Global store** - `~/.plastic/INDEX.md` exists → global mode.
+2. **Local store** - a project store under `~/.plastic/projects/{slug}/` whose registered
    path (in `~/.plastic/projects.yml`) matches the current working directory → project mode.
    The SessionStart hook already detects this; here you only need the slug to scope the
-   dashboard.
+   named intent's store.
 3. If neither exists → announce "No Plastic store found. Run /plastic-install."
 
-## Continue (present the dashboard)
-
-Land on the Markdown board via the `plastic-dashboard` skill. Rendering belongs there, not
-here — run the data payload and fill + present the matching template:
-- Project loaded → `ruby ~/.plastic/scripts/dashboard.rb project <slug> --data`
-- Otherwise → `ruby ~/.plastic/scripts/dashboard.rb continue --data`
-
-Fill the matching template from this skill's `templates/` and **present the filled Markdown
-in your reply** (every time, non-optional). If the reply does not contain the filled Markdown,
-the user sees nothing — tool-call stdout and hook `additionalContext` are both invisible to
-them. `hook-continue` also emits a one-line `systemMessage` summary as a hook-owned fallback;
-treat it as a floor only, never as a substitute for presenting the full board here. See
-`plastic-dashboard` for the fill rules and entry flow.
-
-The board load runs the scoped store check on every load (`doctor --store <scope>`): the
-global board runs `--store global` and a project board runs `--store <slug>`. The result
-arrives in the payload as `store_health`; surface it as a one-line store-health note. It is
-non-fatal (a warn or fail is shown as data, it does not block continuing).
-
-### Then stop
-Present "here is the state, what next?" and wait. Offer active intents first, then future
-intents. Do not start executing work. The branches below are the only follow-ups:
-- User/agent names a specific intent to continue → **Conditional ledger-resume** (below).
-- User says "auto" / an agent is instructed to deliver → hand to `plastic-auto`.
-
 ## Conditional Ledger-Resume
 
 Fires ONLY when the user explicitly asks to continue a SPECIFIC intent, or an agent is
@@ -98,44 +79,21 @@ For that intent's directory:
    - "advance to the next lifecycle stage" (e.g. ledger shows Why/spec.md → next is How).
    - The newest `## Insights` entry supplies human-readable context (Insights are
      append-only, newest at the bottom).
-5. **Announce and stop:**
+5. **Announce, then hand off to `plastic-intent-starting`:**
    ```
-   Resuming intent [ID] — [name]
+   Resuming intent [ID] - [name]
    Store: [global | project:<slug> | local]
    Stage: [from ledger last line]
    Next step: [first unchecked checklist item | advance to <stage>]
    Context: [newest ## Insights entry]
    Drift: [none | ledger rebuilt from filesystem]
    ```
-   Then proceed with the next step. Autonomy is `plastic-auto`'s job — if the intent's
-   `## Insights` contains `(autonomous)` entries, it was being delivered autonomously; hand
-   to `plastic-auto` to continue from the current stage.
-
-## Priority Order
-
-1. **Active intents first** — surface work in progress.
-2. **Project context** — if in a registered project, show governing + tactical intents.
-3. **Stale future intents** — surface for triage (see below).
-4. **Fresh future intents** — offer as next work.
-
-## Stale Future Intents
-
-If a future intent's `created` date is older than the configured `stale_threshold_days`
-(default 3), surface it for triage without taking action:
-
-```
-Stale future intents (no action taken):
-
-- [ID — name] (X days old)
-  a) Activate — start working on it now
-  b) Abandon — mark as abandoned
-  c) Defer to agent: implement | research | ideate
-  d) Auto — go fully autonomous (invokes plastic-auto)
-```
-
-When the user activates a future intent, move it to `## Active` in INDEX.md and auto-commit.
+   Hand off to `plastic-intent-starting`: it takes the lock, boards at this station, and is
+   where the single "auto or guided?" ask for the intent route lives, asked there exactly
+   once and never duplicated here. Its auto branch is the one that hands off to `plastic-auto`;
+   this skill never hands to `plastic-auto` directly.
 
 ## References
 
-- Read `references/context-management.md` for the full save/continue protocol and for
+- Read `references/context-management.md` for the save/continue protocol and for
   debugging the resume flow.

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

@@ -1,15 +1,15 @@
 {
   "skill_name": "plastic-intent-continuing",
-  "notes": "Intent 36, updated for 36a (boot moved into hook-session-start; the skill is now work-continuation only). Scopes: description triggering (1-8) and behavior/convention compliance of the work-continuation skill (9-14). Triggering assertions follow the plastic-auto eval style (one subagent router per case). Behavior assertions are convention checks against the SKILL.md.",
+  "notes": "Intent 158a1: slimmed to the specific-intent resume route of plastic-continuing (D8, extract not duplicate). Bare 'continue' now belongs to the router; triggering evals 1-4 were recast so this skill's positives always name a specific intent, and eval 4 asserts bare 'continue' does NOT settle here directly. Behavior eval 11 (dashboard selection) was removed, relocated to plastic-project-continuing's evals. Behavior eval 15 is new: the terminal handoff goes to plastic-intent-starting, not directly to plastic-auto. Scopes: description triggering (1-8) and behavior/convention compliance of the ledger-resume skill (9-15).",
   "results": {
-    "triggering": { "cases": 8, "passed": 8, "run": "2026-06-16, one subagent per case" },
-    "behavior": { "cases": 6, "passed": 6, "evidence": "convention checks against skills/intent-continuing/SKILL.md after the intent-36 rewrite; doctor --core verified at 0.07s with 9 liveness checks and full doctor unchanged at 30 checks" }
+    "triggering": { "cases": 8, "passed": 8, "run": "2026-07-10, one subagent per case" },
+    "behavior": { "cases": 7, "passed": 7, "evidence": "convention checks against skills/intent-continuing/SKILL.md after the 158a1 extraction" }
   },
   "evals": [
     {
       "id": 1, "scope": "triggering", "set": "train",
-      "prompt": "continue",
-      "expected_output": "Activates plastic-intent-continuing (the bare 'continue' keyword is the documented trigger).",
+      "prompt": "continue intent 4a",
+      "expected_output": "Activates plastic-intent-continuing (a specific intent named by id).",
       "files": [],
       "assertions": [
         { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
@@ -17,8 +17,8 @@
     },
     {
       "id": 2, "scope": "triggering", "set": "train",
-      "prompt": "resume where we left off",
-      "expected_output": "Activates plastic-intent-continuing.",
+      "prompt": "resume the statusline-coloring intent",
+      "expected_output": "Activates plastic-intent-continuing (a specific intent named by description).",
       "files": [],
       "assertions": [
         { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
@@ -26,8 +26,8 @@
     },
     {
       "id": 3, "scope": "triggering", "set": "validation",
-      "prompt": "pick up where we left off in this project",
-      "expected_output": "Activates plastic-intent-continuing.",
+      "prompt": "continuing --intent 96",
+      "expected_output": "Activates plastic-intent-continuing (the --intent form).",
       "files": [],
       "assertions": [
         { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
@@ -35,11 +35,11 @@
     },
     {
       "id": 4, "scope": "triggering", "set": "train",
-      "prompt": "boot plastic and show me where things stand",
-      "expected_output": "Activates plastic-intent-continuing (continuing work + presenting state is the skill's purpose; boot itself is hook-owned).",
+      "prompt": "continue",
+      "expected_output": "Does NOT settle on plastic-intent-continuing directly. Bare 'continue' with no specific intent named belongs to the plastic-continuing router, which defaults to plastic-project-continuing.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
+        { "type": "code", "check": "router CHOICE != plastic-intent-continuing", "observed": "plastic-continuing", "result": "pass" }
       ]
     },
     {
@@ -72,7 +72,7 @@
     {
       "id": 8, "scope": "triggering", "set": "validation",
       "prompt": "what's the dashboard look like right now",
-      "expected_output": "May activate plastic-dashboard rather than plastic-intent-continuing; an overview request without 'continue/resume' is a dashboard task.",
+      "expected_output": "Does NOT activate plastic-intent-continuing directly; an overview request without a specific intent named is a dashboard/project-board task.",
       "files": [],
       "assertions": [
         { "type": "code", "check": "router CHOICE != plastic-intent-continuing", "observed": "plastic-dashboard", "result": "pass" }
@@ -97,16 +97,7 @@
       ]
     },
     {
-      "id": 11, "scope": "behavior", "set": "train",
-      "prompt": "Is dashboard selection project-aware?",
-      "expected_output": "Project loaded -> `dashboard.rb project <slug>`; otherwise -> `dashboard.rb continue`. Skill only invokes, does not render.",
-      "files": ["skills/intent-continuing/SKILL.md"],
-      "assertions": [
-        { "type": "convention", "check": "both dashboard invocations present and gated on project detection", "observed": "'dashboard.rb project <slug>' and 'dashboard.rb continue' in the 'Continue (present the dashboard)' section", "result": "pass" }
-      ]
-    },
-    {
-      "id": 12, "scope": "behavior", "set": "validation",
+      "id": 11, "scope": "behavior", "set": "validation",
       "prompt": "Is ledger-resume conditional and ledger-driven?",
       "expected_output": "Resume fires only when a specific intent is named; reads savepoint.md last line as stage, verifies the stage file, rebuilds on drift, derives next step from first unchecked checklist item.",
       "files": ["skills/intent-continuing/SKILL.md"],
@@ -115,7 +106,7 @@
       ]
     },
     {
-      "id": 13, "scope": "behavior", "set": "validation",
+      "id": 12, "scope": "behavior", "set": "validation",
       "prompt": "Are the stale prose-savepoint fields gone?",
       "expected_output": "No 'In progress' / 'Blockers' fields read from a prose savepoint remain; the ledger model is used instead.",
       "files": ["skills/intent-continuing/SKILL.md"],
@@ -124,7 +115,7 @@
       ]
     },
     {
-      "id": 14, "scope": "behavior", "set": "validation",
+      "id": 13, "scope": "behavior", "set": "validation",
       "prompt": "Is the 'Determine Store' local-store gap filled?",
       "expected_output": "Step 2 of Determine Store describes local/project-store detection (no empty step).",
       "files": ["skills/intent-continuing/SKILL.md"],
@@ -133,13 +124,22 @@
       ]
     },
     {
-      "id": 15, "scope": "behavior", "set": "validation",
+      "id": 14, "scope": "behavior", "set": "validation",
       "prompt": "QMD is present. The user says: continue the work on the statusline coloring (names the intent by description, not id).",
       "expected_output": "Before scanning the store with grep/Read to locate the named intent, runs `ruby ~/.plastic/scripts/qmd-sync search \"statusline coloring\"` to surface the candidate intent, then opens the authoritative intent file for the hit it resumes. No-op fallback to INDEX.md / file scan when QMD is absent.",
       "files": ["skills/intent-continuing/SKILL.md"],
       "assertions": [
         { "type": "human", "check": "qmd-sync search is run before grep/Read when the intent is named by description; authoritative file opened for the hit", "observed": "Conditional Ledger-Resume carries the QMD-first step: run qmd-sync search before grep/Read, then open the authoritative file; no-op fallback when QMD is absent", "result": "pass" }
       ]
+    },
+    {
+      "id": 15, "scope": "behavior", "set": "train",
+      "prompt": "Does the ledger-resume's terminal handoff go to plastic-intent-starting or directly to plastic-auto?",
+      "expected_output": "Step 5 announces state then hands off to plastic-intent-starting, which takes the lock and asks 'auto or guided?' exactly once; plastic-intent-starting's own auto branch is the one that hands to plastic-auto. This skill never hands to plastic-auto directly.",
+      "files": ["skills/intent-continuing/SKILL.md"],
+      "assertions": [
+        { "type": "convention", "check": "step 5 hands off to plastic-intent-starting, not plastic-auto; the single ask is attributed to plastic-intent-starting", "observed": "present in 'Conditional Ledger-Resume' step 5", "result": "pass" }
+      ]
     }
   ]
 }

package/skills/intent-continuing/references/context-management.md

@@ -1,4 +1,4 @@
-# Context Management (Start-Save-Continue)
+# Context Management (Save, then resume-flow debugging)
 
 ## Save Point
 Triggered by PreCompact hook or manually:
@@ -7,26 +7,22 @@ Triggered by PreCompact hook or manually:
 3. Update active intent's `savepoint.md` (in-progress, next steps, blockers, discoveries)
 4. Add observations to `## Insights`
 5. Update INDEX.md
-6. Commit: `cd ~/.plastic && git add . && git commit -m "chore: savepoint — [intent name]"`
+6. Commit: `cd ~/.plastic && git add . && git commit -m "chore: savepoint - [intent name]"`
 7. Notify user to `/clear`
 
-## Continue
-Triggered by UserPromptSubmit hook when user says "continue". Priority order:
+## Debugging the resume flow
 
-**1. Active intents first (resume work):**
-1. Read INDEX.md → find active intent(s)
-2. Read active intent's `intent.md` → what and why
-3. Read active intent's `savepoint.md` → where we left off
-4. Read active intent's `checklist.md` → what's next
-5. Announce: intent name, current state, next step, blockers
-6. Resume
+When a resume looks wrong (the announced stage does not match what is on disk, or the next
+step looks stale):
 
-**2. No active intents → offer future intents:**
-1. List all future intents from INDEX.md
-2. Present them as options
-3. When user picks one, move to Active in INDEX.md
+1. Read `savepoint.md`'s last line directly; that line alone is the source of truth for stage
+   (see `SKILL.md`'s `## Conditional Ledger-Resume` for the full state table).
+2. Confirm the artifact that line implies (`plan.md`, `checklist.md`, `outcome.md`, ...) is
+   present and non-empty on disk.
+3. If the two disagree, the ledger has drifted: rebuild it rather than hand-editing:
+   `ruby -r ~/.plastic/scripts/lib/bridge -e 'Bridge.rebuild_savepoint("<intent_dir>")'`
+4. Re-read the rebuilt last line and re-derive the next step from `checklist.md`'s first
+   unchecked item.
 
-**3. Stale future intents (untouched 3+ days) → triage:**
-- **activate** — start working on it now
-- **abandon** — mark as abandoned
-- **defer to agent** — implement, research, or ideate
+The general "land on the board / priority order / stale future intents" flow now lives in
+`plastic-project-continuing`; this file no longer duplicates it.

package/skills/intent-planning/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plastic-intent-planning
-description: "Write implementation plans from a spec. Produces plan.md, checklist.md, and (L tier only) actions/ in the active intent directory."
+description: "Write implementation plans from a spec. Produces plan.md, checklist.md, and at least one real actions/ACTION_N.md (every tier) in the active intent directory."
 user-invocable: true
 ---
 
@@ -31,12 +31,12 @@ If the spec covers multiple independent subsystems, it should have been broken i
 
 ## Tier shapes
 
-Read the spec's stamped `Tier:` line (written by intent-speccing) and pick the plan shape it calls for:
+Read the spec's stamped `Tier:` line (written by intent-speccing) and pick the action shape it calls for. Every tier produces at least one REAL action file in `actions/`; the tier only changes how many:
 
-- **S or M (default):** an inline plan-as-checklist. Tasks live directly in `plan.md` with rationale inline; `checklist.md` mirrors the task list. Do NOT create any `actions/` files. Leave the `actions/` directory empty (or absent).
+- **S or M (default):** write ONE consolidated `actions/ACTION_1.md` that carries the whole ordered delivery (the steps plus the exact changes). `plan.md` still holds the overall map and `checklist.md` still mirrors the task list. You may split into a few action files when that reads cleaner, but one real action file is the floor.
 - **L (many independent tasks, dispatched in parallel):** self-contained `actions/ACTION_N.md`, one per task, each readable without the plan (see `references/plan-format.md`).
 
-Default to inline for S and M. Reserve `actions/` for L, where tasks are independent enough to hand to separate subagents in parallel. When in doubt, prefer inline; creating unnecessary `actions/` files is a plan failure at S/M tier.
+A `.gitkeep` never counts as an action, and an empty `actions/` fails the How gate at every tier. At S/M, keep it to a single consolidated action file rather than one-per-task; over-splitting a small intent is the S/M failure mode, an empty `actions/` is the tier-wide one.
 
 ## File Structure
 
@@ -97,11 +97,11 @@ If you find issues, fix them inline. No need to re-review, just fix and move on.
 ## Plastic Artifacts
 
 After writing `plan.md`, create `checklist.md` (execution registry following the
-FORM: `## In Progress`, `## Completed`, `## Session Log`) in the intent directory.
-For L tier only, also create `actions/ACTION_N.md` (one self-contained file per
-task, in an `actions/` directory inside the intent directory). For S/M tier, do
-not create `actions/` files at all (see Tier shapes above). For the exact format
-of both, read `references/plan-format.md`.
+FORM: `## In Progress`, `## Completed`, `## Session Log`) and at least one real
+`actions/ACTION_N.md` (self-contained, in an `actions/` directory inside the intent
+directory). At S/M write one consolidated `actions/ACTION_1.md`; at L write one
+`actions/ACTION_N.md` per task (see Tier shapes above). For the exact format of
+both, read `references/plan-format.md`.
 
 ## Owner-decision hard-gate items
 
@@ -118,12 +118,12 @@ When collecting owner rulings for `[ORCHESTRATOR]` hard-gate items, read
 ## Gate position
 
 - **Before:** `spec.md` exists.
-- **Produces:** `plan.md` and `checklist.md` (plus `actions/` for L tier only).
+- **Produces:** `plan.md`, `checklist.md`, and at least one real `actions/ACTION_N.md` (every tier; one consolidated file at S/M, one per task at L).
 - **Next:** /plastic-intent-executing.
 
 ## Git Commit
 
-After writing all artifacts (plan.md, checklist.md, actions/ for L tier), commit to the store:
+After writing all artifacts (plan.md, checklist.md, and the actions/ACTION_N.md files), commit to the store:
 
 ```bash
 cd {store_root} && git add . && git commit -m "docs: plan for intent {id}: {name}"

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/intent-savepoint/SKILL.md

@@ -42,6 +42,18 @@ Read the active store's `INDEX.md` and extract intents under `## Active`.
 - Confirm the **last line's stage** matches the stage derived from files-on-disk
   (`Bridge.derive_stage`). If they disagree, or the file is missing/empty, the ledger has
   drifted.
+- Run `Bridge.savepoint_phantom_lines(intent_dir)` (pure, disk-only, no bridge or session
+  resolution; intent 134). It flags a line disk evidence contradicts: a file-landing milestone
+  whose file is absent or still a sentinel placeholder, a duplicate `(stage, milestone)` pair, or
+  a state line (`How  started` / `Exec  started`) whose stage prerequisites are absent. If it
+  returns any lines:
+  - **LIVE intent (INDEX `## Active`):** rebuild via step 3 below.
+  - **INDEX `## Completed`/`## Abandoned` intent:** REPORT the phantom lines and STOP. Do not
+    rewrite. Completed intents are immutable. A repair is available only under an explicit human
+    grant, following the 124a precedent: rebuild the file-landing skeleton (step 3), then
+    re-append the terminal `Done  <disposition>` bookend with the disposition read from
+    `outcome.md`'s `disposition:` frontmatter and the timestamp recovered from the merge commit or
+    the file's mtime, never invented.
 
 ### 3. Rebuild on drift
 Reconstruct from the filesystem rather than hand-editing:

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

@@ -40,7 +40,7 @@
       "scope": "triggering",
       "set": "validation",
       "prompt": "continue",
-      "expected_output": "Does NOT activate plastic-intent-starting; bare 'continue' is plastic-intent-continuing (no specific intent named).",
+      "expected_output": "Does NOT activate plastic-intent-starting; bare 'continue' is plastic-continuing (the router, no specific intent named).",
       "files": [],
       "assertions": [
         { "type": "code", "check": "router CHOICE != plastic-intent-starting", "result": "expect-pass" }

package/skills/project-continuing/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: plastic-project-continuing
+description: >-
+  Use when the user wants to land on the project board, asks "what should I work on" in this
+  project, or wants active intents plus the most-valuable next work surfaced. This is the
+  default route of plastic-continuing for a bare "continue" with no specific intent or roadmap
+  named. It presents state and stops without asking how to proceed - that single mode question
+  lives in plastic-intent-starting, once the user names a specific intent to work.
+user-invocable: true
+---
+
+# Project Continuing - land on the board
+
+`plastic-project-continuing` is the project route of `plastic-continuing`. It lands on the
+Markdown board, presents active work and the most-valuable next work, and stops. It does not
+resume a specific intent by ledger (that is `plastic-intent-continuing`) and it asks nothing.
+
+## Continue (present the board)
+
+Land on the Markdown board via the `plastic-dashboard` skill. Rendering belongs there, not
+here - run the data payload and fill + present the matching template:
+- Project loaded -> `ruby ~/.plastic/scripts/dashboard.rb project <slug> --data`
+- Otherwise (no project loaded, the global fallback) -> `ruby ~/.plastic/scripts/dashboard.rb continue --data`
+
+Fill the matching template from `plastic-dashboard`'s `templates/` and **present the filled
+Markdown in your reply** (every time, non-optional). If the reply does not contain the filled
+Markdown, the user sees nothing - tool-call stdout and hook `additionalContext` are both
+invisible to them. `hook-continue` also emits a one-line `systemMessage` summary as a
+hook-owned fallback; treat it as a floor only, never as a substitute for presenting the full
+board here. See `plastic-dashboard` for the fill mechanics (`references/board-fill.md` has the
+scoped detail).
+
+The board load runs the scoped store check on every load (`doctor --store <scope>`): the
+global board runs `--store global` and a project board runs `--store <slug>`. The result
+arrives in the payload as `store_health`; surface it as a one-line store-health note. It is
+non-fatal (a warn or fail is shown as data, it does not block continuing).
+
+## Priority Order
+
+1. **Active intents first** - surface work in progress.
+2. **Project context** - if in a registered project, show governing + tactical intents.
+3. **Stale future intents** - surface for triage (see below).
+4. **Fresh future intents** - offer as next work.
+
+## Stale Future Intents
+
+If a future intent's `created` date is older than the configured `stale_threshold_days`
+(default 3), surface it for triage without taking action:
+
+```
+Stale future intents (no action taken):
+
+- [ID - name] (X days old)
+  a) Activate - start working on it now
+  b) Abandon - mark as abandoned
+  c) Defer to agent: implement | research | ideate
+  d) Auto - go fully autonomous (invokes plastic-auto)
+```
+
+When the user activates a future intent, move it to `## Active` in INDEX.md and auto-commit.
+
+**Defer to agent: research.** Selecting `research` is a real dispatch, not a label. Resolve
+`plastic-future-intent-researcher`'s model via `read-config agents.models.<basename> --project
+<repo>` (project override, then global, then the shipped tier default) rather than relying on
+bare frontmatter, which also honors a sanctioned `agents.models.<name>` override if one is
+configured. Dispatch the agent (Agent tool, `subagent_type: "plastic-future-intent-researcher"`)
+on the selected stale future intent, passing the resolved model explicitly. The agent writes its
+findings into that intent's `## Context` (see `agents/plastic-future-intent-researcher.md`); it
+does not itself dispatch further sub-agents. Once it returns, re-present the stale-future-intent
+triage so the user can act on the fresh findings now on record.
+
+## Deciding rules
+
+The board's ranked next-work order is deterministic, computed by `dashboard.rb`; this skill
+never re-derives it. Cite the rule NAMES only when explaining a ranking or disposition: Effort,
+Value, Flags, Override, Caps. Read `plastic-dashboard`'s `references/classification.md` for the
+definitions; do not restate or copy them here.
+
+## Then stop
+
+Present "here is the state, what next?" and wait. Offer active intents first, then future
+intents. Do not start executing work. The only follow-up from here:
+- User/agent names a specific intent to continue -> hand to `plastic-intent-continuing`
+  (which reads the ledger and, in turn, hands to `plastic-intent-starting` for the single
+  auto-or-guided ask).
+
+## Coordination
+
+Intent 149 has landed: the dashboard is demoted to prose (no Value x Effort grid). This skill
+was built against the live INDEX.md-parsing `--data` path (147, the DB cutover, has not
+landed). Its rule-name citations (`classification.md`, cited by name, not logic) and the
+`dashboard.rb project <slug> --data` -> `dashboard-project.md` path still resolve.
+
+Intent 148 landed: roadmaps are the primary planning surface. When the tier has a mid-flight
+roadmap (`ruby ~/.plastic/scripts/roadmap-next --roadmaps-dir <tier>/roadmaps` reports a `state`
+other than `none`), the roadmap route (`plastic-roadmap-continuing`) is the live surface for
+"what to work next", and `plastic-continuing` routes there. This board still presents project
+state and stops, asking nothing (unchanged): it does not itself dispatch, re-rank, or resume a
+roadmap. The global store and any project with no roadmap report `none`, so this board stays the
+default route for them.
+
+## References
+
+- `references/board-fill.md` - the template-fill mechanics and store-health surfacing detail.