Beads Implement
Use this skill to execute work from a bead or epic id with minimal back-and-forth.
Workflow
- •
Load beads guidance if needed
- •If bd CLI usage or bead structure is unclear, read
/Users/btraut/Development/skills-external/beads/SKILL.mdand follow its session protocol.
- •If bd CLI usage or bead structure is unclear, read
- •
Open the bead
- •Read the title, description, acceptance criteria, and dependencies.
- •If required info is missing or a dependency blocks progress, ask a single targeted question and wait.
- •
Create a brief to-do list
- •At the start of execution, create a short to-do list of the tasks/sub-tasks you plan to complete and update it as you go.
- •
Decide scope
- •If the bead is a single task, implement it directly.
- •If the bead is an epic, identify all sub-tasks and implement them in dependency order.
- •
Implement and commit
- •For each task/sub-task: implement, run relevant checks/tests, then commit.
- •Use one commit per task; include the bead id in the commit message.
- •
Communicate only when needed
- •Do not interrupt the user while work is progressing.
- •Only pause to ask for help when blocked, when information is missing, or when a meaningful decision is required.
- •
Report progress
- •Provide a concise summary of completed tasks, commits made, and what remains (if anything).