Project One-Slider

Decide what the slide should say; delegate generic PowerPoint mechanics to an available maintained PPTX skill or presentation tool.

Evidence standard

Do not invent facts, metrics, outcomes, users, deployments, timelines, or business impact. Label gaps as:

• Not found in local files
• Inferred from code/config
• Needs user confirmation

Inspect the repository's current evidence: local instructions, README/docs, manifests and configuration, entry points, tests, reports, notebooks, assets/screenshots, deployment files, and version-control state when available. Prefer executable configuration and current source over stale prose. Cite paths in the evidence brief.

Use $project-understanding when available for a large or unfamiliar repository, but keep this skill responsible for executive selection and compression.

Build the story

Extract:

• Project and audience.
• User/business problem.
• What was built.
• Three to five load-bearing components or workflow steps.
• Current status.
• Demonstrated impact or qualitative capability.
• Important gap, risk, or next action.

Choose one defensible headline: <Project>: <outcome-oriented statement>. Avoid generic claims such as “leveraging cutting-edge AI.”

Produce the content

Create:

1. one-slider/project_brief.md — evidence, uncertainties, and selected story.
2. one-slider/slide_copy.md — final copy only.
3. one-slider/slide.mmd when a diagram improves comprehension.
4. one-slider/<project>_one_slider.pptx — exactly one slide.

Use no more than five content zones and no more than 22 short bullets. Prefer labels, metrics, compact tables, and workflow nodes over paragraphs. A nontechnical reader should understand the problem and outcome; a technical reader should recognize the real architecture.

Recommended copy:

# <Project>: <Outcome>

## Problem
- <1–2 bullets>

## Solution
- <2–3 bullets>

## Architecture / Workflow
- <3–5 steps or components>

## Impact / Current Evidence
- <2–3 evidence-backed bullets>

## Next Steps
- <2–3 concrete bullets>

Read references/layouts.md to select the visual structure.

Create the PPTX

Prefer an already-available maintained PPTX skill, presentation workspace, or project-native generator. Supply it with the evidence brief, final copy, selected layout, visual assets, and the hard requirement of exactly one editable 16:9 slide.

If no presentation backend is available:

1. Check for an existing project-native slide tool or python-pptx.
2. Reuse it when present.
3. If a new dependency or global installation is required, explain it and obtain authorization.
4. Keep any fallback generator deterministic and local to one-slider/.

Do not silently modify the project's dependency manifest for a one-off presentation.

Use $diagramming when available for architecture/workflow source. Render it to an image before embedding when the PPTX backend cannot render Mermaid natively. Prefer relevant project-owned screenshots or images over generic decoration. A logo or decorative icon alone does not satisfy the meaningful-visual requirement; the primary visual must communicate workflow, architecture, evidence, status, or risk.

Verify the artifact

Follow references/pptx-qa.md. At minimum:

• Confirm the file is a valid PPTX package.
• Confirm exactly one slide.
• Confirm all intended images are embedded.
• Confirm every shape is inside the 16:9 bounds.
• Render or inspect the slide visually when a viewer or rendering tool is available.
• Check clipping, overlap, legibility, alignment, and font-size consistency.
• Confirm every displayed metric or status traces to the evidence brief.

Report Structural QA and Visual QA separately. XML coordinates and slide bounds do not prove that text is unclipped, readable, or well composed. If no rendered slide or presentation view was inspected, write Visual QA: not performed and do not claim that overlap, clipping, or visual balance passed.

Deliver

Report:

• The selected story and layout.
• Clickable paths to the brief, copy, diagram, and PPTX.
• Validation actually performed.
• Missing evidence or claims that still need confirmation.