DSTA ProductOps Co-pilot

Prompts

Operational-scenario generator

draft an operational scenario from operator research and capability brief

ResearchEngineeringCLARA

Output: A full operational scenario covering operator, mission context, environment, sequence, decisions, success/failure modes, and capability impact.

Paste into a CLARA-enabled chat

CLARA will confirm the route, ask for anything she still needs in one batched question, and show you the draft before filing.

Use CLARA's `operational-scenario-generator` for <programme name>.

What CLARA will ask you for

  • Programme name — your programme's name (e.g. SKYPROTECT).
  • Track — the slice of the programme this artefact belongs to (workstream, capability area, feature line, etc.), or Programme-wide if it spans tracks.
  • Scenario title — short (e.g. "Tank crew night transit through contested terrain", "Fighter aircraft low-altitude intercept", "Frigate surface-contact classification at dusk").
  • Inputs — CLARA will search the programme's Confluence space for operator research — interviews, field/exercise observations, workshop outputs; capability brief or statement of operational need; doctrinal or procedural references the operators work from (optional); themes (optional); friction points (optional). You can also paste fresh material if it's not in Confluence yet.

Where the output lands

Knowledge Base/{{track}}/Operational scenarios/{{scenario-title}} inside your programme's Confluence space.

Tips

  • Validate the draft with at least one operator before using it in capability discussions. Their reaction is the real test.
  • Pay particular attention to the failure modes — that's where the design opportunity usually hides.
  • Pair the output with a visual: use Nanobanana, Luma, or Forma to make the scenario tangible.
  • The output feeds the capability-spec generator and mission-thread mapper.

Where this fits in the chain

Use after

These prompts produce outputs you can paste as inputs here.

Research synthesiser

turn interview transcripts and field observations into a single Research synthesis page covering themes, friction, problem statement, and success criteria

Feeds into

The output of this prompt is consumed by these downstream prompts.

Capability-spec generator

derive measurable capability requirements from an operational scenario

Capability-storyboard scripter

script a visual storyboard showing how a capability is exercised end-to-end

Mission-thread mapper

map an end-to-end mission thread for the operational task a capability supports

Test-plan generator

draft a complete test plan with scenarios, participants, measurement, and analysis