beads-seed

To generate epics and stories from architecture docs, use a deterministic seeding workflow that maps architecture artifacts to a structured beads graph, automatically creating the connected items and wiring their dependencies.

A beads graph is a versioned issue structure that connects epics, stories, and tasks. It bridges architecture planning documents describing what to build with the implementation tracking of how it is built.

Wiring dependencies between tasks seeded from architecture artifacts happens automatically during the graph initialization process, reflecting architectural constraints and sequencing directly within the versioned beads structure.

You need to seed an issue graph from architecture documentation when your planning artifacts describe what to build and why, requiring a structured breakdown of epics, stories, tasks, and dependencies to track implementation.

Yes, you can initialize a versioned beads graph from existing planning artifacts by applying a deterministic seeding workflow that parses the architecture documents to form the initial connected structure.