speckit-implement-epic

Epic automation executes all tasks within a development epic continuously, progressing from one to the next without manual confirmations. It handles ready tasks sequentially and blocks execution only when encountering unresolved blockers.

Auto-continue for batch epic implementation is an unattended execution mode for large-scale software tasks. It is needed when manual confirmation for each individual task is infeasible, enabling continuous progression until completion or a block.

Spec context is loaded automatically at task start and after context compaction. This ensures automated epic execution remains fully aligned with the original specifications throughout the continuous progression.

Yes, unattended large-scale epic implementations include memory state setup and state-management protocols. These recovery workflows handle validation loops and ensure task state is maintained until the epic is fully complete or blocked.

When automated task execution encounters a blocker, the system halts progression and triggers blocked handling protocols. This prevents further automated execution until the blocker is resolved and the task is ready.

No, unattended batch task automation includes built-in validation loops and recovery workflows. The system automatically handles quality validation during continuous progression without requiring manual intervention.