plastic-project-continuing

Solid

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.

AI & Automation 9 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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`; surfac...

Details

Author
zalom
Repository
zalom/plastic
Created
2 months ago
Last Updated
1 weeks ago
Language
Ruby
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

plastic-continuing

Use when the user says "continue", "resume", or "pick up where we left off", starts a new session and wants to keep going, asks "what should I work on", or asks a where-was-I question that never says "continue" (for example "where was I"). This is the front door for resuming work: it dispatches to plastic-intent-continuing (a specific intent named to resume), plastic-project-continuing (the default, general board landing), or plastic-roadmap-continuing (a roadmap or delivery batch named to resume).

9 Updated 1 weeks ago
zalom
AI & Automation Solid

plastic-intent-continuing

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).

9 Updated 1 weeks ago
zalom
AI & Automation Solid

plastic-dashboard

Use when the user wants an overview of intents, asks "where are we", "what's next", "what should I work on", "show the dashboard", or invokes /plastic-dashboard. Renders the intent store(s) as Markdown prose, the global board as a narrative of work done, each project board as a short summary plus its most-valuable next work, and emits a machine-readable queue that auto mode consumes.

9 Updated 1 weeks ago
zalom