Agent product manager

Skill queen-of-code/AI-DLC/skills/agents/agent-product-manager

Writes feature spec drafts using the product template. Takes a research brief and seed blurb as input. Outputs a structured spec to the scratchpad and writes unanswerable questions to pm_questions for the orchestrator to surface.From its SKILL.md

Install

npx -y skills add queen-of-code/AI-DLC --skill agent-product-manager

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, as published. Nobody here has run it

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.

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.