team-communication-feedback
Scannednpx machina-cli add skill dzhibas/engineering-manager-plugin/team-communication-feedback --openclawTeam Communication and Feedback
Async Team Updates
Draft structured weekly or bi-weekly updates following this format:
What shipped: Completed deliverables with owners and brief impact notes.
In progress: Current sprint items with status and ETA. Flag anything at risk.
Blockers: Issues requiring cross-team help. Be specific about what's needed and from whom.
Upcoming: Next sprint priorities and any staffing or dependency changes.
Wins & recognition: Call out individual and team achievements. Be specific about the contribution.
Pull data from project tracker and chat to auto-populate where possible.
SBI Feedback Framework
Structure all written feedback using Situation-Behavior-Impact:
Situation: When and where the behavior occurred. Be specific and recent.
Behavior: What the person did. Observable and factual — not interpretive. Describe actions, not character.
Impact: The effect on the team, project, or stakeholder. Make it concrete and measurable where possible.
Example: "During yesterday's sprint review (situation), you presented the API redesign with clear before/after metrics and addressed every stakeholder question directly (behavior). This built strong confidence in the approach and we got immediate sign-off, saving a week of follow-up meetings (impact)."
Skip-Level Meeting Preparation
When preparing for skip-level meetings:
- Review recent team health signals from chat and project tracker
- Identify themes from recent 1:1s with the person's direct manager
- Prepare open-ended questions about psychological safety, growth, and blockers
- Frame the conversation around learning and listening, not investigating
- Suggested questions:
- "What's working well on the team that you'd want to keep?"
- "If you could change one thing about how the team works, what would it be?"
- "Do you feel like you have what you need to do your best work?"
- "Is there anything you think I should know that I might not?"
Retrospective Facilitation
Generate structured retro formats based on team preference:
Start/Stop/Continue: Three-column exercise. Good for teams new to retros.
4Ls (Liked/Learned/Lacked/Longed for): Deeper reflection format. Good for project wrap-ups.
Timeline retro: Walk through the sprint chronologically, noting highs and lows. Good for incident review.
For all formats:
- Timebox each section (suggest 5-10 min per section)
- Generate follow-up action items with assigned owners
- Track action items from previous retros to ensure follow-through
Source
git clone https://github.com/dzhibas/engineering-manager-plugin/blob/main/skills/team-communication-feedback/SKILL.mdView on GitHub Overview
This skill provides templates and guidance for async team updates, SBI-style feedback, and skip-level prep. It also covers retrospective facilitation and team announcements to keep stakeholders informed and aligned.
How This Skill Works
It uses built-in templates to auto-populate fields from the project tracker and chat. It enforces SBI (Situation-Behavior-Impact) for feedback and supplies step-by-step prompts for skip-level meetings and retros.
When to Use It
- Draft a weekly/bi-weekly async team update
- Write SBI-formatted feedback
- Prepare for a skip-level meeting
- Facilitate a retrospective
- Draft a team announcement or async update for stakeholders
Quick Start
- Step 1: Gather inputs from the project tracker and relevant chat threads.
- Step 2: Select the target format (async update, SBI feedback, skip-level prep, or retro), then outline sections.
- Step 3: Generate content, assign owners for action items, and share with the team.
Best Practices
- Pull data from the project tracker and chat to auto-populate where possible.
- Use the SBI framework: Situation, Behavior, Impact—be specific, observable, and concrete.
- For skip-level prep, review health signals and manager themes; prepare open-ended questions about psychological safety, growth, and blockers.
- For retrospectives, choose a format (Start/Stop/Continue, 4Ls, or Timeline), timebox sections to 5-10 minutes, and generate follow-up action items with owners.
- Track action items from previous retros to ensure follow-through and celebrate wins.
Example Use Cases
- Draft an async update: What shipped, In progress, Blockers, Upcoming, Wins.
- Provide SBI feedback with a concrete example, e.g., 'During yesterday's sprint review...' (Situation/Behavior/Impact).
- Prepare for a skip-level meeting by reviewing health signals and 1:1 themes, then draft open-ended questions.
- Facilitate a retrospective using Start/Stop/Continue with timeboxed sections and action items.
- Draft a team announcement to communicate milestones or changes to stakeholders.
