Post-Stage Retrospective Artifact

Generate idempotent post-stage retrospective artifacts for NFL content pipelines.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/JDL440/nfl-eval --skill post-stage-retrospective-artifact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Post-Stage Retrospective Artifact
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/post-stage-retrospective-artifact
Command: npx skills add https://github.com/JDL440/nfl-eval --skill post-stage-retrospective-artifact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-stage retrospective artifacts address the need to capture learnings, audit trails, and improvement opportunities after a pipeline stage completes, without gating core execution.

Core Features & Use Cases

  • Structured artifact: stores learnings, revision histories, and validation notes for later analysis.
  • Cross-surface visibility: surfaces insights to dashboards, tests, and reviewers for informed iteration.
  • Idempotent persistence: ensures repeated runs do not create duplicate artifacts and maintains a consistent history.
  • Use Case: after article publication or a pipeline slice, generate a retrospective artifact summarizing changes and recommended actions.

Quick Start

Create a post-stage retrospective artifact for the latest pipeline stage to capture learnings and improve future runs.

Frequently Asked Questions about Post-Stage Retrospective Artifact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a post-stage retrospective artifact in a content pipeline?▼

A post-stage retrospective artifact captures structured learnings, audit trails, and improvement recommendations after a pipeline stage completes. It stores revision histories and validation notes for later analysis without gating core execution.

How do I capture pipeline learnings after an article publication stage?▼

Generate a retrospective artifact summarizing changes and recommended actions after article publication or a pipeline slice. This artifact captures structured findings and validation results to improve future runs.

How does idempotent artifact creation prevent duplicate retrospective records?▼

Idempotent artifact creation ensures repeated pipeline runs do not create duplicate artifacts. This maintains a consistent revision history by safely persisting post-stage learnings across multiple executions.

Can I store retrospective artifacts using a custom database repository?▼

Yes, retrospective artifacts store results in a persistence layer compatible with src/db/repository.ts. This integrates with existing stage model references in src/types.ts for cross-surface visibility across dashboards and tests.

What is the best way to surface post-stage learnings to dashboards and reviewers?▼

Creating a structured retrospective artifact surfaces insights to dashboards, tests, and reviewers. It provides cross-surface visibility by storing validation notes and improvement recommendations for informed iteration.