nexus-report-slideslisted

*[日本語](SKILL.ja.md)* # nexus-architect Report Slides Builds an explanation deck from what a nexus-architect project has produced so far. The project is **read only** — this skill never writes into it. Working directory is the slide-forge root; the command is `.venv/bin/python`. ## Boundaries | Request | Route | |---|---| | Explain a nexus-architect project's results as slides | this skill | | Produce or rerun the analysis itself | nexus-architect's own `/architect:*` `/product:*` skills | | Add or change a page template | `slide-template-creator` (pack rules: `references/nexus-reports.md`) | | Deck generation mechanics, master selection | `google-slides-template` | | Check the generated deck visually | `slide-qa` | | Export to PowerPoint | `pptx-export` (or `output: local` in `config/settings.json`) | ## The unfinished pipeline is the normal case A pipeline is usually mid-flight: phases pending, one running, another that wrote two of its four declared outputs. Three rules follow, and they are not optional: 1. **Establish coverage before content.** `collect.py` reads `work/pipeline-progress.json` (and `tools/nexus-status.sh --json` when a nexus-architect checkout is reachable) and writes one `coverage.json`. Page 2 of every deck is `pipeline-coverage`, stating how many phases the deck rests on. 2. **Only completed work becomes content.** A phase with some outputs written is built from the files that exist, never from the ones that do not. 3. **Gaps ship as