iterate-on-implementation

Automate feature implementation refinement by loading rework reports, prioritizing iterate actions, running quality checks, and updating OpenSpec documents to systematically identify and resolve defects.

Prioritize defect fixes by surfacing iterate-actions first, followed by revisions to specs or deferrals as needed, ensuring structured iteration cycles across OpenSpec changes.

Structured defect identification works by gathering findings from code changes, OpenSpec deltas, and rework reports to guide targeted improvements and produce a final consensus summary.

Yes, you need an OpenSpec change-id to invoke the iteration process, which targets the specific openspec/changes/<change-id> directory to run quality checks and update impl-findings.

Automated iteration cycles are not suitable when your development pipeline lacks structured OpenSpec documents or when rework reports and impl-findings are not generated for defect tracking.

Close an iteration cycle by running integrated quality checks, updating impl-findings, and producing a final consensus summary that aligns feature code with OpenSpec throughout the refinement process.