managing-productlisted

# Managing Product Defines *what to build* before any architecture or code: translates an understood idea into a structured, prioritised PRD that agents can execute against without ambiguity. **Position:** understanding-the-ask (clarify problem) → solutioning (choose direction) → managing-product (define what to build) → architecting-software (design how). **Inputs:** a clear problem statement, a chosen solution direction ("we will build software"), and the user's domain knowledge accessible through conversation. **Output:** `PRD.md` with five essential elements — problem statement, target users, success criteria, scope (MoSCoW-prioritised plus explicit out-of-scope), and requirements as user stories with testable acceptance criteria. **Not covered:** problem clarification or solution direction (upstream), technical architecture (architecting-software), chunk enrichment, roadmapping, sprint planning, rollout strategy. ## Workflow ### Step 1: Establish Starting Context Check whether you already have a clear problem statement, an identified audience, and any stated constraints. If the user arrives with problem and audience clear (e.g. "I want to build a habit tracking app for myself"), confirm inline and proceed — upstream skills are not required. If either remains vague after confirmation, return to understanding-the-ask. State what you understand so the user can correct it before extraction begins: > "Before we define what to build, let me confirm: we're solving [pr