# Plastic Intent Starting

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-zalom-plastic-intent-starting`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [zalom](https://agentstack.voostack.com/s/zalom)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [zalom](https://github.com/zalom)
- **Source:** https://github.com/zalom/plastic/tree/main/skills/intent-starting
- **Website:** https://github.com/zalom/plastic

## Install

```sh
agentstack add skill-zalom-plastic-intent-starting
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Intent Starting — board a session onto an intent

Announce: "Boarding intent [ID] — [name]."

`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".

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 /`
   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`:
   ```bash
   # guided (lock only):
   ruby -r ~/.plastic/scripts/lib/bridge -e \
     'Bridge.arm_guided(ENV["CLAUDE_CODE_SESSION_ID"], intent_id: "", intent_dir: "/", store: "", name: "")'
   # auto (lock + auto), then hand to plastic-auto:
   ruby -r ~/.plastic/scripts/lib/bridge -e \
     'Bridge.arm_auto(ENV["CLAUDE_CODE_SESSION_ID"], intent_id: "", intent_dir: "/", store: "", name: "")'
   ```
   Replace ``, `` (`~/.plastic/projects//store` or `~/.plastic/store`),
   `` (the `ID--slug` directory), and ``.
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--.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 `. The agent runs QMD discovery
   over the intent's `chain`/`sources` and deposits findings to
   `resources/discovery--.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.

**Session id resolution (verbatim from `plastic-auto`).** The first argument is the session
id the bridge is keyed by: pass the hook stdin `session_id` when you have it, otherwise
`ENV["CLAUDE_CODE_SESSION_ID"]`, otherwise `nil`. Both arms call `resolve_session`, which
picks the first non-empty of: the explicit id you pass → `CLAUDE_CODE_SESSION_ID` → a
deterministic derived key (a hash of the store and intent id). It never returns nil, so the
lock is taken even when every session env var is empty; arming prints a one-line stderr
notice when it falls through to the derived key.

**What the lock IS.** Ownership is session-keyed and lease-based: arming writes a durable
`delivery.lock` file in the intent dir naming this session as owner, and the owner's hooks
refresh the file mtime on tool activity (the lease heartbeat). The /tmp bridge is only a
cache of that file; on any disagreement the lock file wins, so a wiped /tmp never strands
the owner. Idempotent re-arm: arming again with the same owner just refreshes the lock; it
is not an error to re-board an intent this session already owns. A failed arm raises with
a message naming the resolving `plastic-lock` verb (`status`, `reclaim`, or `fix`): follow
that message, never delete a lock file by hand.

## Confirm delivery state

Read `savepoint.md` and classify from the **last line** alone, then verify ONLY that line's
artifact is real (sentinel-aware via `Bridge.stage_file_present?`). On drift (the last line
disagrees with files on disk), rebuild the ledger from disk and note the correction. Do not
inline the rebuild; the `plastic-intent-savepoint` skill owns it:
```bash
ruby -r ~/.plastic/scripts/lib/bridge -e 'Bridge.rebuild_savepoint("")'
```

## Report + ask "auto or guided?" ONCE

Report: the intent, the station it lands at (the matrix below), what is delivered, the next
step. Then ask the user **"auto or guided?"** — exactly ONCE, whatever station it lands at.
Never re-ask at a later station.

- **guided** → `arm_guided` (lock only); continue step by step with the user through the
  station's work below.
- **auto** → `arm_auto` (lock + auto), then hand off to `plastic-auto`. The auto branch's
  only remaining job is the handoff; `plastic-auto` runs the cycle from here.

## Board at the latest delivered station

The station is derived from `savepoint.md` last line + real artifacts on disk. See
`references/boarding-matrix.md` for the full table (last line → latest delivered → boards at →
continue with) and the per-station notes. Summary of what "continue" means per station:

- **What** → do what What requires (106-expanded), then brainstorm → `spec.md`.
- **Why** → continue brainstorming → `spec.md`.
- **How** → continue `plan.md` + `actions/` + `checklist.md`.
- **Exec** → verify what has been delivered, then continue (or restart) the delivery /
  research; tick the checklist.
- **ready to complete** (`Exec outcome.md created`) → exit at Done.
- **Done** → report only, ask what is next, never reopen.

## Disarm / release on done

When delivery finishes, disarm and release per the `plastic-auto` disarm/release prose (do
not duplicate it here). The guided branch releases the lock via `disarm_auto`, which is
mode-agnostic (it sets `auto = false` and calls `Worktree.release`), so it releases a guided
lock too. When the work ships through a release, the release path merges the branch before the
worktree is removed; the plain disarm remove is only for the no-release case.

## References

- `references/boarding-matrix.md` — the full boarding table and per-station behaviour.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [zalom](https://github.com/zalom)
- **Source:** [zalom/plastic](https://github.com/zalom/plastic)
- **License:** MIT
- **Homepage:** https://github.com/zalom/plastic

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-zalom-plastic-intent-starting
- Seller: https://agentstack.voostack.com/s/zalom
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.