lovstudio-bp-deck

---
name: "lovstudio-bp-deck"
description: "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."
license: "MIT"
---

# 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 `lovstudio-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 `lovstudio-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;
- no placeholder or fabricated metric.

Send evidence blockers back to `bp-outline`. Small copy corrections may be recorded
in `deck-manifest.md` and applied without changing the thesis.

### Step 2: Select style with minimal friction

Infer style from brand, audience, reference images, and the outline. If the user has
not selected a direction, use `AskUserQuestion` once with 2–3 concrete options.

Recommended first option for seed-stage investors:

**Clean editorial** — white/warm-gray background, one brand color, dark conclusion
headlines, real screenshots, consulting-grade charts, and restrained decoration.

Alternative options:

- **Product keynote** — more whitespace and product/demo emphasis;
- **Consulting report** — denser evidence and chart emphasis;
- **Reference-led** — derive a design system from a supplied visual reference.

If the user says “按推荐方案” or “不要问”, use clean editorial.

### Step 3: Write `deck-manifest.md`

Record before rendering:

- outline path and version;
- audience, language, slide count, and presentation duration;
- style name, palette, typography, spacing, and safe margins;
- logos, screenshots, photos, data, and QR assets;
- naming convention;
- expected PPTX/PDF/preview paths;
- any slide intentionally marked illustrative.

### Step 4: Generate with `lovstudio-any2deck`

Invoke `lovstudio-any2deck` using the approved outline and chosen style. Preserve the
BP page order and evidence notes. Use 16:9, body text at least 20 pt, and a single
dominant visual per page.

Prefer:

- real product screenshots and user scenes;
- process diagrams and evidence ladders;
- source-backed charts with axes, units, dates, legends, and notes;
- simple cover and one clear final contact action.

Avoid stock-photo filler, decorative card walls, gradients, tiny source text, fake
dashboards, and unsourced growth curves.

### Step 5: Export and inspect

Produce editable PPTX, PDF, all slide images, and one full-deck preview. Review every
page at presentation size:

- no clipped/overlapping text or broken CJK;
- title/body/source hierarchy is consistent;
- logos are optically balanced;
- images are not stretched;
- chart values match the evidence ledger;
- product screenshots are genuine and legible;
- QR codes decode from the final rendered slide;
- PPTX and PDF page counts match;
- filenames include project, document type, and date/version.

Regenerate only affected slides. Record the result in `deck-manifest.md`.

### Step 6: Handoff

Return PPTX, PDF, preview, manifest, and any unresolved visual risks. Recommend
`lovstudio-bp-polish` for an adversarial final review.

## Recommended Next Step

```text
$lovstudio-bp-polish ./business-plan/project-bp.pdf --full
```