scalar-proposal-slideslisted
Install: claude install-skill wfukatsu/slide-forge
*[日本語](SKILL.ja.md)*
# Scalar Solution Proposal Slides
Use `references/scalar/workflow-contract.md` for shared sales-material rules
and `references/scalar/research-policy.md` for freshness/research. This skill
owns only proposal-specific decisions and generation.
Working directory: the slide-forge root — `${CLAUDE_PLUGIN_ROOT}` when running
from an installed plugin, `/path/to/slide-forge` on a local clone
(literal `cd` paths below assume the local clone).
## Important
- **Prerequisite skill**: `google-slides-template` (same repo) — auth, the
shared venv, the `scalar-2026` template, drawing API, and QA tooling. This
skill owns only what is proposal-specific: the hearing checklist, the
challenge→product mapping, and the proposal deck structure.
- **The customer's challenges drive everything.** A proposal without agreed
challenges is a product intro — route it to `scalar-product-slides`. Collect
hearing material (minutes, notes, RFP) before designing slides; what is not
known must surface as "to confirm today" on the deck, never as a guess.
- **Never fabricate customer-specific numbers.** Quantified effects need a
calculation basis from the hearing; otherwise write qualitative effects and
route quantification to the PoC ("measure it during the PoC and use it as
material for internal approval"). Public case numbers (ENS approx. 1/5, etc.)
are usable with sources.
- **Every initial proposal includes an architecture diagram and a BOM.** The
standard topol