pm-reconcile-statuslisted

Progress dashboard for an in-flight reconciliation rebuild. Reads the Reconciliation Plan and state.json, shows which areas are done, in progress, and pending, surfaces open business-logic divergences that still need the team's decision, and routes to the next area command. Run it every time you sit down to a multi-session reconcile. Read-only - it changes nothing.
ljucask/pureinn-product-development · ★ 1 · AI & Automation · score 77

Install: claude install-skill ljucask/pureinn-product-development

# PM - Reconcile Status ## Agent mode (`--agent`) Supports `--agent`: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note. - **No flag** → interactive (default); if inputs are heavy, offer agent mode. - **`--agent`** → obey. First check inputs are complete. Anything missing: do NOT invent it - mark `[ASSUMED - what/why]` in the output and summary. Never hallucinate to fill a gap. --- ## What this skill does A read-only dashboard for a reconciliation rebuild driven by `pm-reconcile`. Because reconciliation runs across multiple sessions, this skill answers "where are we" at a glance: which areas are done, what is next, and which divergences still need a human ruling. It writes nothing. Run it whenever you return to a reconcile in progress, before deciding what to do next. --- ## Dependencies - `pm-reconcile` plan exists: `reconcile/reconciliation_plan.md` and `state.json reconcile.areas[]`. If no plan exists, do not guess. Tell the user: ``` No reconciliation plan found. Run /pm-reconcile first to inspect the docs and build the plan. ``` --- ## Step 1: Read state Read `state.json reconcile` (machine source of truth for status) and `reconcile/reconciliation_plan.md` (area definitions). If they disagree, trust `state.json` and note the drift. Read `reconcile/reconciliation_report.md` to count and list open divergences (`DIV-NN` rows with no ruling, and any "Open questions for the team"). If a `recon