jon-devlapaz CONOPS Builder
Use this skill to define intended use before requirements or design.
Workflow
- State the operational objective in user-visible terms.
- Identify actors, environment, preconditions, external interfaces, and constraints.
- Write the nominal scenario as observable user/system behavior.
- Write off-nominal and degraded scenarios, including trigger, system response, and recovery expectation.
- Separate behavior from design: say what must happen, not how to implement it.
- List assumptions, open questions, and unresolved interfaces.
- Output a CONOPS brief with: objective, actors, context, nominal flow, off-nominal flows, end state, assumptions, interfaces, and candidate requirements.
- Hand off candidate requirements to
requirements-distiller; hand off intended-use checks tovalidation-planner.
Source grounding
Start with references/source-grounding.md, then inspect extraction/pages/page_060.md and Appendix S pages extraction/pages/page_261.md through extraction/pages/page_263.md before making CONOPS-specific claims.