Prompts

Capability-spec generator

derive measurable capability requirements from an operational scenario

ResearchEngineeringCLARA

Output: Markdown capability spec with functional requirements, performance thresholds, environmental constraints, and traceability back to the scenario.

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 `capability-spec-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.
  • Operational scenario — page reference under Knowledge Base/{{track}}/Operational scenarios/* to base the spec on.
  • Capability name — short (e.g. "Tank-crew alerting aid", "Fighter aircraft sensor-fusion module", "Frigate surface-contact classifier").
  • Inputs — CLARA will search the programme's Confluence space for operational scenario for this capability; capability brief or statement of operational need; known constraints (optional) — regulatory, integration, schedule, platform. You can also paste fresh material if it's not in Confluence yet.

Where the output lands

Knowledge Base/{{track}}/Capability specs/{{capability-name}} inside your programme's Confluence space.

Tips

  • When you review CLARA's spec, every requirement should trace back to a specific scenario beat. Challenge any that can't — that's where drift creeps in.
  • Performance thresholds are where CLARA's draft will be vaguest unless your operational scenario contains hard numbers. Push for measurable thresholds ("within 5 seconds, 95th percentile") rather than "fast enough".
  • Pair CLARA's output with a Napkin AI system diagram so the requirements have a structural picture to anchor against.