agfwriting-prdlisted

# Writing a PRD (Product Requirements Document) Use this skill when: - product-lead finished `superpowers:brainstorming` and the user approved the rough direction - Formalizing a feature into `docs/prd/[feature]-[YYYY-MM-DD].md` before dispatching execution layer - Updating an existing PRD after an open question is resolved ## Pre-conditions - [ ] Feature direction approved (don't write a PRD for something still being explored — use `superpowers:brainstorming` first) - [ ] You know who the user is and what business outcome you're optimizing - [ ] At least 1 measurable success metric is identifiable (else: brainstorm more, the requirement is too vague) If any precondition fails: **stop, do not write a PRD**. Route back to brainstorming or SendMessage user for clarification. ## File path & naming `docs/prd/[feature-kebab-case]-[YYYY-MM-DD].md` — e.g. `docs/prd/oauth-login-2026-05-12.md`. One PRD per feature. Updates go to the same file with a `## Changelog` entry at the bottom; do NOT create a new dated file unless scope materially changes (then archive old, link to new). ## Required sections (in order) ```markdown # PRD — [Feature Name] - **Date**: YYYY-MM-DD - **Owner**: product-lead - **Status**: Draft / Review / Approved / In Progress / Done / Archived - **Estimated effort tier**: Small / Medium / Large（依据 skill `agf:cost-budget`） ## 1. Background 为什么做？解决的用户痛点 / 业务驱动；引用 Linear ticket / Slack 讨论 / 用户访谈。1–3 段。 ## 2. Goal & Non-Goals **目标**: - 一句话目标声明 - KPI（上线后用