Files

T

jpmschweitzerandClaude Opus 4.6 7158ae9cf5 feat(meta): add whatsinagame multi-agent team starter kit

Claude-native starter kit that bootstraps multi-agent team
infrastructure for any project. Clone once, install as a global
skill, run /kit-install in any project directory.

Includes:
- 3-tier profile system (minimal/standard/full: 3-12 agents)
- 16 agent archetype templates with personality spectrum
- 18 skill templates using domain-action naming convention
- Stakeholder persona panel for workshops and PR reviews
- SQLite ticketing DB with CLI tools (config-based DB paths)
- Decision tracking, sprint lifecycle, workshop orchestration
- Multi-git-host support (GitHub, Gitea, GitLab)
- /kit-update skill for syncing with source repo evolution
- Naming theme support for agent identity/flavor
- Smoke tests for all three profile tiers

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-18 02:22:30 +01:00

1.7 KiB

Raw Blame History

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:

db/connectors/sqlite-query "SELECT * FROM ticket_history WHERE changed_at > datetime('now', '-1 day') ORDER BY changed_at DESC"

Active work:

db/connectors/ticket list --status in_progress

3. Identify Blockers

Flag potential issues:

Tickets marked in_progress with 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

1.7 KiB Raw Blame History