customer-card-render

Run scripts/generate_cards.py with --canonical-dir pointing at your canonical DT markdown folder and --output-dir for the generated content.yaml files. Then activate the powerpoint skill and hand it the content directory, style path, and output path to build the deck.

It supports Vision Statement, Problem Statement, Scenario, Use Case, and Persona artifacts. Vision, Problem, Scenario, and Persona each produce one slide, while each Use Case expands into 4 consecutive slides covering overview, execution, quality context, and extensions.

No. It only generates content.yaml slide definitions. The actual deck build is delegated to the experimental powerpoint skill, which owns Invoke-PptxPipeline.ps1, theming, validation, and export. If that skill is unavailable, the build step cannot run.

The skill requires Python 3.11 or later and the uv package manager for environment setup and testing. The generator script itself uses only the Python standard library, so it has no runtime package dependencies.

Empty output usually means the canonical directory path is wrong or the markdown files lack frontmatter. Missing sections occur when headings do not match the expected names in the mapping spec, such as 'Use Case Description' or 'How Might We'.

Every dynamic value passes through a yaml_escape function that escapes backslashes, double quotes, and newlines, and every template placeholder is wrapped in double quotes. Frontmatter is parsed by string partitioning rather than a YAML loader, so no arbitrary object construction occurs.