sprint-workflow

Sprint Workflow

A structured end-to-end development sprint using Copilot CLI's full capability stack. Inspired by Garry Tan's gstack approach — each step feeds the next, nothing falls through.

Think → Plan → Build → Review → Test → Ship → Monitor

When to Use

• Starting a new feature or significant refactor
• Any task that spans multiple files or requires sequencing
• When you want structured, reviewable output rather than ad-hoc changes
• Team environments where pull requests are the delivery mechanism

Prerequisites

• Copilot CLI authenticated (gh auth status)

• For the Review step: standard mode (no extra setup)

• For the sprint-retro skill after this sprint: enable experimental features first:

  /experimental on
  

  ⚠️ /chronicle (used in sprint-retro) requires /experimental on to be run in the same session.

The Sprint

Step 1: Think — Frame the Problem

Before writing a line, challenge the premise:

> I want to build [X]. What am I actually trying to solve?

Push back on your own framing. Identify:

• The real user pain (not the feature request)
• Assumptions that could be wrong
• The simplest possible version that delivers value

Step 2: Plan — Structured Implementation Plan

Switch to Plan Mode (Shift+Tab) and describe the task:

[Plan Mode]
> Implement paginated results for the /api/users endpoint

Copilot will ask clarifying questions, then produce a structured plan. Review it carefully. Approve with exit_plan_mode when ready.

For complex tasks, prompt for explicit sections:

[Plan Mode]
> Design the pagination feature. Include:
> 1. Data flow and API contract
> 2. Edge cases and error handling
> 3. Test plan (unit + integration)
> 4. Files to change and why

Step 3: Build — Autopilot Execution

After plan approval, switch to Autopilot Mode (Shift+Tab) and let Copilot execute:

[Autopilot Mode]
> Implement the plan

Copilot works autonomously. You can monitor progress or continue other work. For parallelizable tasks (multiple independent files), use: