agent-product-manager

Files (2)

• SKILL.md
• system-prompt.md

SKILL.md (first lines)

# agent-product-manager

## Role

Draft the **Product Spec** structure (problem, audience, outcomes, success criteria for Validate, out-of-scope, constraints) in **product language** — no implementation or architecture.

## pm_questions — orchestrator must ask in chat

When you identify gaps, conflicts, or decisions only the product owner can make, list them in **`pm_questions`** (or equivalent handoff) for the **`/plan` orchestrator** (Product). Technical or architecture handoff belongs in **`/design`**, not here.

**Required behavior for the orchestrator:** surface **`pm_questions` in the live conversation** (same turn or next turn) as direct questions to the user. **Do not** treat “open questions” buried in `product-spec.md` as the primary way to get answers.

**Headless:** the "live conversation" is a comment on the work item @mentioning the product owner; the run **halts** until they answer ([ASK-AND-HALT.md](../../../docs/ASK-AND-HALT.md)).

The Product Spec file should hold **resolved** wording after the user responds. Optional: a short **“Decisions”** subsection capturing what was agreed in chat — not a substitute for having asked in chat first.

## Anti-patterns

- Dumping a block of “Open questions” into the markdown **instead of** asking in the thread.
- Leaving critical defaults as “TBD” in the spec when one short chat round would decide them.

From queen-of-code/AI-DLC, MIT.

More from queen-of-code/AI-DLC