Existing proposals
Problem
Agent Zero's initial workflows start from existing pull requests. To handle broader software-engineering work, it needs a bounded way to turn a scoped GitHub issue into an investigated, implemented, verified, review-ready pull request without becoming an unrestricted autonomous coding agent.
Parent roadmap: #5
Desired outcome
Deliver the v0.4 issue-to-PR workflow milestone.
Acceptance goals:
- accept scoped GitHub issues as task inputs
- investigate repository context and define acceptance criteria
- implement changes in isolated branches
- verify changes before opening pull requests
- produce review-ready PR descriptions with evidence
- support human approval gates for high-impact changes
Likely area
GitHub adapter
Safety and compatibility
High impact. Issue text is untrusted input and must not override repository policy or agent safety constraints. Work must occur in isolated branches/runners, respect explicit write permissions and budgets, and require human approval where impact or uncertainty exceeds policy. A PR must not claim success unless verification evidence supports it.
Alternatives considered
Allowing arbitrary natural-language tasks without repository-scoped acceptance criteria was rejected because it makes authority and completion ambiguous. Direct commits to protected/default branches were rejected; the intended output is a reviewable pull request with evidence and explicit approval gates.
Existing proposals
Problem
Agent Zero's initial workflows start from existing pull requests. To handle broader software-engineering work, it needs a bounded way to turn a scoped GitHub issue into an investigated, implemented, verified, review-ready pull request without becoming an unrestricted autonomous coding agent.
Parent roadmap: #5
Desired outcome
Deliver the v0.4 issue-to-PR workflow milestone.
Acceptance goals:
Likely area
GitHub adapter
Safety and compatibility
High impact. Issue text is untrusted input and must not override repository policy or agent safety constraints. Work must occur in isolated branches/runners, respect explicit write permissions and budgets, and require human approval where impact or uncertainty exceeds policy. A PR must not claim success unless verification evidence supports it.
Alternatives considered
Allowing arbitrary natural-language tasks without repository-scoped acceptance criteria was rejected because it makes authority and completion ambiguous. Direct commits to protected/default branches were rejected; the intended output is a reviewable pull request with evidence and explicit approval gates.