domain-chassis

Scaffold a new domain workspace with the common chassis files

Use this agent when the user wants to manage a gate lifecycle or load domain context through the gate operator. Triggers on: "gate Q{n}", "review Q{n}", "work Q{n}", "re-review Q{n}", "prime", "orient me", "what's in flight". <example> Context: User wants to load domain context user: "prime" assistant: "I'll use the gate-operator agent to load domain context." <commentary> The gate-operator has the prime skill preloaded and can load session context. </commentary> </example> <example> Context: User wants to start or continue a gate lifecycle user: "gate Q14" assistant: "I'll use the gate-operator to detect the Q14 lifecycle state and dispatch the appropriate stage." <commentary> The gate-operator reads filesystem state to determine lifecycle position and dispatches accordingly. </commentary> </example>

This skill should be used when the user asks to "do an AAR", "after action review", "retrospective", "review what happened", "what went well", "lessons learned", "post-mortem", "debrief the session", "debrief the run", or mentions reviewing a completed work session, analyzing outcomes, or capturing operational lessons. Provides the AAR methodology framework for structured retrospective analysis across any domain.

This skill should be used when the user asks to "write up this component", "document this system", "produce a technical writeup", "create a component writeup", "architecture documentation", "system documentation", "document the architecture of X", "technical writeup of X", "how does this system work — write it up", "map out this system's components", or mentions producing structured technical documentation of a system, subsystem, or component set. Produces progressive-disclosure documentation following the Patnaik template with system-decomposition analytical rigor — component inventory, architecture overview, data flow, per-component detail, and grouped references.

This skill should be used when the user asks to "create a gate", "plan a gate", "write a gate", "draft a gate", "new gate", "gate Q4", "gate for Q4", "gate plan", "create Q-gate", "gate plan for Q", "write a validation plan", or mentions creating a gate document, drafting validation criteria for a queue item, or planning what needs to be proven before work is considered done. Provides the gate document authoring methodology for creating production validation plans from queue items.

This skill should be used when the user asks to "review the gate", "audit the gate", "check the gate", "gate review", "does this gate pass", "evaluate this gate", "review Q3-gate", "is this gate ready", or mentions evaluating an existing gate document against quality standards, checking gate verification rigor, or auditing a gate before execution. Provides the gate quality audit methodology for evaluating gate documents against the gate-plan quality bar.

This skill should be used when the user asks to "work the gate", "execute the gate", "run the gate", "work Q3", "run Q3", "do Q3", "execute Q3", "work through the gate", "gate work", "task me with the gate", "resume the gate", or mentions executing against an existing gate file, working through gate checkpoints, resuming a partially-completed gate, or validating against a gate document. Provides the gate execution methodology for working through an operator-authored validation plan.

Loads and summarizes session context by reading the doctrine, project index, queue, and triage state.

This skill should be used when the user asks to "review a spec", "validate a spec", "is this spec implementable", "critique this spec", "find problems in my spec", "check this design doc", "is this plan sound", "review before implementation", "review this document", "document review", or mentions reviewing specs or structured documents for correctness, implementability, cross-reference consistency, or control-flow soundness before execution begins. Provides a structured multi-round review methodology using targeted subagent prompts that trace state through control flow branches and cross-reference interfaces.