epic-executor

To orchestrate beads epics sequentially, provide an epic-id to initiate end-to-end processing. The workflow coordinates subagents to execute tasks one at a time, avoiding conflicts and ensuring traceable completion across the entire epic.

The two-stage review workflow for task automation enforces mandatory verification before closing any task. It first conducts a spec compliance review, then immediately follows with a code quality review to ensure both standards are met.

Epic execution tracks task state transitions deterministically through statuses like in_progress, approved, needs_changes, and closed. It records epics context and base SHA for complete auditability and traceable completion across multiple tasks.

No, bead-epic workflows enforce sequential, one-task-at-a-time execution. This deterministic pipeline prevents conflicts and ensures precise staged reviews are completed for each task before moving to the next.

Yes, you must provide an epic-id to begin processing tasks end-to-end. This identifier initializes the context management, status tracking, and base SHA recording required for the staged review pipeline.

You should avoid this deterministic epic execution pipeline if your workflow requires parallel task processing or if your project does not rely on the beads epic structure and subagent coordination for code review.