beads-seed

Bridge the gap between architectural planning and implementation tracking by seeding the beads issue graph from architecture documentation.

When to use

Use this command after completing architectural planning and before starting implementation. Also apply when new architectural decisions are made mid-project that require new work items.

This transition point occurs when you have stable architecture documents describing WHAT to build and WHY, and need to create the beads structure tracking HOW and WHEN.

Input: Architecture documentation

Architecture and planning documents serve as source material:

• System design documents describing overall architecture
• Component breakdown documents identifying major subsystems
• Feature specifications detailing user-facing capabilities
• ADRs (Architecture Decision Records) explaining technical choices
• Technical specifications with implementation approaches