Moonshot Retro
Role
Collect compact task closeout summaries, import them into the account-root retro inbox, aggregate daily patterns, and render advisory harness improvement proposals or local issue drafts.
This skill does not change verification, score, closeout, promotion, installed profile, or runtime DB authority.
Commands
moonshot-relay retro collect --project <id> --task-id <taskId> --task-root <dir> --date <YYYY-MM-DD> --out .moonshot-relay/retro-outbox/<YYYY-MM-DD> --json
moonshot-relay retro import --project <id> --from .moonshot-relay/retro-outbox/<YYYY-MM-DD> --date <YYYY-MM-DD> --json
moonshot-relay retro daily --project <id> --date <YYYY-MM-DD> --json
moonshot-relay retro propose --project <id> --date <YYYY-MM-DD> --json
moonshot-relay retro issue-draft --project <id> --date <YYYY-MM-DD> --json
Hard Stops
- Do not copy raw logs, prompts, transcripts, browser scrapes, MemoryGraph dumps, KG dumps, ontology dumps, or secret-like strings into retro records.
- Do not treat retro output as completion authority.
- Do not create remote GitHub issues from this initial workflow.
- Do not mutate
.claude/**, .codex/**, account-root profiles, or source files from a retro finding.
Required Evidence
promotionAuthority: false on generated JSON and proposal artifacts.- Focused retro tests for schema, redaction, aggregation, proposals, issue drafts, and CLI routing.
npm test before claiming source implementation complete.
1---2name: moonshot-retro3description: Use for advisory retrospective collection, daily pattern analysis, and local improvement proposal or issue draft generation.4---56# Moonshot Retro78## Role910Collect compact task closeout summaries, import them into the account-root retro inbox, aggregate daily patterns, and render advisory harness improvement proposals or local issue drafts.1112This skill does not change verification, score, closeout, promotion, installed profile, or runtime DB authority.1314## Commands1516```bash17moonshot-relay retro collect --project <id> --task-id <taskId> --task-root <dir> --date <YYYY-MM-DD> --out .moonshot-relay/retro-outbox/<YYYY-MM-DD> --json18moonshot-relay retro import --project <id> --from .moonshot-relay/retro-outbox/<YYYY-MM-DD> --date <YYYY-MM-DD> --json19moonshot-relay retro daily --project <id> --date <YYYY-MM-DD> --json20moonshot-relay retro propose --project <id> --date <YYYY-MM-DD> --json21moonshot-relay retro issue-draft --project <id> --date <YYYY-MM-DD> --json22```2324## Hard Stops2526- Do not copy raw logs, prompts, transcripts, browser scrapes, MemoryGraph dumps, KG dumps, ontology dumps, or secret-like strings into retro records.27- Do not treat retro output as completion authority.28- Do not create remote GitHub issues from this initial workflow.29- Do not mutate `.claude/**`, `.codex/**`, account-root profiles, or source files from a retro finding.3031## Required Evidence3233- `promotionAuthority: false` on generated JSON and proposal artifacts.34- Focused retro tests for schema, redaction, aggregation, proposals, issue drafts, and CLI routing.35- `npm test` before claiming source implementation complete.36
munlucky