feat(squad): add sprint planning workflow#29
Conversation
- Add Sprint Planning ceremony to ceremonies.md - Add sprint planning route to routing.md (Ralph + Aragorn) - Add sprint-planning skill injection row to routing.md Skills section - Add guardrail 6: trigger planning ceremony on every plan.md change - Create .squad/playbooks/sprint-planning.md (8-step playbook) - Create .squad/skills/sprint-planning/SKILL.md Closes #28 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
SummarySummary
CoverageAppHost - 0%
Domain - 93.4%
ServiceDefaults - 0%
Web - 68.1%
|
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a standardized Sprint Planning workflow to the squad process docs, triggered by plan.md creation/material updates, and documents the responsibilities split across Ralph/Aragorn/Boromir.
Changes:
- Added a Sprint Planning ceremony entry to the ceremonies template.
- Introduced a new sprint-planning playbook and a corresponding injectable skill.
- Updated routing to include sprint planning responsibilities, skill/playbook injection, and a new guardrail.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| .squad/templates/ceremonies.md | Documents the Sprint Planning ceremony trigger, roles, and agenda. |
| .squad/routing.md | Routes sprint-planning work, adds injection guidance and a guardrail for plan.md updates. |
| .squad/playbooks/sprint-planning.md | Full end-to-end playbook describing milestones, issues, project board usage, and worktrees. |
| .squad/skills/sprint-planning/SKILL.md | Skill card to inject the sprint-planning workflow and CLI patterns into agent prompts. |
| Planning is **mandatory for ALL plans** — see `.squad/ceremonies.md` (Sprint | ||
| Planning ceremony) for the trigger and participants. |
There was a problem hiding this comment.
This references .squad/ceremonies.md, but the ceremony added in this PR is in .squad/templates/ceremonies.md. If .squad/ceremonies.md doesn’t exist (or isn’t generated), this link will be broken; update the reference to the correct path (or add the expected file) to keep documentation navigable.
| # Sprint Planning Playbook | ||
|
|
||
| **Owner:** Ralph (decomposition) + Aragorn (GH artifacts) + Boromir (worktrees) | ||
| **Ref:** `.squad/ceremonies.md` (Sprint Planning ceremony) |
There was a problem hiding this comment.
Same issue as the skill doc: this points to .squad/ceremonies.md but the ceremony entry in this PR is under .squad/templates/ceremonies.md. Update the reference (or ensure the referenced file exists) so readers can follow the link.
|
|
||
| **Naming convention:** `Sprint {N}: {Theme}` (e.g., `Sprint 1: Foundation`) | ||
|
|
||
| Note the milestone number returned — you will need it for Step 5 and Step 7. |
There was a problem hiding this comment.
Step 5 is worktree/branch setup and doesn’t use a milestone number. This is internally inconsistent and can confuse the operator; update the text to reference only the steps that actually require the milestone number (e.g., Step 7), or adjust the steps so the milestone number is used where claimed.
|
|
||
| ```bash | ||
| # 1. Ralph verifies 100% milestone completion | ||
| gh api repos/mpaulosky/MyBlog/milestones/{N} | jq '{title,open_issues,closed_issues}' |
There was a problem hiding this comment.
In the GitHub API, {N} here is interpreted as the milestone number/ID, which typically won’t match the sprint sequence number (Sprint 1/2/3). The playbook correctly distinguishes {milestone_number} later; this command should also use {milestone_number} (or clearly state how to look it up), otherwise the documented command is likely to query the wrong milestone or 404.
| ## Step 4 — Aragorn: Add Issues to Project Board | ||
|
|
||
| Add each new issue to the **MyBlog** GitHub Project: |
There was a problem hiding this comment.
The PR description notes a manual prerequisite (project creation + project OAuth scope via browser flow), but the playbook/skill don’t call this out. Since Step 4 depends on that prerequisite, add a short prerequisite note here (and/or in the skill) explaining the required auth scope and that the project must exist, otherwise the workflow will fail when run 'automatically' on plan.md updates.
- Replace {PROJECT_NUMBER} placeholder with project 4 (MyBlog)
- Repo linked to https://github.com/users/mpaulosky/projects/4
- Status columns confirmed: Backlog, In Sprint, In Review, Done, Released
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Summary
Implements the standard sprint planning workflow decided in session, triggered on every
plan.mdcreation or material update.Changes
.squad/templates/ceremonies.md.squad/routing.md.squad/playbooks/sprint-planning.md.squad/skills/sprint-planning/SKILL.mdWorkflow Added
On every
plan.mdcreation or material update:Sprint N: {Theme})squad:{member}labelssprint/{N}-{slug}branch +../MyBlog-sprint-{N}/worktreeGitHub Project board ("MyBlog" with columns: Backlog → In Sprint → In Review → Done → Released) cannot be created headlessly — it requires the
projectOAuth scope via browser flow.To create it:
Closes #28