pipeline-summary-report

Read every report in docs/analysis/, write 3-8 bullet summaries per report grouped by pipeline phase, then synthesize a 2-4 paragraph executive narrative connecting findings across reports. Write the result to docs/analysis/26-pipeline-summary.md.

Generate it only after all or most pipeline skills have completed and written their reports to docs/analysis/. Running it while reports are still being produced yields an incomplete synthesis, so wait for the pipeline orchestrator to signal completion.

The summary still gets written but includes a Pipeline Health table marking each expected report as present, missing, or stub. With fewer than 10 reports, the output is flagged as preliminary with insufficient coverage for full synthesis.

No. It only reads and synthesizes existing reports. It does not re-run analyses, modify upstream reports, produce new findings, or generate the subagent instruction prompt, which is the responsibility of skill 25.

Carry caveats from source reports into the summary explicitly and prefix uncertain findings with their confidence level. Never present low-confidence results as definitive, and list all flagged reports in the Pipeline Health section.