plastic-intent-continuing

Solid

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

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

# Continuing (intent route) `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 `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 resumes the named intent. This is the seam future continue-flags build on (see [[39]]). ## When to Use - 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 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 named intent's store. 3. If neither exists → announce "No Plastic store found. Run /plastic-install." ## Conditional Ledger-Resume Fires ONLY when ...

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-project-continuing

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.

9 Updated 1 weeks ago
zalom
AI & Automation Solid

plastic-intent-starting

Board a session onto an intent: take the lock FIRST, confirm savepoint state, ask auto or guided ONCE, then resume at the latest delivered station and run the cycle to Done. Use on `continuing --intent {id}`, when a new intent is registered and the user asks to work it, or when the user picks an intent to work. Requires the intent in INDEX `## Active`.

9 Updated 1 weeks ago
zalom