菜单
Turn a Demo Thesis into a causal software-product demo story. Use when creating a hook, 5-8 beat outline, claim-proof map, rough script, run-of-show, or second station of Damien's demo process before Demo Path and capture planning.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Start Alexandria in the current project. Initializes the project when needed, or welcomes the user back when Alexandria is already configured.
Raven's procedure for running EL3 Front-of-House Walk: launch detached against an EL2 draft bundle, walk the director through section-comprehension checks and held-back problem rulings, bank the director's answer as a Ledger event, and let AX apply only validated section/shape bundle corrections.
Use when writing or revising a library context's LEAD card body — the highest-altitude card whose how-it-does-it story the Index renders for the whole context. The lead must account for every other card in the context: narrate and link its direct children, and `relegates:` its deep internals, so the Index reads as a story instead of a pile of unused words. Applies where card bodies are authored (EL5/atomize), using the relationships Front-of-House has settled.
The authoring standard for product-library card bodies: write the WHAT / WHERE / HOW in the product's own plain language, keep every file path and code identifier in source_evidence (never in the prose), and keep event and ruling ids in frontmatter. Applied wherever a card body is written or revised — the Back-of-House walk's emit_bundle move, Front-of-House corrections, and EL5 body-fill.
Interpret Alexandria event log wake payloads from the local web UI/runtime, decide whether action is needed, and use AX commands to inspect or write event-log state.
Raven's procedure for running EL4 Empty Library Confirm: open a post-EL3 draft bundle as a body-free catalog, guide the director's structural review, and record either a user-authored library.confirmed Ledger event or a structure-only rejection edit list routed back to EL3.
| name | story-spine |
| description | Turn a Demo Thesis into a causal software-product demo story. Use when creating a hook, 5-8 beat outline, claim-proof map, rough script, run-of-show, or second station of Damien's demo process before Demo Path and capture planning. |
Turn the demo thesis into a watchable narrative structure with proof logic.
Read references/story-spine-process.md unless the user explicitly asks for a
very quick pass. If no Demo Thesis exists, create a compact inferred thesis
first and label it as a draft assumption.
Use this structure:
Story Spine
Narrative objective:
Chosen format:
Hook options:
Selected hook:
Beat outline
| beat | purpose | viewer shift | claim | proof needed |
Claim-proof map
| claim | why it matters | visible proof | scene | risk if not shown |
Rough run-of-show:
Lines to avoid:
Required product moments:
Open questions / assumptions:
Hand-off notes for Demo Path:
Do not let the story follow product architecture by default. The order should follow viewer comprehension and proof, not menu structure.