pipeline-retro

Pipeline failure analysis works by tracing through the five-link generation chain. It loads pipeline-test-runner reports containing manifest.json and content.md to identify root causes across domain research, chain composition, scaffolder templates, architecture rules, and step menus.

The five-link generation chain consists of domain research, chain composition, scaffolder template, architecture rules, and step menu. Pipeline failure tracing isolates which generation stage introduced the defect by evaluating each link sequentially.

Prove generator fixes by applying regeneration to affected pipelines after proposing fixes with evidence citations. Validate that regeneration results show improvements across subdomains to confirm the root cause is resolved and recurrence is prevented.

Generate a structured retro report by feeding pipeline-test-runner output and the related pipeline spec for analysis. The tool produces a dual-layer artifact detailing failures, trace analysis, proposed generator fixes, and regeneration results ready for review.

Yes, you can trace pipeline failures by loading and parsing manifest.json and content.md files from pipeline-test-runner reports. These files provide the failure inventory and test output data required to perform root cause analysis across the generation chain.

Pipeline failure regeneration proves improvements across subdomains but requires the related pipeline spec to validate fixes. Without proper evidence citations and the full pipeline spec, regeneration results may not accurately confirm that root causes are resolved.