pm-reconcilelisted

Rebuild playbook for an existing product onboarded to Pureinn. Reconciles the actual codebase against a folder of legacy documents (BRD, FSD, domain/entity models, business rules) that may contain logical, semantic and structural inconsistencies. Runs in two phases - first PLAN (inspect docs + code, define which areas to reconcile, in what order, into which Pureinn artifacts), then per-area EXECUTION (/pm-reconcile domain | rules | features ...) one layer at a time. Produces a living Reconciliation Report and rebuilds the 4 Live Registers + feature inventory clean. A closing verify pass (/pm-reconcile verify) re-reads the source one last time, proves every unit was transposed, incorporates any gaps it finds (not just reports them), and rules whether the legacy source is safe to archive - the source-disposal gate. The source is whatever the user points to (any format), never a hardcoded BRD. Use when a product was built outside the framework, has stale or conflicting docs, and the (often new) team needs one co
ljucask/pureinn-product-development · ★ 1 · AI & Automation · score 77

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

# PM - Reconcile (Rebuild from Existing Product) ## Agent mode (`--agent`) This skill's value is the live dialogue - `--agent` is not supported. If invoked with `--agent`, warn once ("this skill needs interactive back-and-forth; agent mode would hollow it out") and proceed interactively. --- ## What this skill does Takes an existing product - working code plus a pile of legacy, possibly inconsistent documentation - and rebuilds a clean Pureinn structure that matches reality. It runs in **two phases**: 1. **PLAN** - inspect the old-docs folder and the codebase surface, detect which areas exist, map each to its target Pureinn artifact, and define the order. Output: `reconciliation_plan.md`. 2. **EXECUTE per area** - `/pm-reconcile [area]` reconciles one layer at a time in the planned order, asking about real business-logic conflicts, appending to a living Reconciliation Report, and rebuilding that layer's register. Reconciliation can span multiple sessions. Progress is held in `state.json` and shown by **`/pm-reconcile-status`**. This is the **Rebuild playbook** referenced in the `/pureinn` orchestrator. Run it when a product was built outside Pureinn, legacy docs disagree with the code and each other, and the (often new) team needs one trustworthy source of truth. --- ## Invocation modes | Command | Mode | Does | |---|---|---| | `/pm-reconcile` | **Plan / route** | No plan yet → build the Reconciliation Plan. Plan exists → short status + point to the next area (ful