Use this skill to create Beads from a plan/spec and do the review pass so implementers can just pick up issues and ship.
使用此技能根据计划/规格创建Beads，并完成审核环节，以便实施人员可以直接接手议题并推进交付。
Workflow
工作流程
Load beads guidance if needed
If bd CLI usage or bead structure is unclear, consult the official Beads GitHub repo at
https://github.com/steveyegge/beads
and follow the documented workflow for your installed
bd
version.
Decide which mode you are in
If the user has a finalized plan/spec and wants Beads filed: do Create mode.
If the user already has Beads and wants them improved: do Review mode (skip straight to step 5).
Confirm the plan is ready (Create mode)
Ensure there is a finalized plan or spec outside Beads.
If the plan is still fuzzy, ask for revisions first and iterate up to 5 times before importing.
Translate the plan into Beads structure (Create mode)
Create epics that map to major milestones or deliverables.
Create issues for concrete, implementable tasks.
Hierarchy rule: When an epic has child milestones/tasks, create them as
hierarchical children (dotted IDs like
EPIC.1
,
EPIC.2
) rather than
separate top-level issues with only parent-child deps. Follow the bd CLI
“Create epic with hierarchical child tasks” flow (create the epic, then
create children so bd auto-assigns
EPIC.N
IDs). Verify the returned IDs;
if bd doesn’t assign dotted IDs, stop and ask the user how to proceed.
Add dependencies, ordering constraints, and opportunities for parallel work.
Review and polish (Create mode + Review mode)
Fix vague titles, missing acceptance criteria, or unclear scope.
Ensure each issue is something one agent can do in a single task.
Verify dependencies, sequencing, and opportunities for parallel work.