implement

To execute implementation plans from beads issues in parallel, you invoke the skill with a beads issue id. It automatically detects epic versus task hierarchies and spawns Claude worker teams for concurrent software engineering execution.

Swarm orchestration automatically detects whether a beads issue is an epic or a single task, then coordinates either a parallel worker swarm or solo execution based on the extracted context. This ensures appropriate resource allocation for different engineering workflow scales.

Yes, you can use this for solo software engineering tasks. The skill automatically coordinates solo work based on context when a beads issue does not require parallel swarm execution, maintaining the same stepwise workflow and error recovery.

The stepwise workflow for beads tasks includes task discovery, context extraction, worker setup, and wave completion. It stepwise claims tasks, reads context, closes tasks, and reports results while including robust error handling and recovery throughout the process.

Wave-based progress handles errors during parallel execution through robust error handling and recovery mechanisms. These ensure that worker spawn failures or task execution errors are captured and managed without halting the entire software engineering workflow.

No, you do not need to manually set up worker prompts for swarm collaboration. The skill automatically handles swarm setup and generates worker prompts based on the extracted context from your beads issues during the implementation workflow.