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>
1.7 KiB
1.7 KiB
name, description, user-invocable, allowed-tools
| name | description | user-invocable | allowed-tools |
|---|---|---|---|
| team-standup | Generate async standup status summary. Use when the user says "standup", "daily status", "what's happening", or invokes /team-standup. Scans recent git activity and ticket changes to generate a per-team status report. | true | Bash, Read, Grep, Glob |
Async Standup
Generate a per-team status report from recent git activity and ticket changes.
Workflow
1. Determine Time Range
Default to the last 24 hours, or since the last standup output if one exists.
Check for a previous standup file to determine the cutoff time.
2. Gather Per-Team Activity
Recent commits per branch:
git log --oneline --since="24 hours ago" --all
Ticket status changes:
tooling/db/sqlite-query "SELECT * FROM ticket_history WHERE changed_at > datetime('now', '-1 day') ORDER BY changed_at DESC"
Active work:
tooling/db/ticket list --status in_progress
3. Identify Blockers
Flag potential issues:
- Tickets marked
in_progresswith no recent commits on their branch - Stalled PRs: open for more than 48 hours with no review activity
- Tickets with unresolved dependencies (blockedBy relationships)
4. Generate Summary
Format the output as:
## Standup — {date}
### {Team}
**Active:** #N title (agent), #N title (agent)
**Completed:** #N title
**Blocked:** #N title — waiting on #M
**Next up:** #N title (ready, unblocked)
Repeat the team section for each team that had activity.
5. Flag Risks
Highlight at the end of the report:
- High-priority tickets with no activity in the last 24 hours
- Dependency chains where upstream work is stalled
- Tickets approaching sprint end without completion