plastic-intent-starting

Intent Starting — board a session onto an intent

plastic-intent-starting is the Start procedure. It boards a session onto one intent: take the lock FIRST, confirm the delivery state, ask auto or guided ONCE, board at the latest delivered station, then run the cycle to Done. The What → Why → How → Exec stations are the train track; Start boards the train, the ending procedure (~93) exits it.

Precondition + trigger

Fires when the user picks an intent to work, when an agent is told to continue a SPECIFIC intent, or on continuing --intent {id} (the continuing → starting router is 106's job; this skill is invokable standalone now).

If the intent is terminal (Done / Abandoned in INDEX): report only. Take NO lock, run NO resume, do NOT reopen it. Summarize the outcome and ask what is next. Stop here.

Lock FIRST (the spine)

The lock is non-negotiable and comes before any mutating work. The ACTION-3 lock-gate enforces it: without a held lock, mutating writes to this active intent's dir are denied with "run /plastic-intent-starting to lock and begin".

Read ../plastic-conventions/references/locks-and-worktrees.md for delivery isolation: the single-owner lock, claims, worktrees, solo mode, and the station ledger behind everything below. This path resolves relative to this skill's own installed directory.

1. Ensure the intent is in INDEX ## Active. If it sits in ## Future, activate it (move it to ## Active, auto-commit) before arming. Creation precedes activation, so a brand-new What intent is activated here, then locked.
2. Self-heal the lock state first. Run: ruby ~/.plastic/scripts/plastic-lock fix --intent-dir <STORE>/<dir> This is the one repair function (same one /plastic-lock exposes): it removes corrupt or legacy lock state and rebuilds the lock and bridge from disk for this session. If it reports held, another session owns the intent: STOP and tell the user who holds it. If it reports stale, ask the user before running plastic-lock reclaim (takeover is audited).
3. Arm the bridge. Which arm is chosen by the mode answer (below), but the lock itself is taken first. Reuse the arm one-liner shape from plastic-auto:

   # guided (lock only):
   ruby -r ~/.plastic/scripts/lib/bridge -e \
     'codex=ENV["CODEX_THREAD_ID"].to_s.strip; claude=ENV["CLAUDE_CODE_SESSION_ID"].to_s.strip; harness=!codex.empty? ? "codex" : (!claude.empty? ? "claude" : nil); session=!codex.empty? ? codex : (!claude.empty? ? claude : nil); Bridge.arm_guided(session, intent_id: "<ID>", intent_dir: "<STORE>/<dir>", store: "<STORE>", name: "<name>", harness: harness, agent: "plastic-enforcer", thread: (!codex.empty? ? codex : nil))'
   # auto (lock + auto), then hand to plastic-auto:
   ruby -r ~/.plastic/scripts/lib/bridge -e \
     'codex=ENV["CODEX_THREAD_ID"].to_s.strip; claude=ENV["CLAUDE_CODE_SESSION_ID"].to_s.strip; harness=!codex.empty? ? "codex" : (!claude.empty? ? "claude" : nil); session=!codex.empty? ? codex : (!claude.empty? ? claude : nil); Bridge.arm_auto(session, intent_id: "<ID>", intent_dir: "<STORE>/<dir>", store: "<STORE>", name: "<name>", harness: harness, agent: "plastic-enforcer", thread: (!codex.empty? ? codex : nil))'
   

   Replace <ID>, <STORE> (~/.plastic/projects/<slug>/store or ~/.plastic/store), <dir> (the ID--slug directory), and <name>.
4. Dispatch What-stage discovery (under the lock). Right after arming, when the intent was just activated in step 1 (on a resume that already has resources/discovery--<slug>.md, skip: discovery runs once per intent, at activation only), dispatch the plastic-intent-discovery agent (see the plastic-intent-discovering skill), now that this session owns the lock, deposit authorized as the owner session. Resolve its model explicitly and pass it at dispatch time (belt-and-braces): read-config agents.models.plastic-intent-discovery --project <repo>. The agent runs QMD discovery over the intent's chain/sources and deposits findings to resources/discovery--<slug>.md only; it never writes the intent file, so the lock-owner-only rule is untouched. This is advisory context for Why, not a gate: if discovery yields nothing, proceed to Why normally.