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 | open-questions ...) one layer at a time. Produces a living Reconciliation Report and rebuilds the 5 Live Registers clean, including consolidating scattered open questions/divergences/blockers into the Open Questions Register. 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
ljucask/pureinn-product-development · ★ 2 · AI & Automation · score 78

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. --- ## Standalone run Needs the artifacts listed under **Dependencies** - it synthesizes them, so without them there is nothing to synthesize. - No workspace, or inputs missing: name which are missing and what each one unlocks, then offer the PREREQ paths - proceed on stated assumptions marked `[ASSUMED - what/why]`, or route to the skill that produces the missing input. Never hard-block, and never invent the input. - Writing never depends on `/pureinn` having run: with no workspace, create just the folder this skill writes into, or write to a path the user names, and say where the file went. - Read `pureinn-variables.md` / `state.json` where a value is actually used, not at the top of the run. Missing value: continue and name the capability it costs. --- ## 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-