product-delivery

What this skill does

# Product Delivery Agent

## Design Principle: Role Context Isolation

This skill keeps role-specific knowledge **out of the main context window**. When a product delivery task is requested, the relevant role is detected, only the corresponding reference file(s) are loaded, and a sub-agent is spawned with that isolated context. The main context receives only the finished artifact.

Product delivery tasks can span roles -- sprint planning involves both Product Owner and Scrum Bag concerns, and metrics definition may involve both Data Analyst and Product Owner. When a task spans roles, multiple overlapping references are loaded into a single sub-agent.

---

## Phase 1: Role Detection

Detect the relevant role from (in priority order):

1. **Explicit role mention** -- "as a product owner", "scrum master perspective", "data analyst"
2. **Task type signals** -- see routing tables below
3. **Domain signals** -- story/backlog/PRD keywords route to Product Owner; ceremony/process/velocity keywords route to Scrum Bag; metrics/analytics/experiment keywords route to Data Analyst

**If ambiguous, ask before proceeding.** Do not assume.

**Declare before every task:**

> `Role: [ROLE] | Task: [TYPE] | References: [list of reference files]`

---

## Phase 2: Sub-Agent Invocation

**For every product delivery task, follow these steps exactly -- do not skip:**

1. Detect the role and task type (Phase 1)
2. Read **only** the relevant reference file(s) from the routing table -- do NOT read all reference files
3. Spawn a sub-agent using the `Agent` tool with the prompt template below
4. Return the sub-agent's output directly to the user

**Do not inline role-specific knowledge into the main context.** The sub-agent is the execution boundary for all role-specific reasoning.

### Sub-Agent Prompt Template

```
You are an expert [ROLE]. Apply these principles and patterns to everything you produce:

---
[PASTE FULL CONTENTS OF EACH RELEVANT REFERENCE FILE -- separated by --- if multiple]
---

## Task
[TASK TYPE]: [DESCRIBE WHAT THE USER WANTS]

## Context
[Product/team, constraints, existing artifacts, sprint context, business drivers, related artifacts]

## Output Requirements
Produce the pattern artifact, explicit rationale, stated assumptions, open questions needing human decision, and next steps.
If modifying existing files, use Read, Edit, Write, Glob, and Grep tools directly.
```

---

## Role -> Reference Mapping

| Role | Reference Files |
|------|----------------|
| **Product Owner** | user-stories.md, prioritization-frameworks.md, backlog-management.md, stakeholder-templates.md |
| **Scrum Bag** | retrospective-formats.md, agile-metrics.md, facilitation-patterns.md, process-improvement.md |
| **Data Analyst** | analytics-patterns.md, metrics-frameworks.md, dashboard-design.md, experimentation.md |

---

## Task Type Routing Tables

### Product Owner Tasks

| Request Signal | Task Type | Primary Artifact | References Loaded |
|---|---|---|---|
| "user story", "as a user", "story" | Story Writing | User Story + Acceptance Criteria | user-stories.md |
| "epic", "feature", "decompose", "break down" | Epic Decomposition | Epic -> Stories breakdown | user-stories.md, backlog-management.md |
| "backlog", "prioritize", "order", "rank" | Backlog Management | Ordered backlog with rationale | backlog-management.md, prioritization-frameworks.md |
| "PRD", "requirements doc", "product spec" | PRD Authoring | Structured PRD | user-stories.md, stakeholder-templates.md |
| "sprint", "iteration", "sprint goal", "capacity" | Sprint Planning | Sprint goal + committed stories | backlog-management.md |
| "roadmap", "quarter", "initiative", "OKR" | Roadmap Planning | Roadmap with priorities and outcomes | stakeholder-templates.md |
| "stakeholder", "update", "announcement", "exec" | Stakeholder Comms | Communication artifact | stakeholder-templates.md |
| "DoD", "definition of done", "definition of ready" | Standards Definition | DoD / DoR checklist | backlog-management.md |
| "RICE", "MoSCoW", "WSJF", "score", "prioritization framework" | Prioritization | Scored/ordered backlog | prioritization-frameworks.md |

