bf-rebuild-plan

specclaw bf-rebuild-plan

First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).

Turn the four analysis documents — plus, when present, decisions.md, clarifications.md, and the baseline outputs (manifest.json/scenarios.md) — into a living, ID-stable rebuild backlog. Read-only side-command — no specclaw-validate-change call, no <change> involved, matching the analyze/architecture/domain/clarify/baseline pattern.

Determine the invocation mode from the user's message: refresh mode if it contains --refresh, default mode otherwise. Additionally, if the message contains --module MOD-###, this is a module-scoped run: pass that flag through to both collect and render, unchanged.

Step 1 — Collect

specclaw-bf-rebuild-collect collect .specclaw [--refresh] [--module MOD-###]

Pass --refresh only in refresh mode, and --module MOD-### only if the user named a module. This single step:

• Checks that all five .specclaw/analysis/*.md documents exist — the four analysis documents plus module-map.md, which declares the MOD-### modules every backlog item is grouped under. If it exits non-zero for this reason, surface its stderr message to the user verbatim and stop — it names exactly which document(s) are missing and which command produces each (module-map.md comes from /specclaw:bf-domain). Don't retry, don't attempt a partial backlog from partial input, and never invent a grouping to work around a missing map.
• Fails if --module names no active module in the map, listing the ones that do exist. A withdrawn module cannot be planned — its id stays claimed as a tombstone.
• If .specclaw/analysis/rebuild-backlog.md already exists and --refresh was not passed, it exits non-zero with a refusal message — surface that message verbatim and stop. Do not delete or archive the file yourself; tell the user to re-run with --refresh, or to archive/delete it manually first if they genuinely want a from-scratch run.
• Otherwise emits one JSON object to stdout: the module roster from module-map.md (each module's id, name, active/withdrawn status, DR-### rules, and dependencies) together with the map's own PROPOSED/CONFIRMED status and this run's module_scope; the five documents' paths/line counts; which optional inputs are present (decisions.md, clarifications.md, .specclaw/baseline/manifest.json, .specclaw/baseline/scenarios.md) with their resolved paths; every clarifications.md question's id/type/blocking/answered/rules/items (ID-level facts only, no prose); which CQ-### ids have a recorded decision; the scenarios.md roster and manifest.json fixtures (id/rules/item); whether a "No Legacy Behaviour Exists" section is present; and — in refresh mode — every existing BL-### item's id/title/depends_on/rules/status/prior Gate/Verification. It also reports the next free BL-### id.