Automated issue advancement

[tobio]

At a high level:

• Undesigned issues are automatically picked up by an iterative design workflow
• Designed and planned issues are automatically picked up by an implementation workflow

Those workflows must:

• Have a hard iteration ceiling to stop runaway bad plans
• Be focussed on minimising human review time. People should be able to look at a thoroughly reviewed and AI approved PR with a high level of confidence that it will be mergeable the first time around. This won't happen overnight, but it's the north star in any design decision/prompt evaluation.
• Be token/model/cost efficient.
• Have a manageable DOP. Maybe this means pausing when there's X human-ready PR. Maybe human review throughput is it's own backpressure (though that sounds mentally overwhelming).
• Have appropriate stop conditions. For implementation this is easier, since we have a thorough change proposal. Thought needs to be put into when a design proposal is human ready.

[github-actions]

Thanks for filing this! I've added the needs-human label to this issue.

This issue describes a high-level process/automation vision for automated issue advancement workflows. While the ideas are interesting, the issue is more of a meta-discussion or roadmap item than a concrete feature request or bug report with enough specificity to route to an automated pipeline — it doesn't name a particular Terraform resource, API, or schema design that implementers could act on directly.

A maintainer will review it shortly to determine the best path forward. In the meantime, feel free to add more detail — for example, a breakdown of specific tasks, a proposed design, or links to related issues.

If I've misclassified this, please leave a comment and a maintainer can adjust the label manually.