generate-slide

Generate Slide

Turn the markdown files in a Requirement Blueprint defined/ folder into a BA/pre-sales briefing.

This skill does not invent requirements. It only presents what is already in defined/ (and NEED-CONFIRMATION.md when still open).

Page size depends on the chosen format:

• PDF: A4 portrait (210 × 297 mm). Printable pack. Fit more of the markdown on the page.
• PPTX: 16:9 landscape (13.333" × 7.5"). Presentation deck. Split lists across more slides because the body is shorter.

Carry across the lists, features, scenario flows, screens, phases, and tasks from the markdown — compressed wording is fine; dropping whole sections is not.

When to use

Use when the user wants slides, a PDF deck, or a PowerPoint from a generated blueprint pack.

Do not use this skill to analyse a new customer brief. Use requirement-blueprint for that.

Workflow

List folders in output/
        ↓
Ask which pack to generate (do not skip this)
        ↓
Ask PDF or PowerPoint (unless already stated)
        ↓
Read that pack’s defined/*.md files
        ↓
Build an outline that covers each file
        ↓
Render PDF as A4 portrait, or PPTX as 16:9 landscape
        ↓
Save under output/<chosen-slug>/slides/

Do not generate files until the pack and the format are known.

Step 1 — Choose a folder in output/

Live packs are the child folders of output/ that contain defined/.

List them by running:

ls -d output/*/defined 2>/dev/null

Ignore output/README.md and output/.gitkeep. Do not list examples/ in this picker.

Then ask, before doing anything else:

Which pack in output/ should I generate slides from?

1. <slug-a>
2. <slug-b>

Rules:

• If a structured choice tool exists, use it. Always print the numbered list in chat.
• If the user already named a folder under output/ (or gave a full path), use that and skip the picker.
• If there is only one pack, still list it as option 1 and wait for them to pick it, unless they already named it.
• If output/ has no pack folders, stop. Tell them to export a confirmation pack with requirement-blueprint first. Do not invent slides. Do not silently use examples/.
• Use an examples/<slug>/ pack only when the user names that path.
• Do not write a new requirement pack into examples/.