Release Planning Loop

Goal

Prepare release plan

How to Run

Run this loop after sprint completion to validate release preparedness. The agent will guide you through planning steps, check for completeness, and iterate until ready.

1. 01

   Start Loop

   Input your release context and version details to initiate the planning process

2. 02

   Execute Planning Step

   Follow the agent's workflow step instructions to gather requirements and assess readiness

3. 03

   Run Check Command

   Execute 'release readiness review' to verify current planning status

4. 04

   Inspect Results

   Review the agent's output and address any identified gaps or issues

5. 05

   Iterate if Needed

   Continue the loop until all checklist items are satisfied and exit condition is met

Workflow Steps

1. 01

   Define Release Scope

   Identify features, bug fixes, and technical debt items included in this release

2. 02

   Assess Current Status

   Evaluate development progress and testing coverage for all scoped items

3. 03

   Identify Risks and Dependencies

   Document potential blockers, cross-team dependencies, and mitigation strategies

4. 04

   Create Release Timeline

   Establish milestones including code freeze, testing windows, and deployment dates

5. 05

   Plan Resource Allocation

   Assign responsibilities for QA, documentation, deployment, and post-release monitoring

6. 06

   Prepare Release Notes

   Draft user-facing documentation describing what's new and changed in this release

Start the "Release Planning Loop" loop.

Goal: Prepare release plan
Max iterations: 10
Between iterations run: release readiness review
Exit when: Checklist complete


I'm preparing a release plan. Please help me organize this systematically. Here's my context: Target release version is v2.5.0, planned for next Friday. Major features include user authentication overhaul and payment gateway integration. What should be our first planning step? Let's start with 'release readiness review'.

Self-pace this loop. After each iteration, run `release readiness review` and evaluate the output, and only continue if the exit condition is not met (Checklist complete). Stop when the exit condition passes or 10 iterations are reached. Give a short status update each pass.