product-owner

Draft PRDs and acceptance criteria from stakeholder inputs using MoSCoW and RICE frameworks.

Updated Apr 4, 2026

Search Tags:#prioritization #backlog #prd #rice #acceptance-criteria #moscow

Ready to run

npx skills add https://github.com/asalhamed/dev-agents --skill product-owner-asalhamed

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-owner
Source: https://github.com/asalhamed/dev-agents/tree/main/product-owner
Command: npx skills add https://github.com/asalhamed/dev-agents --skill product-owner-asalhamed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write PRDs, define acceptance criteria, and prioritize features to keep stakeholders aligned and drive focused delivery.

Core Features & Use Cases

PRD drafting: capture objectives, scope, success metrics, and alignment with business goals.
Acceptance criteria generation: produce testable Given/When/Then criteria for features.
Backlog prioritization: apply MoSCoW and RICE frameworks to sequence work.
Collaboration facilitator: translate stakeholder requests into actionable work items for analysts, UX researchers, and engineers.

Quick Start

Draft a PRD for a new feature, including objective, scope, success metrics, and a prioritized backlog.

Frequently Asked Questions about product-owner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I draft a PRD that aligns stakeholders and drives focused delivery?▼

Drafting a PRD involves capturing objectives, scope, success metrics, and business goal alignment to keep stakeholders aligned and drive focused delivery. It translates stakeholder requests into structured output artifacts for downstream teams.

What is the best way to prioritize a backlog using MoSCoW and RICE frameworks?▼

Prioritizing a backlog with MoSCoW and RICE frameworks sequences work by categorizing features into must-haves and scoring them by reach, impact, confidence, and effort. This scopes features across product and system boundaries effectively.

How do I write testable acceptance criteria for new product features?▼

Writing testable acceptance criteria requires producing structured Given/When/Then statements for features. This ensures validation requirements are clear and provides structured output artifacts for downstream engineering teams.

Can I translate stakeholder requests into actionable work items for UX researchers and engineers?▼

Translating stakeholder requests into actionable work items is supported by acting as a collaboration facilitator. It converts stakeholder inputs into structured PRDs and testable acceptance criteria for analysts, UX researchers, and engineers.

Does this approach scope features across both product and system boundaries?▼

Scoping features across product and system boundaries is achieved by applying MoSCoW and RICE frameworks during backlog prioritization. This ensures structured output artifacts align with business goals and system constraints.