skills.rest
jcteague
jcteagueCOMMUNITY
Explore all skills by this author →
GitHub

product-owner

Elicit features and decompose them into user stories with Gherkin acceptance criteria.

Updated Mar 6, 2026
Search Tags:#epics#user-stories#acceptance-criteria#backlog-management#wheelbase#feature-elicit
One-click install
npx skills add https://github.com/jcteague/wheelbase --skill product-owner-jcteague
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-owner
Source: https://github.com/jcteague/wheelbase/tree/main/.claude/skills/product-owner
Command: npx skills add https://github.com/jcteague/wheelbase --skill product-owner-jcteague

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide clear product direction for Wheelbase by guiding stakeholders through feature discovery, story creation, and backlog governance.

Core Features & Use Cases

  • Feature elicitation: turn ideas into concrete, well-scoped product requirements.
  • Story writing: produce user stories with Given-When-Then acceptance criteria and EPIC organization.
  • Backlog management: maintain epics, track dependencies, and plan work using the beads CLI.
  • Domain validation: consult the options-expert skill for domain knowledge and risk checks.
  • Mockup integration: generate UI mockups after story creation to validate design.

Quick Start

Provide feature elicitation, write well-scoped user stories with acceptance criteria, and organize them into epics and backlog items for Wheelbase.

Frequently Asked Questions about product-owner

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

FAQPage Schema
How do I elicit features and break them down into user stories with acceptance criteria?▼

To elicit features and write user stories, guide stakeholders through feature discovery, decompose ideas into well-scoped stories with Given-When-Then Gherkin acceptance criteria, and organize them into epics for backlog governance.

What is the best way to manage a product backlog using epics and user stories?▼

Managing a product backlog with epics and user stories involves coordinating feature discovery, tracking dependencies, and planning work hierarchically across phases using the beads CLI to maintain backlog governance.

How do I write Gherkin acceptance criteria for user stories?▼

Writing Gherkin acceptance criteria for user stories requires structuring each story's validation rules using Given-When-Then syntax, ensuring each includes context, dependencies, and mockups for domain validation.

Can I integrate UI mockups after creating user stories for feature validation?▼

Yes, you can integrate UI mockups after story creation to validate design. This ensures each user story includes visual context and design validation alongside its acceptance criteria and dependencies.

Do I need domain validation when eliciting features for product planning?▼

You need domain validation during feature elicitation to perform risk checks and ensure domain accuracy. Consulting the options-expert skill provides the necessary domain knowledge for well-scoped product requirements.

Related Skills

Explore More Product & Management Skills→
w020316w020316

project-requirements-clarification

Guide structured questioning to clarify project ideas into requirement documents.

Community
Intermediate
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

Community
Advanced
gaiastudio-aigaiastudio-ai
2

gaia-validate-story

Validate story files against canonical artifacts and record verdicts via review-gate.sh.

Official
Intermediate
dundasdundas

user-story-generator

Generate user stories with acceptance criteria in Markdown format.

Community
Intermediate