plastic-intent-continuing

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 the user explicitly asks to continue a SPECIFIC intent, or an agent is instructed to continue one. It is not part of every boot.

QMD-first (when available): when the user names the intent by description rather than id, before scanning the store with grep/Read run ruby ~/.plastic/scripts/qmd-sync search "<terms>" to surface the candidate intent, then open the authoritative intent file for the hit you resume. The command is a no-op when QMD is absent, so fall back to the existing INDEX.md / file scan.