printing-press-retro
Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for printed-CLI polish or a single-CLI fix.
Install
git clone https://github.com/mvanhorn/cli-printing-press /tmp/cli-printing-press && ln -s /tmp/cli-printing-press/skills/printing-press-retro ~/.claude/skills/printing-press-retroFrom README
/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. Boundaries Redact every real secret and PII before quoting. Issue bodies and retro docs are public. Use references/secret-scrubbing.md Layer 0. Never quote a leaked value as evidence of the leak.
More from this repo
printing-press
Set up a new integration, connector, or CLI binding for any API.
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript...
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy —...