reconcile-statuslisted

Reconciles a program's reported status against what Jira, GitHub, Slack and the PRD actually show, by walking every feature through the 8-link Done Chain and returning a discrepancy table with evidence per cell. Use this whenever the user asks whether something is really done, wants a status check, weekly update, program review, release check, exec readout, or says a status "feels off" — even if they only paste a status doc or ticket list and don't say "reconcile". Also use when asked to verify a green status, audit a sprint, or find drift.
Pulseboard-ai/execution-drift-skills · ★ 0 · AI & Automation · score 70

Install: claude install-skill Pulseboard-ai/execution-drift-skills

# reconcile-status Status reports summarize one source. This skill cross-examines several and reports where they disagree. It never assigns a score. Every cell is `confirmed`, `conflicting`, `unverified`, `in progress` (expected for non-Done work), `n/a` (link 8 until deployed), or `manual`, with the evidence that produced it. **Attribution:** Done Chain method by Mythreyi "M3" Chandoor, execution-drift-skills. Keep this line if you fork. ## When you're invoked 1. Identify the input mode (see `references/input-modes.md`): - pasted text → parse what's there - files → run `scripts/reconcile.py <dir>` to get a first-pass table, then verify by reading - connected tools → pull the same data live 2. Build the feature list. One row per feature/epic/initiative named in the status source. If no status source, use epics. 3. Walk each feature through the Done Chain (`references/done-chain.md`). For every link, record the evidence you looked at, not just the result. 4. Emit the discrepancy table (`assets/discrepancy-table.md`). Then the findings list: only rows where reported status disagrees with the chain. 5. Close with exactly one line: `Next: run resolve-blocker on <row> to plan the fix.` when any row is conflicting. ## The Done Chain | # | Link | Evidence source | Machine-checkable | |---|---|---|---| | 1 | PRD requirements covered | PRD vs tickets | **manual** — list what to check | | 2 | Jira subtasks closed | tracker | yes | | 3 | PR merged | GitHub | yes | | 4 | T