validate-beads

You can validate bead definitions by running a quality gate check that ensures self-containment, complete spec coverage, and correct dependencies. The process maps requirements to beads and automatically creates missing gaps beads when needed.

To check for orphan work, run a validation workflow after completing your decomposition plan. It performs orphan and dependency validation to ensure proper scope and acyclic dependencies across all generated beads.

Self-containment checks validate that every bead definition includes a clear Task and Acceptance Criteria. Running the validation workflow after decompose-plan verifies this quality before implementation begins.

Yes, the validation process automatically fixes issues and creates missing beads as needed. It enforces required sections, cross-bead mappings, and dependency integrity using the beads toolkit and updates the decomposition log.

Dependency validation ensures proper scope and acyclic dependencies across beads. It verifies dependency integrity during planning and execution workflows to prevent circular references and orphan work.

Run spec coverage validation immediately after completing a decomposition plan and before implementation begins. This verifies bead quality, maps requirements to beads, and creates gaps beads for any missing coverage.