aibdd-reconcile

What problem does it solve?

AIBDD reconcile prevents downstream artifacts from silently drifting when an upstream defect or requirement change affects an existing plan package by reclassifying the earliest impacted planner and replaying only the reconcilable planner chain.

Core Features & Use Cases

• Boundary-aware reconciliation: Reconciles only the fixed planner suffix chain aibdd-discovery → aibdd-plan → aibdd-spec-by-example-analyze.
• Session-based archival: Archives the current plan package root entries into archive/<session_id>/ (or merges into an in-flight session) to preserve traceability and avoid duplicate work.
• Trigger classification & cascade replay: Classifies the earliest affected planner from a merged trigger history and advances the session replay pointer as each planner completes.
• Human-readable narrative output: Writes RECONCILE_RECORD.md summarizing the session, trigger history, chosen earliest planner, and cascade chain.
• Stale follow-up reminder: Ensures users re-derive tasks and re-run implement after /aibdd-reconcile completes because /aibdd-tasks and /aibdd-implement are treated as expired.

Quick Start

Run a reconcile trigger for an existing numbered plan package path and provide a defect or requirement change description so the skill archives the snapshot and replays the impacted planners.