prd-writerlisted

# PRD Writer ## Goal Create a clear product or implementation brief that preserves decisions, unresolved questions, scope, validation, and non-goals. ## When to use - The user asks for a PRD, implementation brief, product spec, or handoff spec. - Current conversation context needs to become a durable planning artifact. - Engineering, product, validation, and rollout expectations need one shared document. ## When not to use - The user only needs an ADR for a narrow repo-level decision. - The task is ready for implementation and does not need a planning artifact. - The user asks for a marketing document rather than product or engineering scope. ## Inputs to inspect - Current conversation, existing specs, issues, roadmap items, ADRs, and domain docs. - User goals, constraints, target users, non-goals, and known decisions. - Existing validation commands and release process when relevant. ## Workflow 1. Identify the audience and artifact type: PRD, implementation brief, or handoff spec. 2. Separate problem, goals, non-goals, proposed solution, decisions, and open questions. 3. Write user stories or use cases only when they clarify behavior. 4. Include acceptance criteria and validation commands. 5. Add rollout, migration, observability, docs, or support notes only when relevant. 6. Keep unresolved questions explicit instead of pretending decisions are final. 7. Ask before writing files unless the user requested a file update. ## Safety rules - Do not invent product dec