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.
Resumen
/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.
Archivos 14 archivos
- SKILL.mdMarkdown
- phases/01-gather-evidence.mdMarkdown
- phases/02-mine-the-session.mdMarkdown
- phases/03-triage-candidates.mdMarkdown
- phases/04-classify-findings.mdMarkdown
- phases/05-prioritize.mdMarkdown
- phases/06-write-the-retro.mdMarkdown
- phases/07-plannable-work-units.mdMarkdown
- phases/08-issue-gate.mdMarkdown
- phases/09-package-upload-present.mdMarkdown
- references/artifact-packaging.mdMarkdown
- references/issue-template.mdMarkdown
Instálala a mano
Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:
npx skills add mvanhorn/cli-printing-press --skill printing-press-retroMás de mvanhorn
- last30daysmvanhornResearch what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.44.6 k instalaciones en skills.sh0
- printing-pressmvanhornSet up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a service, or names an API by domain.7,100 instalaciones en skills.sh0
- printing-press-publishmvanhornPublish a generated CLI to the printing-press-library repo6,500 instalaciones en skills.sh0
- printing-press-polishmvanhornPolish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use after any /printing-press run, or on any CLI in $PRESS_LIBRARY/. Trigger phrases: "polish", "improve the CLI", "fix verify", "make it publish-ready", "clean up the CLI", "get this ready to ship".6,400 instalaciones en skills.sh0
- printing-press-reprintmvanhornRegenerate an existing printed CLI from scratch under the current Printing Press, with prior research, prior novel features, and prior patches (post-publish hand-fixes) carried into the writing pipeline as reconciliation context rather than dropped on the floor. Pulls the CLI from the public library if it isn't local, recommends reuse-vs-redo of prior research based on age, then hands off to /printing-press with the right context. Use when a machine upgrade would benefit a published CLI more than manual polish. Trigger phrases: "reprint <api>", "regenerate <api>", "redo the <api> CLI", "rebuild <api> from scratch", "this CLI would benefit from a reprint".6,200 instalaciones en skills.sh0
