codingthefuturewithai/teamcraft-glgd:stakeholder-update

Goal

Produce a stakeholder update that gives the audience exactly what they need — no more. Different audiences need fundamentally different information: a client cares about delivered value and risk to their timeline; an executive cares about status and decisions needed; an engineering team needs specifics about what shipped, what's blocked, and what changed. The source of truth is always the live project data — not memory, not estimates.

Hard Constraints

• Pull live data from GitLab before composing any update. Never estimate or describe sprint status from memory.
• The update is generated FROM the project artifacts, never instead of them. If the PRD or tech decisions are stale, flag it — do not paper over it in the update.
• If a Drive file operation fails with a path error, read the error message to identify a valid accessible host path and retry with it.

Resolve Drive Account

Call mcp__google-drive__list_accounts before any other Drive operation:

• No accounts — skip Drive operations and proceed from GitLab data only.
• One account — Use it. Pass account_email explicitly on every Drive tool call this session.
• Multiple accounts — Present the list, ask which account to use.

Identify the Project and Sprint

Use mcp__gitlab__list_projects to surface available projects and ask the user which one this update covers. Use mcp__gitlab__list_milestones to identify the active or most recently completed sprint.

Pull Live Data

From GitLab, gather the current state of the sprint:

• Issues: open, in progress, completed, blocked — with titles and labels
• MRs: open, merged, draft — pipeline status
• Any issues flagged as at-risk (blocked label, overdue, no recent activity)
• Sprint goal from milestone description

Ask if the user can point at the PRD and any other relevant Drive documents for context. Load them if available.

Determine Audience and Compose

Use $ARGUMENTS and context to determine the audience type. Ask if not clear. The audience shapes every word:

Client / external stakeholder — delivered value in business terms, risks to scope or timeline with mitigations, decisions the client needs to make. No internal jargon. No ticket numbers. Green / Yellow / Red overall status with plain-language rationale.

Executive / leadership — overall health (G/Y/R), progress toward sprint goal, risks that need a decision or escalation, asks. Under 300 words. No ticket-level detail.

Engineering team — what shipped, what's blocked and why, what changed in scope or priority, what's up next. Ticket-level specifics welcome. Technical language appropriate.

Cross-functional partners — what affects them: scope changes, new dependencies on their team, timeline shifts, decisions they need to weigh in on.

See references/example-stakeholder-update.md for structure and tone calibration by audience type.

Review and Store

Show the complete update for review. Offer to adjust tone, length, or level of detail.

Ask whether to store this in Google Drive. If yes, ask where — which folder. Never save to root. Record the URL.

Done

Share the update text and Drive URL if stored. The update is derived from the live project state — rerun this skill any time the audience or period changes.