Prompts
Capability-storyboard scripter
script a visual storyboard showing how a capability is exercised end-to-end
DesignEngineeringCLARA
Output: Markdown storyboard script: beat-by-beat panels with what to show, what's happening, and what changes from the prior beat.
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-storyboard-scripter` 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. - Storyboard title — short (e.g. "Tank-crew alerting under degraded comms").
- Length — number of panels. Typically 8–12; shorter (5–6) for a quick brief or longer (15+) for a full narrative.
- Audience — who the storyboard is for. Examples: operators reviewing the capability for the first time, or the engineering team scoping the build.
- Inputs — CLARA will search the programme's Confluence space for operational scenario this storyboard depicts; capability spec for the capability being shown (optional); persona depicted in the storyboard (optional). You can also paste fresh material if it's not in Confluence yet.
Where the output lands
Knowledge Base/{{track}}/Capability-storyboards/{{storyboard-title}} inside your programme's Confluence space.
Tips
- When you review CLARA's panels, check the carry-over field on each. Without it you get a set of disconnected hero shots, not a narrative.
- If CLARA's panels read like a system diagram, push back — the capability should be visible in use.
- CLARA's panel-level prompts are the spec for the visualisation tool, not the visualisation itself. Send them through to Luma / Nano Banana / Forma for the actual rendering.
Where this fits in the chain
Use after
These prompts produce outputs you can paste as inputs here.