jpmschweitzerandClaude Opus 4.6
b025fe8152
Remove the db/connectors → tooling/db/ symlink added in Sprint 21 (#274) and migrate all references to use tooling/db/ directly. - Delete tracked symlink from db/connectors - Remove duplicate db/connectors/* permission patterns from settings - Update project-structure.md to reflect removal - Move whatsinagame/static/db/connectors/ to whatsinagame/static/tooling/db/ - Update 20 whatsinagame template, skill, and test files - Update comment references in client/tests/test_anti_tedium.gd - Historical docs (old sprint briefings, changelog, discussions) left as-is Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.3 KiB
2.3 KiB
name, description, user-invocable, allowed-tools
| name | description | user-invocable | allowed-tools |
|---|---|---|---|
| sprint-retro | Run a sprint retrospective. Use when the user says "run retro", "retrospective", "what went well", or invokes /sprint-retro. Scans git history and ticket outcomes for the sprint period, generates a structured retro document. | true | Bash, Read, Grep, Glob, Write, Task |
Sprint Retrospective
Run a structured sprint retrospective by gathering data from git history, ticket outcomes, and PR activity.
Workflow
1. Identify Sprint
Find the most recently completed sprint, or accept --sprint N as argument.
- Read sprint record from DB:
tooling/db/sprint status - If a sprint number is provided, use:
tooling/db/ticket list --sprint N - Extract sprint start and end dates from the sprint record.
2. Gather Data
Collect activity data for the sprint period:
Git history:
git log --oneline --since=<start_date> --until=<end_date>
Ticket outcomes:
tooling/db/ticket list --sprint N
Categorize tickets into: done, carry-over, cancelled.
PR history:
- Count merged PRs in the period
- Calculate average review turnaround (time from open to merge)
Decision changes:
git log --oneline --since=<start_date> --until=<end_date> -- decisions/
3. Generate Retro Document
Write the retrospective to docs/sprints/sprint-N/retro.md using this structure:
# Sprint N: <Theme> — Retrospective
**Period:** <start_date> to <end_date>
**Velocity:** X/Y tickets completed (Z%)
## What Shipped
- List of completed tickets with brief descriptions
## What Went Well
- Smooth integrations, clean PRs, good velocity areas
## What Hurt
- Blockers, stalled tickets, context switching, scope creep
## What We Learned
- Process insights, technical lessons, team dynamics
## Carry-Over
| # | Title | Why it carried |
|---|-------|----------------|
## Action Items
- Concrete improvements for next sprint
4. Optional: Stakeholder Perspective
If stakeholder personas are configured, spawn 1–2 personas to comment on what shipped from a user perspective. Use the Task tool for parallel persona evaluation.
5. Report
Write the retro file to disk and report a summary to the user including:
- Velocity percentage
- Key highlights from each section
- Number of action items generated