product-owner

Convert ambiguous product ideas into Gherkin-compliant specifications and roadmap milestones.

8|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/ddobrin/plan-skills --skill product-owner-ddobrin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-owner
Source: https://github.com/ddobrin/plan-skills/tree/main/plugins/plan/skills/product-owner
Command: npx skills add https://github.com/ddobrin/plan-skills --skill product-owner-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms ambiguous product ideas into clear, testable specifications and prioritized roadmap milestones, preventing misunderstandings before technical planning begins.

Core Features & Use Cases

  • Interactive Requirement Discovery: Grills stakeholders with focused questions about edge cases, validation rules, error states, scaling limits, and user experience details.
  • Specification Creation: Produces structured, Gherkin-compliant product specifications with user stories, acceptance criteria, constraints, and applicable UI or UX descriptions.
  • Roadmap Management: Initializes and updates the master roadmap with release targets, milestone status, descriptions, and specification links.
  • Use Case: When a stakeholder proposes a new feature with incomplete requirements, use this Skill to resolve ambiguity and create a specification ready for architectural planning.

Quick Start

Use the product-owner skill to interview me about the feature, create a complete specification, and add the resulting milestone to the master roadmap.

Frequently Asked Questions about product-owner

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

FAQPage Schema
How do I turn ambiguous product ideas into actionable specifications?

To create actionable product specifications from ambiguous ideas, use interactive requirement discovery to clarify edge cases and validation rules, then generate structured product requirements with Gherkin-compliant acceptance criteria ready for architectural planning.

How do I write Gherkin acceptance criteria for product requirements?

Writing Gherkin acceptance criteria involves structuring product requirements into user stories with defined constraints, validation rules, and documented edge cases. This ensures specifications remain testable and unambiguous before technical planning begins.

What is the best way to conduct stakeholder interviews for feature discovery?

Conducting stakeholder interviews for feature discovery requires asking focused questions about error states, scaling limits, and user experience details. This resolves incomplete requirements and extracts necessary constraints for comprehensive product specifications.

How do I update a roadmap with new feature milestones after specification?

Updating a roadmap with new feature milestones involves adding release targets, milestone status, descriptions, and specification links to the master roadmap. This occurs after finalizing testable acceptance criteria and before architectural planning.

Can I use this approach for bug fixes and refactoring initiatives?

Yes, this specification approach applies to bug fixes, refactoring initiatives, and release planning. It converts these ambiguous product tasks into rigorous, testable specifications with documented edge cases before technical execution.