Printing Press Retro

After you ship a CLI from the Printing Press, this retro runs a structured post-mortem to figure out what went wrong at the system level, not just the CLI you just made. It looks through manuscripts, conversation history, and the printed CLI to find patterns where the generator templates, scoring tools, or skill instructions could have raised the floor for the next API. The default stance is "don't change the machine" because most issues are one-off quirks, so it applies a three-phase triage with an adversarial check before filing anything. When it does find something worth fixing, it scrubs secrets and opens a GitHub issue with artifacts so maintainers can actually improve the Press. Best run right after shipcheck while the context is still warm.

skills.sh installs: 6.7K
GitHub stars: 4.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add mvanhorn/cli-printing-press --skill printing-press-retro --agent claude-code

Installs into .claude/skills of the current project.

Files

/printing-press-retro

Result: A scrubbed retro document and, when the issue gate passes, GitHub issues for Printing Press defects only.

Next consumer: A maintainer or agent who will change the Printing Press (generator, scorer, skills, or binary) — not the printed CLI that just shipped.

Done: The manuscript proof exists and is scrubbed; every work unit is file-new, comment-on-existing, or local-only; no unredacted secret or PII remains; the user has the outcome list.

Intent: "Raised the floor" is analysis language, not a filing bar. File only when the Printing Press must change to stop a current, reproducible, generalizing P1 or P2 defect. Manual iteration on one CLI is expected work, not a finding. In user-facing output say "the Printing Press"; name the subsystem when pointing at a fix.