product-delivery

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.