メニュー
Coordinate Damien's Alexandria demo video process across Demo Thesis, Story Spine, Demo Path, and downstream production stations. Use when the user asks for an end-to-end demo video plan rather than one specific station artifact.
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 | demo-video |
| description | Coordinate Damien's Alexandria demo video process across Demo Thesis, Story Spine, Demo Path, and downstream production stations. Use when the user asks for an end-to-end demo video plan rather than one specific station artifact. |
Use this skill when coordinating the full demo-video process for Alexandria.
references/alexandria-demo-video.md for the default framing.demo-thesis first when the audience, belief change, proof burden, or
CTA is not already locked.story-spine next to create hook options, causal beats, and a
claim-proof map.demo-path next to create exact product steps, required data, risks, and
fallback paths.