product-manager

To draft a PRD that aligns stakeholders, apply best-practice templates and DACI-based stakeholder mappings to structure goals, scope, and success criteria clearly. The skill guides this by running a lightweight intake to select the appropriate PRD format like Amazon PR/FAQ or Linear Project Spec.

The best way to structure user stories and acceptance criteria is by applying best-practice templates that map features directly to your prioritized backlog. This ensures development teams have clear, actionable scope and outcomes mapped from discovery to launch.

Yes, you can use this for roadmap planning across startups and enterprises. It provides living-doc guidance, DACI role assignments, and prioritization methods tailored to product initiatives ranging from early discovery to final launch stages.

Yes, this PRD format works with Amazon PR/FAQ, Intercom Intermission, and Linear Project Spec templates. It requires chosen PRD formats and structured intake questions to guide scope and outcomes tailored to your specific product stage and competitive landscape.

To start creating product documentation without a structured intake, run a lightweight intake to understand context including product stage, team size, decision enabled, audience, and competitive landscape. This context directly informs the selected PRD format and roadmap structure.

You need DACI roles for stakeholder mapping when creating product docs that require clear decision-making alignment across teams. DACI roles clarify who drives, approves, contributes, and informs, ensuring structured alignment on goals and scope from discovery to launch.