printing-press-retro
mvanhorn/cli-printing-press
Conduct structured retrospectives on Printing Press runs and file defect issues.
What is printing-press-retro?
Use this skill when you need to analyze a Printing Press CLI generation run, identify defects, and file issues for the Printing Press itself (not the generated CLI). It guides you through evidence gathering, triage, classification, and issue filing with mandatory secret/PII scrubbing.
- Gather evidence from Printing Press run logs and artifacts
- Mine session data to identify potential defects and issues
- Triage and classify findings by severity and impact
- Prioritize work units for Printing Press improvements
- Generate a scrubbed retrospective document
- File GitHub issues for P1/P2 defects only
How to install printing-press-retro
npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press-retro- Access to Printing Press run logs and artifacts
- GitHub repository access for filing issues (when submitting)
- Knowledge of what constitutes a P1/P2 defect vs. expected manual iteration
How to use printing-press-retro
- 1.Read references/run-resolution.md to resolve API_NAME, RUN_ID, RUN_DIR, CLI_DIR, and IN_REPO variables
- 2.Execute phase 01-gather-evidence.md to collect logs and artifacts from the run
- 3.Execute phase 02-mine-the-session.md to extract potential issues from session data
- 4.Execute phase 03-triage-candidates.md to filter and validate findings
- 5.Execute phase 04-classify-findings.md to categorize defects by type and scope
- 6.Execute phase 05-prioritize.md to rank findings by severity
- 7.Execute phase 06-write-the-retro.md to generate the retrospective document
- 8.Execute phase 07-plannable-work-units.md to create actionable work items
Use cases
- Analyze why a generated CLI failed or behaved unexpectedly and identify root causes in the Printing Press
- Document lessons learned from a CLI generation run and propose improvements to the generator
- Identify reproducible defects in the Printing Press scorer, skills, or binary that affect multiple runs
- Conduct post-mortems on failed CLI shipments to prevent similar issues in future generations
- File tracked defects against the Printing Press for the maintainer team to address
- Printing Press maintainers and operators
- CLI generation engineers
- QA and testing teams reviewing generated CLIs
- Agent workflows that need structured retrospective analysis
printing-press-retro FAQ
Use it when the user asks to conduct a retro, retrospective, post-mortem, file findings, or improve the Printing Press after a CLI run. Trigger phrases include 'retro', 'what went wrong', 'lessons learned', and 'file a retro'. Do not use it for polishing the generated CLI itself.
Only P1/P2 defects in the Printing Press (generator, scorer, skills, or binary) that are reproducible and generalizing. P3 issues, single-CLI fixes, and manual iteration are not filed. The issue gate enforces this filter.
All secrets and PII must be redacted before the retro document and any GitHub issues are created. Use the secret-scrubbing.md reference (Layer 0) and never quote leaked values as evidence. Unscrubbed artifacts are never uploaded.
A Printing Press maintainer or agent who will change the Printing Press itself—not the printed CLI that shipped. The retro is for improving the generator, not iterating on the generated CLI.
No. The skill authorizes reading manuscripts/library and writing the retro proof and scratch copies, but not editing the printed CLI or Printing Press source. The burden of proof is on the finding before any changes are made.
Full instructions (SKILL.md)
Source of truth, from mvanhorn/cli-printing-press.
name: printing-press-retro description: > 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. version: 0.1.0 allowed-tools:
- Bash
- Read
- Glob
- Grep
- Write
- Agent
- AskUserQuestion created_by: user
/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.
- Don't change the machine by default. The burden of proof is on the finding.
- No P3. File only P1/P2. Anything else is Skip or Drop, not a low-priority issue. The issue gate files P1/P2 Do work units only.
- Never upload unscrubbed artifacts. Never modify manuscript or library source trees; scrub copies only.
Authority
Invocation authorizes reading manuscripts/library and writing the retro proof plus scratch copies. It does not authorize GitHub filing or public upload until the user confirms Submit. It does not authorize edits to the printed CLI or to Printing Press source.
Steps
Read references/run-resolution.md first. It
resolves $API_NAME, $RUN_ID, $RUN_DIR, $CLI_DIR, and $IN_REPO.
Never execute a phase from memory. When you enter a phase, Read its file from phases/ first.
Follow each file's final Next: pointer. Late procedure lives in the phase
file or a role-named reference it loads
(references/artifact-packaging.md,
references/issue-template.md,
references/secret-scrubbing.md). Do not
restate those files here.
Related skills
More from mvanhorn/cli-printing-press and the wider catalog.
printing-press-score
Score generated CLIs against the Steinberger bar and compare them side-by-side.
printing-press
Generate ship-ready Go CLIs from OpenAPI, HAR, or Postman specs via structured research-generate-build-test loop.
printing-press-amend
Turn dogfood friction into PRs for published CLIs in the printing-press library.
printing-press-catalog
Browse and install pre-built Go CLIs for popular APIs from the catalog
last30days
Research what people actually say about any topic in the last 30 days across Reddit, X, YouTube, TikTok, and more.
pp-company-goat
Look up startups across SEC Form D, GitHub, Hacker News, Companies House, YC, and Wikidata in one command — including the SEC fundraising data hidden behind paid Crunchbase tiers. Trigger phrases: `look up this startup`, `research <company>`, `what does <company> do`, `form D for <company>`, `is <company> still active`, `compare <a> and <b>`, `use company-goat`, `run company-goat-pp-cli`.