proagent-delivery

Overview of all delivery management capabilities: sprint planning, status reports, risk assessment, milestone tracking, retrospectives, ROM estimation, and delivery health reviews.

Review delivery health: sprint-health, delivery-risks, timeline, stakeholder-alignment, estimate-review, meeting-insights, comms-quality, or sow-review assessment.

Execute delivery workflows: plan-sprint, status-report, risk-assess, milestone-track, retrospective, rom-estimate, generate-sow, or others.

Use this agent for project delivery management across all delivery phases. Handles sprint planning, milestone tracking, status reporting, risk assessment, stakeholder communication, retrospective facilitation, resource allocation, agile/scrum ceremony management, standup notes generation, PRD creation, todo management, meeting insights analysis, internal communications, agentic KPIs tracking, task planning, and Eisenhower matrix prioritization. Examples: <example>Context: A project manager needs to prepare a weekly status update for stakeholders. user: "I need to write the weekly status report for the Customer Portal project" assistant: "Let me use the delivery-specialist agent to gather project data and generate a structured status report." <commentary>Status reporting is a core delivery function, dispatch delivery-specialist to produce a tailored report.</commentary></example> <example>Context: A team lead needs to assess risks before a major milestone. user: "We have a release milestone next week, what risks should we be worried about?" assistant: "I'll have the delivery-specialist agent run a risk assessment focused on the upcoming milestone." <commentary>Pre-milestone risk assessment is a cross-cutting delivery concern, so the delivery-specialist handles the structured analysis.</commentary></example> <example>Context: A developer wants AI-generated standup notes from recent git activity. user: "Generate my standup notes from yesterday's commits" assistant: "I'll have the delivery-specialist agent analyze git history, correlate with Jira tickets, and produce a structured standup note." <commentary>Standup notes generation from git/Jira/calendar data is a delivery automation function.</commentary></example> <example>Context: A PM wants to track agentic delivery KPIs. user: "Show me our agentic KPIs for this sprint" assistant: "I'll have the delivery-specialist agent calculate autonomy rate, first-pass success, cycle time, and other agentic KPIs." <commentary>Agentic KPI tracking measures AI-human collaboration effectiveness in delivery.</commentary></example>

Use this agent to extract client context from Slack channels and Google Drive documents for SOW generation. It reads Slack channel history, extracts Google Drive URLs from messages, reads linked documents and meeting transcripts, and produces a structured Client Context Brief. Use when: the SOW generator workflow needs to gather client context before generating a Statement of Work. This agent is dispatched by the generate-sow command to keep the extraction phase isolated from the main conversation context. Do NOT use for: generating the SOW itself, conducting the clarification interview, or any non-SOW task. Examples: <example> Context: The SO wants to generate a SOW and has provided a Slack channel and Drive folder. user: "Extract client context from #proj-acme-delivery and the linked Drive folder" assistant: "I'll dispatch the sow-context-extractor agent to read the Slack channel and Drive documents." <commentary>SOW context extraction is an isolated data-gathering phase, dispatch sow-context-extractor.</commentary> </example> <example> Context: The generate-sow command needs pre-processing of client information sources. user: "Read all the context from Slack channel proj-acme and Drive folder https://drive.google.com/..." assistant: "I'll have the sow-context-extractor gather and synthesize all client context." <commentary>Multi-source extraction benefits from a dedicated subagent to keep the main context clean.</commentary> </example>

Use when managing project delivery -- sprint planning, milestones, stakeholder updates, status reports, risk management, timelines, resource allocation, agile/scrum ceremonies, retrospectives, standup notes generation, PRD creation, todo management, meeting insights analysis, internal communications, agentic KPIs tracking, task planning, and Eisenhower matrix prioritization

Analyze project documents, task lists, or scope descriptions and generate ROM (Rough Order of Magnitude) effort estimates in CSV format. Supports reading project files from Google Drive via MCP. Use when: the user needs project scoping, effort estimation, budgeting, resource planning, team composition analysis, or ROM generation from roadmaps, requirements, or task lists. Do NOT use for: sprint planning (use delivery-assistant), status reports, risk assessments, or retrospectives.

4 hooks across 2 events

Atlassian MCP server for Jira sprint management, backlog grooming, issue tracking, velocity metrics, burndown charts, and Confluence documentation publishing (meeting notes, charters, risk registers, dashboards).