Writing PRD

Overview

Template + formatting rules for PRDs, usable in any repository. Not an interview — assemble the document from what's already known in the conversation; ask only if a required section is genuinely unfillable.

When to use

• User asks to write/draft a PRD, "продуктовые требования", "product requirements document".
• Goal/scope not yet decided? Run superpowers:brainstorming first — PRD documents a decision, doesn't make one.

Storage & naming

Same docs/ convention as roadmaps (see roadmap/SKILL.md, itself project-agnostic):

• docs/<feature-slug>/YYYY-MM-DD-<feature-slug>-prd.md at repo root.
• Git-tracked, kept permanently — never tmp/, never deleted after shipping.
• If the current environment offers native Plan Mode (EnterPlanMode/ExitPlanMode), use it like brainstorming/writing-plans: draft in Plan Mode's service file, ExitPlanMode, save to docs/ only after approval. If Plan Mode isn't available (e.g. a dispatched subagent), draft the content in chat first and get explicit user approval before saving.
• Never commit automatically — only on explicit request.