Summon — Session Bootstrap

/summon is the sole entry point for every new conversation. All workflows — planning, direct execution, discussion, and design — route through summon.

Global Context-Gathering Rule

Every /summon path is user-intent-first, then context-gathering. After the user picks path 1-4, the very next step is to ask for their actual ask — what they want to build, change, discuss, or design, what scope they're thinking, which subsystem or surface area they care about. Do not run recon, Glob, Grep, or Read before the user tells you what they're trying to do.

Why: recon's planning-mode output is large (dependency graph, entry points, hotspots, symbols). Running it blind means it's a generic snapshot. Running it AFTER the user describes the ask means dominion/the agent knows which parts of the output matter — which entry points are relevant, which files to open first, which subsystems are in scope. The clarification is what turns a blind AST map into a targeted one.

Order for every path that needs repo context (A, B, C, D):

1. User intent first — ask what they want and get a response; surface the minimum substantial clarifying questions if the ask is underspecified
2. Recon second — run corvalis-recon with the user's ask in mind (keywords, subsystems, files they mentioned) so subsequent reasoning targets the relevant output sections
3. Targeted reads third — Glob/Grep/Read only to fill gaps recon couldn't cover