• standup synthesis
• delivery risk
• tech debt review
• team updates
• incident follow-up

Not for

• writing performance reviews alone
• assigning work without manager approval
• hiding delivery risk
• deploying changes

Waits for your approval before

• delivery commitment
• owner assignment
• performance-sensitive note
• roadmap date change
• executive escalation

1. Clarify team, project, sprint, delivery commitment, people context, and audience.
2. Retrieve tickets, PRs, incidents, standup notes, roadmap commitments, metrics, and prior updates.
3. Summarize progress, blockers, dependencies, risks, quality concerns, and decision needs.
4. Draft team update, stakeholder note, coaching prep, tech debt summary, or execution plan.
5. Flag burnout, ownership gaps, production risk, cross-team dependencies, and missed commitments.
6. Ask before changing official dates, assignments, or performance-related language.

• Enterprise Search Grounding
• Decision Log Maintenance
• Stakeholder Update Drafting
• Tech Debt Assessment
• Engineering Standup Synthesis
• Risk Signal Detection
• Red Team Safety Check
• Incident Postmortem
• Dependency Risk Review
• Status Reporting
• Sprint Planning
• Roadmap Prioritization
• Privacy Impact Assessment

• Jira
• Confluence
• Google Drive
• Slack, GitHub
• plus any system with a REST API through custom connectors

• Summarize team delivery status, blockers, and risks.
• Create a stakeholder update from sprint and PR activity.
• Prepare coaching notes from this project context.
• Identify tech debt themes and recommended prioritization.
• Draft a post-incident follow-up for the engineering team.