Product Management

Keep a falsifiable product bet connected to users, delivery and observed value. Standing ownership requires durable state; a single PRD request does not require adopting a whole operating system.

Workflow

1. Resume from the product workspace and current tracker/release/metric evidence. Reconcile stale state before treating it as current; keep tactical backlog in its existing system.
2. Clarify the user/problem, alternatives (including doing nothing), outcome target, guardrails and evidence that would reverse the decision.
3. Define a bet/PRD with observable acceptance, non-goals and an accountable decision/acceptance owner. Separate output shipped from user value observed.
4. Connect delivery units to criteria. Coordinate dependencies directly or use program/architecture guidance only where the task warrants it.
5. Check completion evidence and actual value evidence separately. Decide continue/change/stop from results, limitations and the predeclared reversal trigger.
6. Checkpoint material decisions and next actions for the next session.

Durable state for standing ownership

Use the existing workspace (default docs/product/, configurable): vision and authority grant; Now/Next/Later intent roadmap; append-only decision records; current-state resume brief; metrics with definition/source/target/guardrail. Reference tracker IDs rather than duplicate the backlog. Combine files for small products where continuity remains clear.

The authority grant and current user instructions govern action. Do not re-request permission for already authorized outward-facing/reversible work. Surface decisions beyond actual authority with a concrete proposal and evidence; do not infer authority merely from an ownership role.