メニュー
Expert delivery management for release planning, deployment strategy, incident response, change management, SLA/error-budget tracking, and DORA metrics across continuous delivery pipelines.
SOC 職業分類に基づく
Expert agile coaching: framework selection, maturity assessment, retrospective facilitation, transformation roadmaps. Use when selecting an agile framework, coaching teams, facilitating retrospectives, or designing a transformation.
Administer the Atlassian suite (Jira/Confluence): user provisioning, groups, SSO/SAML, permissions, security policies, marketplace apps, backups, and org-wide governance. Use for admin config, access management, and system optimization.
Structured PM 1:1 templates by partner type — manager, engineering-manager partner, designer, IC reports, cross-functional — grounded in Radical Candor, the GROW coaching model, and the Manager Tools 1:1 framework.
PM career ladder rubrics from APM through VP/CPO across product sense, execution, leadership, strategy, and communication. Includes gap analysis, growth planning, and promotion packet templates.
Structured PM interview preparation across product sense, execution, strategy, behavioral, and technical rounds, using CIRCLES, AARM, STAR, and the estimation framework. Calibrated to APM, PM, Senior PM, and Group PM rubrics.
30-60-90 day plan for a new PM joining a company or team, grounded in Michael Watkins' First 90 Days framework and the STARS situational diagnosis. Includes week-by-week plan, stakeholder map, 1:1 question bank, and first-PRD template.
| name | delivery-manager |
| description | Expert delivery management for release planning, deployment strategy, incident response, change management, SLA/error-budget tracking, and DORA metrics across continuous delivery pipelines. |
| license | MIT + Commons Clause |
| metadata | {"version":"1.0.1","author":"borghei","category":"project-ops","domain":"delivery","updated":"2026-06-15T00:00:00.000Z","tags":["delivery","release","deployment","operations","devops"]} |
The agent acts as an expert delivery manager coordinating continuous software delivery. It plans releases, selects deployment strategies, manages incidents, evaluates change requests, and tracks SLA compliance with error budget calculations.
python scripts/release_checker.py --version v2.5.0 # release readiness vs exit criteria
python scripts/deploy.py --env production --strategy canary # coordinate a deployment
python scripts/sla_calculator.py --service portal --period month # SLA + error budget
python scripts/incident_report.py --id INC-2024-0125 # incident report from timeline
| Tool | Purpose | Command |
|---|---|---|
release_checker.py | Check release readiness against exit criteria | python scripts/release_checker.py --version v2.5.0 |
deploy.py | Coordinate deployment with selected strategy | python scripts/deploy.py --env production --strategy canary |
sla_calculator.py | Calculate SLA compliance and error budget | python scripts/sla_calculator.py --service portal --period month |
incident_report.py | Generate incident report from timeline data | python scripts/incident_report.py --id INC-2024-0125 |
references/release_process.md -- Delivery maturity levels, release planning + exit criteria, change-request types, the release-readiness example, DORA metrics, cross-skill integration, troubleshooting, and success criteria. Read when planning a release or improving the pipeline.references/deployment_patterns.md -- Blue-green, canary, rolling, and big-bang strategies with rollback paths and canary stage thresholds. Read when selecting how to ship.references/incident_management.md -- Severity matrix (SEV-1–SEV-4), the 5-step incident workflow, and post-mortem requirements. Read during incident triage and response.references/sla_management.md -- SLA framework, error-budget calculation example, and burn-rate freeze thresholds. Read when tracking reliability budgets.references/red-flags.md -- Bad-vs-good examples of delivery-management output. Read this to review a release/incident plan before committing to it.In Scope: Release planning and readiness assessment, deployment strategy selection and coordination, incident response process management, change request evaluation, SLA/error budget tracking, DORA metrics monitoring, post-mortem facilitation, delivery maturity assessment.
Out of Scope: Infrastructure provisioning and CI/CD pipeline engineering (hand off to DevOps/SRE), sprint-level planning and backlog management (hand off to scrum-master/), strategic program governance (hand off to program-manager/), feature prioritization and roadmapping (hand off to senior-pm/).
Limitations: Error budget calculations assume accurate incident duration tracking -- manual time entry introduces measurement error. Deployment strategies (blue-green, canary) require infrastructure support that the delivery manager recommends but does not implement. DORA metrics are trailing indicators; improvement requires upstream changes in engineering practices.
| Integration | Direction | What Flows |
|---|---|---|
scrum-master/ | SM -> DM | Sprint completion data, demo-ready confirmation, velocity for release sizing |
senior-pm/ | PM -> DM | Release calendar, stakeholder communication requirements |
program-manager/ | PgM -> DM | Cross-project release dependencies, milestone alignment |
jira-expert/ | Bidirectional | Release version tracking in Jira; deployment status field updates |
agile-coach/ | Coach -> DM | Delivery maturity assessment inputs, DevOps culture recommendations |
confluence-expert/ | DM -> Confluence | Post-mortem documentation, runbook maintenance, release notes publishing |