plastic-dashboard

# Dashboard — Plastic Work Cockpit A deterministic overview of the intent store(s). It answers three questions at a glance: **where we are** (recently worked), **where we go next** (the most-valuable next work), and **how to conduct it** (a disposition per intent). The human-facing surface is **Markdown**, because the user's UI renders Markdown natively but collapses raw tool-call stdout. The script does all the data work. The agent fills a Markdown template from the script's payload with near-zero reasoning and **presents the filled board in its reply**. Same store state → byte-identical payload, regardless of model. Do NOT hand-summarize intents. ## When to Use - User invokes `/plastic-dashboard` - User asks "where are we", "what's next", "what should I work on", "show me the intents" - `plastic-project-continuing` lands on the board on resume - `plastic-auto` reads `--json` to choose the next dispatchable intent ## Procedure (the Markdown board — default human surface) ### Step 1 — Get the data payload ```bash ruby ~/.plastic/scripts/dashboard.rb [continue|project <slug>] --data ``` - `continue` (default) → the **global** board payload (`mode: "global"`). - `project <slug>` → that **project** board payload (`mode: "project"`). The payload is read-only JSON. Global-board fields: `date`, `store_health`, `summary`, `next_work`, `next_total`, `next_shown`, `counts`, `projects`, `project_totals`, `footer`. Project-board fields: `slug`, `store_health`, `description`, `s...