aibdd-plan

Sequence diagrams and class diagrams are generated by transforming accepted AIBDD discovery truth into a boundary-aware implementation design model. This process derives operation contracts and state schemas to produce implementation-ready design artifacts for downstream tasking.

Boundary-aware planning enforces strict CWD-anchored artifact output and a hard artifact write contract to prevent spec drift. It ensures operation contracts and state targets are derived via delegated specifier skills rather than hand-authoring formats.

Operation contracts are derived by delegating to specifier skills using accepted discovery truth as read-only input. This prevents manual formatting errors and ensures contracts align with boundary-aware operation constraints and state schemas.

When upstream discovery truth is insufficient, structured clarification is delegated to a clarify-loop to identify and resolve gaps. This safety mechanism ensures missing requirements are addressed before deriving operation contracts and design artifacts.

Python3 is required to run the aibdd-plan workflow scripts that transform discovery truth into implementation design models. The scripts handle boundary-aware artifact generation, contract derivation, and sequence diagram output within the current working directory.

Boundary-aware planning requires accepted AIBDD discovery artifacts as read-only input and cannot operate without them. It relies on specifier skills for contract formats and clarify-loop delegation, meaning incomplete upstream discovery will interrupt the planning workflow.