Idea
Generate a Method playback summary for PRs from issues, commits, checks, and witness links.
Method already cares about playbacks, witnesses, and retros. With GitHub Issues as the tracker, a small tool could synthesize the PR-level story instead of relying on agents to write bespoke summaries each time.
Possible shape
method playback --pr <number> reads linked issues, labels, commits, check results, and changed design/retro/witness files.- Emits a PR comment or Markdown block with: hill, sponsor/context, issues closed, witness evidence, checks, unresolved risks, and follow-ups created.
- Flags missing witness links for issues labeled
needs-witness.
- Flags design changes without playback notes when a label such as
needs-playback is present.
Why it matters
This makes the Method loop visible to OSS reviewers without requiring them to know the local ritual. It also lowers the chance that a PR merges with code done but witness/playback bookkeeping missing.
Acceptance sketch
- The tool can generate a read-only Markdown report locally.
- Optional
--post writes the report to the PR.
- It does not invent evidence; missing evidence is reported as missing.
- It works in any repo using canonical Method labels.
Idea
Generate a Method playback summary for PRs from issues, commits, checks, and witness links.
Method already cares about playbacks, witnesses, and retros. With GitHub Issues as the tracker, a small tool could synthesize the PR-level story instead of relying on agents to write bespoke summaries each time.
Possible shape
method playback --pr <number>reads linked issues, labels, commits, check results, and changed design/retro/witness files.needs-witness.needs-playbackis present.Why it matters
This makes the Method loop visible to OSS reviewers without requiring them to know the local ritual. It also lowers the chance that a PR merges with code done but witness/playback bookkeeping missing.
Acceptance sketch
--postwrites the report to the PR.