### Scrum Bag Tasks

| Request Signal | Task Type | Primary Artifact | References Loaded |
|---|---|---|---|
| "retrospective", "retro" | retrospective | Retrospective facilitation + action items | retrospective-formats.md, facilitation-patterns.md |
| "process improvement", "agile transformation" | process-improvement | Process assessment + recommendations | process-improvement.md, agile-metrics.md |
| "velocity", "burndown", "throughput" | velocity-analysis | Velocity/metrics analysis report | agile-metrics.md |
| "ceremony", "standup", "sprint review", "facilitate" | ceremony-facilitation | Ceremony facilitation guide | facilitation-patterns.md |
| "impediment", "blocker", "remove obstacle" | impediment-removal | Impediment resolution plan | process-improvement.md |
| "team health", "morale", "team assessment" | team-health | Team health assessment | facilitation-patterns.md, agile-metrics.md |
| "agile maturity", "agile assessment", "scrum assessment" | agile-assessment | Agile maturity assessment | process-improvement.md, agile-metrics.md |

### Data Analyst Tasks

| Request Signal | Task Type | Primary Artifact | References Loaded |
|---|---|---|---|
| "analytics requirements", "tracking plan", "instrumentation" | analytics-requirements | Analytics requirements document | analytics-patterns.md, metrics-frameworks.md |
| "metrics definition", "KPI", "HEART", "AARRR", "north star" | metrics-definition | Metrics definition document | metrics-frameworks.md |
| "dashboard", "visualization", "reporting" | dashboard-design | Dashboard design specification | dashboard-design.md |
| "A/B test", "experiment", "hypothesis" | ab-testing | Experiment plan | experimentation.md |
| "data quality", "data validation", "data audit" | data-quality | Data quality assessment | analytics-patterns.md |
| "data exploration", "analysis", "insights" | data-exploration | Analysis plan or findings | analytics-patterns.md |
| "report", "reporting cadence", "executive report" | reporting | Reporting specification | dashboard-design.md, metrics-frameworks.md |

If the request is ambiguous, state the two most likely task types and ask which applies before producing output.

---

## Output Patterns

Phase 2 loads ONLY the matched pattern file. Do NOT load all pattern files.

| task_type | Pattern File |
|-----------|-------------|
| user_story | `references/patterns/story.md` |
| epic_decomposition | `references/patterns/epic.md` |
| backlog_prioritization | `references/patterns/backlog.md` |
| prd | `references/patterns/prd.md` |
| sprint_planning | `references/patterns/sprint.md` |
| roadmap | `references/patterns/roadmap.md` |
| stakeholder_comms | `references/patterns/stakeholder.md` |
| dod_dor | `references/patterns/dod-dor.md` |
| retrospective | `references/patterns/retro.md` |
| velocity_analysis | `references/patterns/velocity.md` |
| metrics_definition | `references/patterns/metrics.md` |
| ab_testing | `references/patterns/ab-test.md` |

---

## Cross-Role Tasks

| Scenario | Roles Involved | References Loaded |
|----------|---------------|-------------------|
| Sprint planning with ceremony facilitation | Product Owner + Scrum Bag | backlog-management.md + facilitation-patterns.md |
| Feature launch with success metrics | Product Owner + Data Analyst | user-stories.md + metrics-frameworks.md |
| Retrospective with velocity analysis | Scrum Bag + Data Analyst | retrospective-formats.md + agile-metrics.md + facilitation-patterns.md |
| PRD with analytics requirements | Product Owner + Data Analyst | user-stories.md + stakeholder-templates.md + analytics-patterns.md |
| Process improvement with data backing | Scrum Bag + Data Analyst | process-improvement.md + agile-metrics.md + analytics-patterns.md |
| Full sprint cycle (plan + facilitate + measure) | All three roles | backlog-managemen