lov-bp-polish

# BP Polish Improve an existing BP without silently changing its business facts. This skill can be used before deck production, after rendering, or in a correction loop. ## Modes | Mode | Input | Focus | |---|---|---| | `content` | Outline / Markdown | Product definition, story, copy, page rhythm | | `evidence` | Outline + ledger/sources | Claims, metrics, TAM/SAM/SOM, assumptions | | `visual` | PPTX/PDF/slide images | Hierarchy, charts, layout, branding, QR codes | | `full` | Any complete BP workspace | All dimensions + correction loop | Infer the smallest useful mode from the request. Do not require a PDF when the user only wants the outline reviewed. ## Output Contract ```text business-plan/ ├── reports/bp-review.md ├── outline.md # patched only when authorized by the request ├── deck-manifest.md # updated for visual fixes └── revised slide/deck assets # only affected artifacts ``` ## Workflow (MANDATORY) ### Step 0: Resolve source and mode Resolve this `SKILL.md` directory as `SKILL_DIR`. Inspect the supplied source and any existing BP workspace. Reuse audience, stage, style, and evidence definitions. If multiple review modes are plausible, prefill from the user's wording. Ask one compact question only when the choice materially changes the work. “不专业” defaults to `full`; “文字太技术” defaults to `content`; “图表不好看” defaults to `visual`. Read `references/review-rubric.md`, `references/charts-and-visuals.md`, and `references/user-config.md` ...