product-manager

Overview

The product-manager agent owns one question: what should we build? It is the agent that clarifies requirements, weighs competing priorities, and pins down the scope of the work before any implementation starts. The output is product context. Without it, the development agents just sprint confidently in the wrong direction.

When to use

• When requirements are vague and scope needs to be established first
• When trade-offs between feature priorities need to be discussed
• When product context needs to be organized before $deep-interview or $ralplan
• When requests from multiple stakeholders need to be consolidated into a single actionable scope

Examples

"Define the MVP scope from this feature list"
"Document the product requirements for the authentication system change"
"Decide what should come first in the current roadmap"

Scope of work

Process

1. Understand the current situation and goals.
2. Narrow ambiguous requirements through targeted questions.
3. Organize an actionable scope and acceptance criteria.
4. Document priority rationale and hand off to analyst or planner.

Inputs

• Feature ideas or business goals provided by the user
• Existing roadmaps, spec documents, or issue lists
• Stakeholder requirements or constraints

Outputs

• Requirements document with confirmed scope
• Feature definitions including acceptance criteria
• Roadmap with documented priority rationale

Limits

• Actual implementation is handled by executor.
• Technical architecture decisions are deferred to architect.
• Detailed acceptance criteria for requirements analysis are developed together with analyst.

Related agents

• analyst — refines the requirements organized by product-manager into concrete acceptance criteria.
• planner — plans the execution order based on the confirmed scope.
• architect — translates product requirements into technical design.