write-beads

To convert a Technical Design Document into a BEADS.md file, you use a task-decomposition workflow that transforms the TDD into atomic beads. This produces a structured document with dependency scripts and gating decisions ready for autonomous agents.

Task decomposition into BEADS is the process of breaking down a polished Technical Design Document into atomic, executable units. It structures work into a BEADS.md format that includes dependency scripting and gating for tool-assisted implementation.

Generating an Add-Dependencies script is handled automatically during BEADS.md creation. The workflow orchestrates bead generation and outputs a complete dependency script to apply after the atomic beads are created.

Yes, the BEADS.md format supports gating decisions through DECISION beads where needed. It includes parallelism metadata and gating logic specifically to enable swarm orchestration and autonomous agent execution.

You need a polished Technical Design Document as input. The skill processes the TDD to output a BEADS.md document containing atomic beads and a complete Add-Dependencies script suitable for import into the bd workflow.

You should use DECISION beads in task decomposition when your workflow requires gating between dependent tasks. They are inserted during BEADS.md generation to control execution flow and handle conditional logic for autonomous agents.