--- 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 --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 `): the global board runs `--store global` and a project board runs `--store `. 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. --project ` (project override, then global, then the shipped tier default) rather than relying on bare frontmatter, which also honors a sanctioned `agents.models.` 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 --data` -> `dashboard-project.md` path still resolve. Intent 149a has landed on top of 149: the four intent lists (recently worked, active, future, next work) now render as Markdown tables. The prose demotion and the no-grid stance are unchanged, and the rule-name citations and the `dashboard.rb project --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 /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. Intent 202 has landed on top of 149/149a: the project board is short by default. The Recently-worked table and the raw Future table are both gone, replaced by a 2-3 sentence prose summary (built in `dashboard.rb`, not by this skill) plus a one-line footer stating true totals. Active is capped at 3 (ordered lifecycle-stage descending, a later savepoint breaking a tie - D2), Next-work at 5. Conversational paging ("more"/"all") re-invokes `dashboard.rb ... --data` with `--limit-active`/`--limit-next`/`--all`, carrying no state on disk; `--plain` prints the full uncapped board as plain text for a real pager. The rule-name citations and the `dashboard.rb project --data` -> `dashboard-project.md` path still resolve. ## References - `references/board-fill.md` - the template-fill mechanics and store-health surfacing detail.