aibdd-discovery

Boundary-aware discovery artifacts are generated by executing discovery SOP phases sequentially from a plan spec. They enumerate atomic rules per feature file, detect specification gaps, and delegate clarification to maintain an impact matrix for downstream planning.

Extracting atomic rules and acceptance criteria from a plan spec requires running an SOP-driven discovery phase. This process enumerates rules per feature file, identifies gaps requiring fixes, and updates the plan spec as the single source of truth.

Yes, you must run aibdd-kickoff before executing the discovery workflow to generate the required arguments.yml file. The discovery process relies on resolving required arguments from this configuration to execute its SOP phases correctly.

No, you cannot generate discovery artifacts outside the current working directory due to a strict CWD-anchored artifact safety contract. All created or modified artifacts, including discovery-sourcing.md and plan reports, must remain within the current working directory scope.

When the discovery process finds insufficient evidence for acceptance criteria, it delegates clarification to the clarify-loop. This ensures that specification gaps and ambiguous atomic rules are explicitly resolved rather than guessed by the AI agent.

The discovery phase tracks changes for downstream planning by maintaining a machine-readable impact matrix via the manage_impact_matrix wrapper. This matrix records exactly which boundary truths were affected and how they influence future phases.