exexutor

Guidance for picking the right model per role ("droid whispering"). Activate when configuring agents, starting a new mission, or diagnosing why a role is misbehaving. Model strings age fast — verify current names via search per P-2 before relying on the defaults below.

How to set up every external service the project needs WITHOUT asking the user to run commands or follow long tutorials. The orchestrator handles all installation, configuration, MCP setup, and verification. The user provides only the data the orchestrator cannot obtain itself (credentials, choices). MCP servers are preferred over raw API integration where available.

How to run the two-round multiple-choice discovery questionnaire. Defines the 30 default round-1 questions across 6 categories, how to adapt them per project type, and how to generate the 15 round-2 follow-ups from gaps and contradictions.

How to produce the validation contract, draft plan, and tech-decisions from the description and discovery answers. Web-searches for current versions before committing to anything. Targets fine-grained feature decomposition (more features = better). Features here are DRAFTS — the /mission-tasks phase enriches them. Activate during /mission-plan.

Mandatory handoff template every worker fills out before exiting. The pre-worker-exit hook validates this file and blocks the worker if anything is missing. Activate inside any worker subagent.

Per-feature 20-question interrogation that turns a draft feature spec into a fully-specified one. Three rounds — 10 task questions, 5 follow-ups, 5 "definition of done" questions. Each question has 4 options with one ★ recommended based on context. Activate during /mission-tasks.

Format and quality rules for the validation contract — the flat, numbered, falsifiable assertion list every feature must satisfy. Activate when planning a mission or when validating one.

Forces the orchestrator to web-search for current versions, current authentication methods, and current setup patterns before writing tech-decisions, connection manifest entries, or anything else that depends on the state of the world today. Activate during /mission-plan and /mission-connect. NEVER skip this.

When and how workers use MCP tools during /mission-run. Prefer MCP for live service introspection (Supabase schema, GitHub, etc.) when connections/mcp-registry.md lists the service. Activate in worker subagents during execution.