Skip to main content

ConOps

The narrative of how the system will actually be used.

ConOps

What it's for​

ConOps captures the operational story before requirements harden — a document with four collections: a narrative Sections spine, a Mission Objectives table (Objective / Rationale / Success criteria), Operational Scenarios (Actors, Environment, Pre/Post-conditions, an ordered Sequence), and Stakeholder Needs (Need / Stakeholder / Priority / Rationale).

When to use it​

Early, alongside or just before Requirements, on system- and work-package-level nodes.

How it works​

  1. Pick a node, then choose the AI or Blank-doc path. → The AI path answers a short clarify questionnaire, then drafts all four collections; the blank path starts an empty skeleton with the agent on call.
  2. Click Generate ConOps. → Sections, Mission Objectives, Operational Scenarios and Stakeholder Needs render — each in its own card.
  3. Edit an item (one at a time across the whole document). → A single edit cursor: Edit → Save/Cancel on any section/objective/scenario/need, with a per-item “Ask” that seeds the agent with that exact item.
  4. Set Document Info, refine via a follow-on, and merge. → Changes show in the “Changes From Main Prompt” diff panel and fold into main on merge.

Mechanics​

  • Four collections: Sections · Mission Objectives · Operational Scenarios · Stakeholder Needs
  • Single global edit cursor · per-item “Ask agent” seeds
  • Pre-generation clarify questionnaire
  • Follow-on refine → diff panel → merge · review · baseline
  • Export: PDF · stamped PDF · CSV · JSON

Open ConOps in the app