prime-contextlisted

# prime-context Load working memory before pipeline work on a Ready feature — the convergent counterpart to `discuss`. Forked from `superpowers:brainstorming` but inverted: no exploration, just loading and orienting. Produces no artifact. ## When to use A prep step (not a checkpoint) between `feature-init` and `discover-acs`, on any feature the agent hasn't already worked this session. **Skip when:** the agent just created the feature this session (context already warm). **Not for:** exploring whether a feature is worth doing (`discuss`). ## Workflow 1. **Resolve + locate** — resolve the methodology root + manifest via `${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py` (see `references/resolving.md`); locate the feature (slug arg or branch name). Reject if no folder / no `feature.md`. 2. **Silent batch load** — without narrating: `feature.md`, `CHARTER.md`, `manifest.yml`, prior `handoffs/` (especially the originating `*-discuss.md`), and the files named in `feature.md`'s "Related code / design pointers". 3. **Orient** — give a concise summary: outcome, scope, autonomy level (+ charter cap), key prior decisions, related code, relevant ADRs. 4. **One prompt** — ask exactly one question: anything else to load? If the user names a new code pointer, load it and offer to add it to `feature.md`. Then stop — prime-context orients, it does not interview. 5. **Handoff** — emit a summary. Re-invocation re-loads fresh (no incremental diffing). ## Handoff Emit per `${CLAUDE_PLUGIN_R