agent-product-manager

Draft structured product spec markdown from a seed blurb and research brief.

8|13|Updated Apr 13, 2026

Search Tags:#product-management #success-criteria #product-spec #pm-agent #spec-drafting #research-brief

Ready to run

npx skills add https://github.com/queen-of-code/AI-DLC --skill agent-product-manager-queen-of-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-product-manager
Source: https://github.com/queen-of-code/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/agents/agent-product-manager
Command: npx skills add https://github.com/queen-of-code/AI-DLC --skill agent-product-manager-queen-of-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of converting a brief idea and research into a clear, actionable Product Spec by drafting a complete spec in PM language and surfacing unresolved decisions for the orchestrator to ask.

Core Features & Use Cases

Structured Spec Drafting: Fills the product template with problem statement, target audience, outcomes, measurable success criteria, scope, and constraints.
Decision Handoff: Writes open or unanswerable items as pm_questions so the /plan orchestrator can surface them in chat for the product owner.
Use Case: Provide a seed blurb and a research brief and receive a ready-to-review product spec markdown and a prioritized list of PM questions to resolve outstanding decisions.

Quick Start

Draft a product spec from the seed blurb and research brief, write the completed markdown spec to spec_draft, and list any unresolved PM questions in pm_questions for the orchestrator to ask.

Frequently Asked Questions about agent-product-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert a research brief into a structured product spec?▼

Product spec drafting from a research brief involves synthesizing research data to define problem statements, target audiences, and measurable success criteria. This process populates a structured template with scope and constraints, transforming raw briefs into PM-ready markdown specifications.

What's the best way to define success criteria and scope during product planning?▼

Defining success criteria and scope during product planning requires synthesizing research briefs into a structured spec. This establishes measurable outcomes, explicit constraints, and technical considerations, ensuring the product spec captures the problem statement and target audience accurately.

How do I identify and list unresolved decisions when drafting a product spec?▼

To identify unresolved decisions while drafting a product spec, the agent extracts open or unanswerable items and writes them as a JSON array. This list of PM questions is generated alongside the markdown spec for the orchestrator to surface.

Can I generate a product spec markdown document from a short seed blurb?▼

Yes, you can generate a product spec markdown document from a short seed blurb. By combining the blurb with a research brief, the agent drafts a complete spec template and writes the finalized markdown to a scratchpad for review.

Does product spec drafting handle technical considerations and constraints?▼

Product spec drafting handles technical considerations and constraints by synthesizing the research brief. It populates the product template with explicit constraints and technical factors, writing the completed markdown spec while flagging any unresolved technical decisions as PM questions.