printing-press-retro

Run a retrospective after generating a CLI. Identifies systemic improvements to the Printing Press — templates, Go binary, skill instructions, catalog — so the next CLI comes out better. Creates a GitHub issue with actionable findings when there are Printing Press fixes to make. Use after any /printing-press run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings".

3,106stars320forksUpdated 6/9/2026

Documentation #post-mortem #cli-generation #retrospective #github-issues #documentation #process-improvement

Security Assessment

Critical Risk(0/100)

Detected risks:

Destructive Operations([references/issue-template.md] rm -rf, [references/artifact-packaging.md] rm -rf)

Secret Exposure([references/secret-scrubbing.md] SECRET =, [references/secret-scrubbing.md] API_KEY=, [references/secret-scrubbing.md] PASSWORD=)

Sensitive File Access([references/secret-scrubbing.md] .env)

Security Score0/100

About printing-press-retro

The printing-press-retro skill performs a retrospective analysis after a Printing Press CLI generation run. Its purpose is to identify systemic improvements that could make future generated CLIs better, rather than fixing issues in the specific CLI that was just produced. The skill evaluates whether problems encountered during a generation session could realistically have been prevented or mitigated by improvements to the Printing Press itself. It focuses on recurring, generalizable issues and filters out normal manual customization and iteration that are expected when working with generated CLIs.

The skill analyzes the four subsystems of the Printing Press: the Generator, Scorer, Skills, and Binary. It applies a triage process to determine whether a finding represents a meaningful opportunity to improve future CLI outputs across multiple projects. When valid findings survive review, the skill creates a GitHub issue in the printing-press repository with actionable recommendations and supporting artifacts. It also emphasizes correct terminology, distinguishes system-level improvements from printed-CLI-specific fixes, and enforces strict handling of sensitive information by requiring secrets, personally identifiable information (PII), and other confidential data to be redacted before inclusion in retrospectives or public issue content.

This skill is intended for users who run the Printing Press workflow and want to continuously improve the system that generates CLIs. Typical use cases include post-mortem reviews, lessons-learned sessions, retrospective analysis after generation runs, and filing improvement findings for maintainers. It is particularly useful for contributors and maintainers seeking evidence-based enhancements that can raise the quality and consistency of future generated CLIs across multiple projects.

FAQ

When should I use the printing-press-retro skill?

Use it after a Printing Press run when you want to analyze what could be improved in the Printing Press itself rather than in the generated CLI.

Does this skill create fixes for the generated CLI?

No. Its focus is on systemic improvements to the Printing Press that could benefit future generated CLIs, not one-off fixes for a specific printed CLI.

What parts of the Printing Press can the retrospective evaluate?

It can evaluate findings related to the Generator, Scorer, Skills, and Binary subsystems.

What qualifies as a finding worth filing?

A finding should represent a generalizable improvement that could either prevent an issue entirely or meaningfully raise the baseline quality across multiple generated CLIs.

Are there any requirements for handling evidence and artifacts?

Yes. Secrets, PII, credentials, account identifiers, and sensitive data must be redacted before being included in retrospective documents, artifacts, or public GitHub issues.