GPT Tasks/Plan an Agile Sprint
Task library

Work · GPT Task

Plan an Agile Sprint

Turn a sprint goal, candidate backlog, capacity assumptions, dependencies, and tracking preferences into a bounded sprint plan with priorities, acceptance questions, risks, and review cadence.

Context → structured prompt → explicit AI handoff

Runs in this browser. No upload by this page. External AI handoff is explicit. Review before sharing.

Prompt workbenchConfigure → review → use
01

Configure task

Setup
Describe the outcome this sprint should move toward and what would make the sprint useful.
List candidate work items, priorities, acceptance notes, known blockers, or work that must not be included.
Prompt style
Additional options
Add team availability, ownership, holidays, dependencies, deadlines, existing commitments, or other planning assumptions.

What you’ll need

  • Sprint goal, candidate backlog, and any known capacity or dependency limits
  • Sprint goal and desired outcome
  • Candidate backlog and priorities

What you’ll get

  • Sprint goal and success signal
  • Prioritized sprint backlog
  • Candidate vs deferred work
  • Acceptance questions or definition-of-done gaps
  • Capacity and dependency assumptions
02

Prompt preview

Editable

Review or edit the generated prompt before you copy it or explicitly open an AI chat.

Export

ChatGPT opens with the current prompt prepared. Gemini copies the current prompt, then opens Gemini so you can paste it. Keep secrets and sensitive information out of URL-carried prompts.

Task referenceExamples, expected output, boundaries, and routing.

Examples

1. Software feature sprint

Context: A small product team supplies a two-week goal, prioritized tickets, one dependency, and limited designer capacity.

Goal: Choose a realistic sprint shape without fabricating estimates.

Useful output: Sprint goal, prioritized backlog, capacity assumptions, dependency warnings, tracking plan, and review prep.

2. Marketing delivery sprint

Context: A marketing team supplies campaign tasks, approvals, deadlines, and known team availability.

Goal: Plan a short sprint while separating committed work from stretch work.

Useful output: Core backlog, deferred items, approval dependencies, blocker plan, cadence, and next actions.

3. Operations improvement sprint

Context: An operations group has several process fixes and one two-week improvement goal but incomplete effort estimates.

Goal: Create a plan that exposes estimation gaps before commitment.

Useful output: Priority order, questions, assumptions, risk list, tracking format, and sprint-start checklist.

Expected output

  • Sprint goal and success signal
  • Prioritized sprint backlog
  • Candidate vs deferred work
  • Acceptance questions or definition-of-done gaps
  • Capacity and dependency assumptions
  • Risks and blocker plan
  • Tracking cadence and update format
  • End-of-sprint review preparation
  • Priority next actions

Truth boundary

Treat estimates, capacity, ownership, progress and commitments as user-provided facts or explicit planning assumptions. Do not manufacture completion, velocity, dates or team commitments.

Overlap guard: Owns a bounded, time-boxed sprint commitment decision using a candidate backlog and capacity assumptions. Use Project Plan for broader execution structure, Project Risks for a risk register, Status Update for reporting work already underway, and Product Roadmap for strategic product horizons.

Privacy and handoff

Runs in this browser. No upload by this page. Copy/download locally or explicitly open ChatGPT or Gemini. Source files are attached in the chosen AI service, not uploaded by Mycelgrid. Review the generated prompt and AI output before using or sharing it.