Are the epic requirements fixed or flexible?

Epic requirements are treated as an immutable contract to ensure project goals are met, while individual tasks are flexible and adapt to technical realities discovered during coding.

Can I resume a development plan after clearing my terminal context?

Yes, the skill uses persistent 'bd' state to identify open epics and active tasks, allowing you to resume work exactly where you left off by checking the project state.

How does it handle complex implementation steps?

It breaks tasks down into 4-8 TodoWrite substeps, ensuring that tests are written, implemented, and verified before a task is marked as closed.

What is a mandatory checkpoint in this skill?

A mandatory checkpoint is a hard stop after every completed task that allows the user to review implementation, clear context, and approve the next step to ensure quality control.

What is SRE task refinement?

It is an automated analysis step that applies 7-category corner-case analysis to new tasks, identifying potential edge cases and failure modes before coding begins.

Iterative Plan Execution

Name: Iterative Plan Execution
Author: withzombies

bywithzombies

•

Productividad y Flujo de Trabajo

Executes complex development plans through iterative task tracking, continuous learning, and mandatory human-in-the-loop checkpoints.

Acerca de

This skill manages the systematic implementation of development epics by executing tasks one at a time, ensuring rigorous validation at every step. It bridges the gap between high-level planning and low-level coding by enforcing mandatory checkpoints, allowing the AI to adapt tasks based on real-world discoveries while keeping epic requirements immutable. By integrating SRE-style refinement and automated task tracking, it prevents context exhaustion and maintains high-quality code standards through a structured execute-review-refine loop.

Características Principales

Adaptive task refinement using SRE-style corner-case analysis with Opus 4.1
Mandatory user review checkpoints to prevent runaway execution and context bloat
Immutable Epic requirement enforcement to prevent watering down original goals
13 GitHub stars
Automatic resumption support for long-running workflows across multiple sessions
Iterative task execution with persistent state tracking via beads (bd) commands

Casos de Uso

Implementing multi-step feature epics that require adaptation to discovered technical debt
Managing large-scale refactors where each step must be verified before proceeding
Maintaining development workflows that exceed single-session context limits

Acerca de

Características Principales

Adaptive task refinement using SRE-style corner-case analysis with Opus 4.1
Mandatory user review checkpoints to prevent runaway execution and context bloat
Immutable Epic requirement enforcement to prevent watering down original goals
13 GitHub stars
Automatic resumption support for long-running workflows across multiple sessions
Iterative task execution with persistent state tracking via beads (bd) commands

Casos de Uso

Implementing multi-step feature epics that require adaptation to discovered technical debt
Managing large-scale refactors where each step must be verified before proceeding
Maintaining development workflows that exceed single-session context limits