settled-reach/whatsinagame/templates/.claude/skills/sprint-start/SKILL.md

name, description, user-invocable, allowed-tools

name	description	user-invocable	allowed-tools
sprint-start	Start sprint work on a team branch. Use when the user says "start sprint", "start working", "begin sprint", or invokes /sprint-start. Merges main into the team branch, finds the active sprint, reads the sprint briefing, and presents the work plan with ticket details.	true	Bash, Read, Grep, Glob, TeamCreate, Task, TaskCreate, TaskUpdate, TaskList, SendMessage, AskUserQuestion

Start Sprint Skill

Prepare a team branch for sprint work: sync with main, load the sprint briefing, and present actionable next steps.

Workflow

1. Determine the team

The current branch IS the team. Read it with:

git branch --show-current

If on main, ask the user which team branch to check out first.

2. Sync with main

git fetch --all
git merge origin/main --no-edit

If the merge has conflicts, report them and stop — do not force-resolve.

3. Load sprint context

Run the sprint CLI to get the full context dump in one shot:

db/connectors/sprint start-work

This auto-detects the active sprint and current team from the branch. It outputs: sprint metadata, briefing paths, decision refs, actionable tickets, blocked tickets, and done tickets.

If no active sprint is found, report that and stop.

4. Read the sprint briefing

Read the briefing file(s) listed in the start-work output (e.g. docs/sprints/sprint-N/<team>.md and joint.md). If no matching briefing exists for the team, suggest running /sprint-plan to generate one.

5. Load ticket details

For tickets that need more detail than the start-work summary provides:

db/connectors/ticket show <id>

6. Read key decisions

Read the decision files referenced in the sprint briefing so the agent has full architectural context before starting work.

7. Present the work plan

Output a summary:

• Sprint name and goal
• Branch status (clean merge or conflicts)
• Actionable tickets (unblocked, ready to start)
• Blocked tickets (and what blocks them)
• Key decisions loaded
• Suggested first task (lowest ID unblocked ticket)

Do NOT mark any ticket as in_progress yet.

8. Confirm and spawn the team

Before spawning agents, use AskUserQuestion to confirm the work plan and agent lineup with the user. If declined, stop.

Once confirmed:

8a. Parse agents from the briefing

Extract agent names from the **Agents:** line. Format:

**Agents:** Name (role), Name (role), ...

Map each name to its subagent_type (lowercase). Check the .claude/agents/ directory for the available agent roster and their types.

8b. Create the team

TeamCreate(team_name: "sprint-{N}-{team}")

This makes you the team lead.

8c. Create tasks from tickets

For each ticket in the briefing, create a task:

TaskCreate(
  subject: "#{id}: {title}",
  description: "Full ticket details from step 5, plus briefing notes
    and integration points for this ticket.",
  activeForm: "Working on #{id}: {short_title}"
)

After creating all tasks, mirror the dependency chain from the briefing using TaskUpdate with addBlockedBy.

8d. Spawn agents

For each agent from the **Agents:** line, spawn a teammate in the background. Spawn all agents in parallel (one message, multiple Task calls):

Task(
  subagent_type: "{name_lowercase}",
  team_name: "sprint-{N}-{team}",
  name: "{name_lowercase}",
  prompt: "You are on the {team} team for Sprint {N}.
    Branch: `{team}`

    1. Read the sprint briefing: docs/sprints/sprint-{N}/{team}.md
    2. Read the decision files referenced in the briefing.
    3. Check TaskList for available work.
    4. Claim an unblocked task (TaskUpdate with owner: your name),
       mark it in_progress, and implement it.
    5. When done, mark the task completed and check TaskList for
       the next available task.

    Use `db/connectors/ticket show <id>` for full ticket specs.",
  description: "Sprint {N} {team}: {name}",
  run_in_background: true
)

8e. Report

Output to the user:

• Team name: sprint-{N}-{team}
• Agents spawned (names and roles)
• Tasks created (count actionable vs blocked)
• How to interact: SendMessage to talk to agents, TaskList to check progress

You are now the team lead. Agents work autonomously — monitor via TaskList, communicate via SendMessage, and handle blockers as they arise.