name: team-team-sync
description: "[Team] Generate meeting agendas and facilitate team coordination. Use when preparing standups, sprint reviews, or team meetings. Triggers on keywords like "standup", "team sync", "meeting agenda", "daily", "sprint review"."
argument-hint: "daily | weekly | sprint-review | sprint-planning"
infer: true
allowed-tools: Read, Write, Grep, Glob, TodoWrite
Team Sync
Generate meeting agendas and action item tracking.
Summary
Goal: Generate structured meeting agendas and track action items for team coordination meetings.
| Step |
Action |
Key Notes |
| 1 |
Identify meeting type |
Daily standup, weekly sync, sprint review, or sprint planning |
| 2 |
Review previous items |
Search plans/reports/ for prior agendas and open action items |
| 3 |
Gather current data |
Recent git activity, artifacts, PBIs, blockers |
| 4 |
Generate agenda |
Use type-specific template with current data |
| 5 |
Save output |
plans/reports/{YYMMDD}-{meeting-type}.md |
Key Principles:
- Carry forward incomplete action items from previous meetings
- Use meeting-type-specific templates (standup, weekly, sprint review, planning)
- Include sprint metrics (velocity, commitment %) for review meetings
When to Use
- Daily standup preparation
- Weekly team sync
- Sprint review/planning
- Retrospective facilitation
Pre-Workflow
Activate Skills
- Activate
project-manager skill for meeting facilitation best practices
Meeting Types
Daily Standup
- What I did yesterday
- What I'll do today
- Any blockers
Weekly Sync
- Progress highlights
- Cross-team dependencies
- Upcoming milestones
Sprint Review
- Demo completed items
- Stakeholder feedback
- Velocity review
Sprint Planning
- Capacity check
- Backlog prioritization
- Sprint goal setting
Workflow
- Identify meeting type
- Review previous meeting action items (search
plans/reports/ for prior agendas)
- Gather relevant data (recent git activity, artifacts, PBIs, blockers)
- Check open blockers and pending handoffs
- Track completion status of previous action items; carry incomplete items forward
- Generate agenda template based on meeting type
- Populate with current data
- Save output to
plans/reports/{YYMMDD}-{meeting-type}.md
Detailed Templates
Daily Standup Template
## Daily Standup - {Date}
### Sprint Progress
- Day {N} of {Total}
- Points: {completed}/{planned}
### Yesterday
- {completed items}
### Today
- {planned items}
### Blockers
- {blockers}
Weekly Sync Template
## Weekly Team Sync - {Date}
### Sprint Progress (10 min)
### Cross-Role Updates (15 min)
| Role | Update |
| ------ | ------ |
| PO | |
| BA | |
| Dev | |
| QA | |
| Design | |
### Risks & Blockers (10 min)
### Action Items (5 min)
Sprint Review Template
## Sprint {N} Review - {Date}
### Demo Items
| Feature | Demo By |
| ------- | ------- |
| | |
### Sprint Goal: {goal}
- Status: {achieved/partial/not}
### Metrics
- Velocity: {points}
- Commitment: {%}
### Feedback
Generic Agenda Template
## {Meeting Type} - {Date}
### Attendees
- {names}
### Agenda
1. {item}
### Discussion Points
- {point}
### Action Items
- [ ] {action} - {owner}
### Next Meeting
{date/time}
Example
/team-team-sync daily
/team-team-sync sprint-review
/team-team-sync sprint-planning
Related
- Role Skill:
project-manager
- Command:
/team-team-sync
IMPORTANT Task Planning Notes
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed
1---2name: team-team-sync3description: Generate meeting agendas and action item tracking.4---5
6---
7name: team-team-sync
8description: "[Team] Generate meeting agendas and facilitate team coordination. Use when preparing standups, sprint reviews, or team meetings. Triggers on keywords like "standup", "team sync", "meeting agenda", "daily", "sprint review"."
9argument-hint: "daily | weekly | sprint-review | sprint-planning"
10infer: true
11allowed-tools: Read, Write, Grep, Glob, TodoWrite
12---
13
14# Team Sync
15
16Generate meeting agendas and action item tracking.
17
18## Summary
19
20**Goal:** Generate structured meeting agendas and track action items for team coordination meetings.
21
22| Step | Action | Key Notes |
23|------|--------|-----------|
24| 1 | Identify meeting type | Daily standup, weekly sync, sprint review, or sprint planning |
25| 2 | Review previous items | Search `plans/reports/` for prior agendas and open action items |
26| 3 | Gather current data | Recent git activity, artifacts, PBIs, blockers |
27| 4 | Generate agenda | Use type-specific template with current data |
28| 5 | Save output | `plans/reports/{YYMMDD}-{meeting-type}.md` |
29
30**Key Principles:**
31- Carry forward incomplete action items from previous meetings
32- Use meeting-type-specific templates (standup, weekly, sprint review, planning)
33- Include sprint metrics (velocity, commitment %) for review meetings
34
35## When to Use
36- Daily standup preparation
37- Weekly team sync
38- Sprint review/planning
39- Retrospective facilitation
40
41## Pre-Workflow
42
43### Activate Skills
44
45- Activate `project-manager` skill for meeting facilitation best practices
46
47## Meeting Types
48
49### Daily Standup
50- What I did yesterday
51- What I'll do today
52- Any blockers
53
54### Weekly Sync
55- Progress highlights
56- Cross-team dependencies
57- Upcoming milestones
58
59### Sprint Review
60- Demo completed items
61- Stakeholder feedback
62- Velocity review
63
64### Sprint Planning
65- Capacity check
66- Backlog prioritization
67- Sprint goal setting
68
69## Workflow
701. Identify meeting type
712. Review previous meeting action items (search `plans/reports/` for prior agendas)
723. Gather relevant data (recent git activity, artifacts, PBIs, blockers)
734. Check open blockers and pending handoffs
745. Track completion status of previous action items; carry incomplete items forward
756. Generate agenda template based on meeting type
767. Populate with current data
778. Save output to `plans/reports/{YYMMDD}-{meeting-type}.md`
78
79## Detailed Templates
80
81### Daily Standup Template
82```markdown
83## Daily Standup - {Date}
84
85### Sprint Progress
86- Day {N} of {Total}
87- Points: {completed}/{planned}
88
89### Yesterday
90- {completed items}
91
92### Today
93- {planned items}
94
95### Blockers
96- {blockers}
97```
98
99### Weekly Sync Template
100```markdown
101## Weekly Team Sync - {Date}
102
103### Sprint Progress (10 min)
104
105### Cross-Role Updates (15 min)
106| Role | Update |
107| ------ | ------ |
108| PO | |
109| BA | |
110| Dev | |
111| QA | |
112| Design | |
113
114### Risks & Blockers (10 min)
115
116### Action Items (5 min)
117```
118
119### Sprint Review Template
120```markdown
121## Sprint {N} Review - {Date}
122
123### Demo Items
124| Feature | Demo By |
125| ------- | ------- |
126| | |
127
128### Sprint Goal: {goal}
129- Status: {achieved/partial/not}
130
131### Metrics
132- Velocity: {points}
133- Commitment: {%}
134
135### Feedback
136```
137
138### Generic Agenda Template
139```markdown
140## {Meeting Type} - {Date}
141
142### Attendees
143- {names}
144
145### Agenda
1461. {item}
147
148### Discussion Points
149- {point}
150
151### Action Items
152- [ ] {action} - {owner}
153
154### Next Meeting
155{date/time}
156```
157
158## Example
159
160```bash
161/team-team-sync daily
162/team-team-sync sprint-review
163/team-team-sync sprint-planning
164```
165
166## Related
167- **Role Skill:** `project-manager`
168- **Command:** `/team-team-sync`
169
170## IMPORTANT Task Planning Notes
171
172- Always plan and break many small todo tasks
173- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed