intake

---

name: intake description: "Fast session intake for the swarm leader: settle the plan/task with one clarification batch, cross-check and reuse existing plans/tasks, anticipate ALL follow-up work up front, then a single approval gate that dispatches the batch and delivers either an inline report or a rendered-page report emailed to the operator and linked for posterity. Collapses human-in-the-loop to (at most) one question batch + one approval. Auto-engages on the first substantive request of a session; also invocable as /intake." slug: intake user_invocable: true triggers:

• intake
• /intake
• start session
• what should we do
• new request supported_harnesses:
• claude-code
• cursor entity_id: ent_a650ca318a06a92e54bee312

---

intake

The swarm leader's session-intake protocol. Goal: from the operator's opening request, reach a dispatched plan with the fewest possible human-in-the-loop turns — ideally one clarification batch and one approval gate — then deliver results the way the operator chose.

When to engage

• Auto-engage on the first substantive request of a session (a task or goal), not on quick lookups or one-step asks you can just do.
• Or invoke explicitly: /intake <request>.
• Skip entirely for trivial single-step work — do it directly.

Phase 1 — Settle the work (ONE clarification pass)

1. Bounded retrieval. retrieve_entities over plan and task matching the request (lexical + semantic). Search by CONCEPT and architecture terms, not only the product/feature noun — run several phrasings (the capability or "spine/loop/lifecycle/pipeline" name, the owning role, the core verb), because the best-matching plan is frequently named for the concept rather than the product. A single product-noun query is how a concept-named plan gets missed and a duplicate, competing plan gets created (the cross-workstream-collision failure mode).
2. Cross-check, don't duplicate. Decide whether an existing plan/task already fulfills the request — fully, or better than asked. If so, propose executing/refining THAT (cite entity IDs) instead of creating something new.
3. Bind the plan. Pick the closest existing plan as the session's bound plan; if none fits, create one (/update-plan). Never write one workstream's items into another workstream's plan.
4. Ask all forks at once. Put every genuine decision fork into a SINGLE AskUserQuestion batch; infer sensible defaults for everything else. Do not drip questions across turns.