|
30 | 30 | [ ] Update index.md |
31 | 31 | [ ] Update sidebars.ts |
32 | 32 | [ ] Update combined release notes (if patch release) |
| 33 | +[ ] Ask if user wants to create a PR |
33 | 34 | [ ] Generate Discord format (if requested) |
34 | 35 | </todos> |
35 | 36 | </update_todo_list> |
|
213 | 214 | </step> |
214 | 215 | </steps> |
215 | 216 | </phase> |
| 217 | + <phase name="review_and_refine"> |
| 218 | + <description>Iterative review process allowing users to refine release notes before creating a PR.</description> |
| 219 | + <loop_structure> |
| 220 | + <description>This phase loops until the user chooses to create a PR.</description> |
| 221 | + </loop_structure> |
| 222 | + <steps> |
| 223 | + <step number="1"> |
| 224 | + <action>Ask if user wants to make changes</action> |
| 225 | + <tool>ask_followup_question</tool> |
| 226 | + <details> |
| 227 | + Ask if the user wants to make any changes to the generated release notes before creating a PR. |
| 228 | + This question will be repeated after each change until the user is satisfied. |
| 229 | + </details> |
| 230 | + <example><![CDATA[ |
| 231 | +<ask_followup_question> |
| 232 | +<question>The release notes for version X.Y.Z have been created and all documentation files have been updated. Would you like to make any changes to the release notes before creating a PR?</question> |
| 233 | +<follow_up> |
| 234 | +<suggest>No, create a PR with the title "Release notes for vX.Y.Z"</suggest> |
| 235 | +<suggest>Yes, I'd like to make some changes to the release notes</suggest> |
| 236 | +<suggest>Show me the current release notes file</suggest> |
| 237 | +<suggest>Show me all changed files</suggest> |
| 238 | +</follow_up> |
| 239 | +</ask_followup_question> |
| 240 | + ]]></example> |
| 241 | + </step> |
| 242 | + <step number="2"> |
| 243 | + <action>Process user response</action> |
| 244 | + <details> |
| 245 | + Handle the user's response: |
| 246 | + - If response contains "no, create a pr" (case-insensitive): Proceed to PR creation |
| 247 | + - If "show me the current release notes": Display the vX.Y.Z.mdx file content |
| 248 | + - If "show me all changed files": List all modified files |
| 249 | + - Any other response: Treat as requested changes to implement |
| 250 | + </details> |
| 251 | + <decision_logic> |
| 252 | + <condition>Response contains "no, create a pr"</condition> |
| 253 | + <action>Exit loop and proceed to PR creation</action> |
| 254 | + <condition>Any other response</condition> |
| 255 | + <action>Implement requested changes and loop back to step 1</action> |
| 256 | + </decision_logic> |
| 257 | + </step> |
| 258 | + <step number="3"> |
| 259 | + <action>Implement requested changes</action> |
| 260 | + <details> |
| 261 | + If user provides specific changes: |
| 262 | + 1. Parse the user's request |
| 263 | + 2. Apply the changes to the appropriate files |
| 264 | + 3. Confirm changes were made |
| 265 | + 4. Loop back to step 1 to ask again |
| 266 | + </details> |
| 267 | + <todo_update>Update "Ask if user wants to create a PR" to reflect ongoing review</todo_update> |
| 268 | + </step> |
| 269 | + <step number="4"> |
| 270 | + <action>Create PR when ready</action> |
| 271 | + <details> |
| 272 | + When user selects "No, create a PR": |
| 273 | + 1. Create PR using gh pr create with title "Release notes for vX.Y.Z" |
| 274 | + 2. Include a standard PR description |
| 275 | + 3. Mark the todo item as complete |
| 276 | + </details> |
| 277 | + <example><![CDATA[ |
| 278 | +<execute_command> |
| 279 | +<command>gh pr create --repo RooCodeInc/Roo-Code --title "Release notes for vX.Y.Z" --body "This PR adds release notes for version X.Y.Z. |
| 280 | +
|
| 281 | +## Changes |
| 282 | +- Created release notes file |
| 283 | +- Updated index.md |
| 284 | +- Updated sidebars.ts |
| 285 | +- Updated combined release notes (if applicable)"</command> |
| 286 | +</execute_command> |
| 287 | + ]]></example> |
| 288 | + <todo_update>Mark "Ask if user wants to create a PR" as complete</todo_update> |
| 289 | + </step> |
| 290 | + </steps> |
| 291 | + </phase> |
216 | 292 | <phase name="discord_formatting" optional="true"> |
217 | 293 | <description>Generate Discord-formatted release notes via a subtask.</description> |
218 | 294 | <when_to_use>When user asks for Discord formatting.</when_to_use> |
|
250 | 326 | </main_workflow> |
251 | 327 |
|
252 | 328 | <completion_criteria> |
253 | | - <criterion>Release notes file created with correct formatting.</criterion> |
254 | | - <criterion>All PRs analyzed and described by user benefit.</criterion> |
255 | | - <criterion>Index and sidebar files updated.</criterion> |
256 | | - <criterion>Combined release notes updated for patch releases.</criterion> |
257 | | - <criterion>Links and references are correct.</criterion> |
258 | | - <criterion>Final release notes include only items from the version's changelog.</criterion> |
259 | | - </completion_criteria> |
| 329 | + <criterion>Release notes file created with correct formatting.</criterion> |
| 330 | + <criterion>All PRs analyzed and described by user benefit.</criterion> |
| 331 | + <criterion>Index and sidebar files updated.</criterion> |
| 332 | + <criterion>Combined release notes updated for patch releases.</criterion> |
| 333 | + <criterion>Links and references are correct.</criterion> |
| 334 | + <criterion>Final release notes include only items from the version's changelog.</criterion> |
| 335 | + <criterion>User has reviewed release notes and confirmed readiness for PR creation.</criterion> |
| 336 | + <criterion>PR has been created (or user explicitly declined PR creation).</criterion> |
| 337 | + </completion_criteria> |
260 | 338 | </workflow_instructions> |
0 commit comments