implement-issue

Topics in the source

• Implement one issue
• Phases
• Runner tools
• Time budget
• Trust boundary
• Reviewer notes
• Verification contract
• 1. Read the issue (phase readissue)

Every run walks nine phases, named in each step heading below: readissue, pincriteria, plan (which starts by exploring the repository), planreview, failingtest, implement (which also runs the checks), reviewdiff, publish and waitci. The plan review is one advisory round: plan and planreview run once. Two pairs loop: implement and reviewdiff, at most 5 completed rounds, then waitci back to implement when the pull request's checks fail, at most 3 rounds. Call mcpcuriereportprogress once when you enter a phase, not while you work in it: report before the phase's first tool call, and do not report the same phase again while you stay in it. Every phase except waitci, which the platform reports, gets one report per entry — a new round of a loop, or the return from waitci to implement, is a new entry. Pass phase set to that phase's id, round for plan, planreview, implement and reviewdiff, and an optional one-line note saying what you are about to do. The note is public on the issue, so it must contain no secrets and no raw tool output. If the tool returns an error, continue the work; progress never blocks the run. Every message you send must include a tool call until you have called mcpcu

This is an excerpt. Refer to the complete source and its current requirements.