Improve recurring team meetings with AI
Give engineering-team meetings a clear purpose, decision owner and useful output while protecting focus time.
Improve recurring team meetings with AI by tracing the decisions that arrive late, surprise colleagues or keep returning without resolution. The design-team-cadence skill turns those examples into a proposed operating rhythm for an engineering team, platform group or group of teams. It starts from the work that needs coordination rather than copying someone else's calendar.
Each selected forum gets a purpose, owner, required inputs, participants, decision authority, output and cancellation rule. Written updates carry information that does not require discussion, leaving shared time for judgement, disagreement and coaching. The proposal also names meetings to stop or replace and defines a four-week pilot. You review and implement the plan; it does not send invitations or operate your calendar.
What it does
- Remove duplicated discussions and information-only meetings
- Define who proposes, decides and must be consulted
- Give each forum an output and follow-up owner
- Protect one-to-ones from becoming project-status reports
- Set an escalation trigger, destination and response expectation
- Compare attendance cost with decisions and completed actions
Install and use
- Use a file-capable agent and provide only authorised team context.
- Describe recent failures alongside the current meeting arrangements.
- Ask for the smallest useful cadence and a written contract for each selected forum.
- Review ownership with colleagues, then assess the proposed four-week pilot before making lasting changes.
FAQ
Source
Made by Serhii Zolotov (greenblacked). Original skill: design-team-cadence, published on GitHub under the MIT licence.
View on GitHub