Prompts
Mission-thread mapper
map an end-to-end mission thread for the operational task a capability supports
ResearchEngineeringCLARA
Output: Markdown mission thread: actors, systems, data flow, decision points, dependencies, and failure modes across the full task.
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 `mission-thread-mapper` 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-wideif it spans tracks. - Operational scenario — page reference under
Knowledge Base/{{track}}/Operational scenarios/*. - Mission task — be specific: "detect, identify, and engage an inbound air contact from a frigate", or "neutralise a hostile armoured vehicle in urban terrain" — not "air defence" or "ground operations".
- Inputs — CLARA will search the programme's Confluence space for operational scenario for this capability; system context — systems, platforms, comms involved. You can also paste fresh material if it's not in Confluence yet.
Where the output lands
Knowledge Base/{{track}}/Mission threads/{{mission-task}} inside your programme's Confluence space.
Tips
- When you review CLARA's thread, aim for 5 to 12 steps end-to-end. Too coarse misses decision points; too fine documents screens. Push back if she lands outside that range.
- Look at the "failure mode + recovery" column first — the steps with the most expensive recovery paths are usually where capability investment pays off.
- Pair CLARA's output with a Napkin AI diagram so the data flow is visible at a glance.
Where this fits in the chain
Use after
These prompts produce outputs you can paste as inputs here.