Prompt file imported from ParseANull/SDLCGroundcontrol (.github/prompts/release-train-planning.prompt.md). Copyright stays with the author.

Release-Train Planning Prompt

Use this prompt for multi-sprint planning toward a target release milestone.

When not to use:

• Do not use when release target windows and ownership are undefined.

Input checklist:

• Release window and milestone context defined
• Capacity and sprint calendar available
• Weekly planning outputs collected
• Dependency and risk context compiled

Output template:

• Release objective and boundaries
• Milestone map
• Critical dependency path
• Risk-window mitigation plan
• Gate checklist and contingencies

Inputs:

• Target release date or window
• Sprint calendar and team capacity outlook
• Weekly planning outputs and priority candidates
• Dependencies, external milestones, and known constraints
• Quality, reliability, and operational readiness signals

Output format:

• Release train objective and scope boundaries
• Milestone map by sprint (must-have, should-have, stretch)
• Dependency critical path with owners and dates
• CI/CD risk window analysis and mitigation plan
• Readiness gate checklist by milestone
• Contingency and descoping plan

Must-check items:

• Each milestone item has clear acceptance criteria and readiness status.
• High-risk items include explicit fallback, rollback, or descoping options.
• Critical dependencies have owners, decision deadlines, and escalation paths.
• Capacity planning includes operational load, support obligations, and incident overhead.
• Gate reviews align with PR controls, testing requirements, and release-readiness criteria.

Dependency risk rubric application:

• Mark each critical path dependency as low, medium, or high.
• Require explicit fallback path for each high dependency.

Definition of Done mini-checklist:

• Must-have scope is fully owner-assigned
• Every high-risk milestone item has fallback or descoping option
• Readiness gates are linked to evidence-producing prompts

Method alignment:

• Agile: deliver value in incremental milestones and re-prioritize continuously.
• Scrum: map milestones to sprint goals and commitment reality.
• Lean: reduce batch size and carry less unfinished release scope.
• BDD: ensure milestone stories remain behavior-validated and testable.
• Garage Method: validate assumptions early and scale only proven increments.