lov-bp-deck

# BP Deck Produce the presentation after the investment narrative is approved. This skill owns style selection, visual specification, rendering, export, and final-image QA; it does not invent missing business evidence. ## Input Gate Required: - approved `outline.md` or equivalent page-by-page narrative; - evidence/source notes for core claims; - project/company name. Recommended: - brand logo and primary color; - real product screenshots; - founder/team photos; - source data for charts; - website/contact destination and QR asset. If the outline lacks a clear product definition, financing ask, or source-backed core numbers, stop and recommend `lov-bp-outline` before rendering. ## Output Contract ```text business-plan/ ├── outline.md ├── assets/ ├── deck-manifest.md ├── 01-slide-cover.png ���── ... ├── project-bp.pptx ├── project-bp.pdf └── project-bp-preview.png ``` ## Workflow (MANDATORY) ### Step 0: Resolve input and dependency Resolve this skill directory as `SKILL_DIR` and locate the user's approved outline. Resolve `lov-any2deck` through the active Agent Skills environment; do not assume an author's private installation path. Read `references/user-config.md` and `references/charts-and-visuals.md`. ### Step 1: Lock the narrative Do not rewrite the storyline during style exploration. Check: - 12–15 slides unless the user explicitly chooses otherwise; - one conclusion per slide; - evidence IDs/source notes on core claims; - chart type and exact data mapping; ...