skills.rest
niltsiar
niltsiarCOMMUNITY
Explore all skills by this author →
Website𝕏@niltsiarGitHub

product-designer

Drafts product requirements documents with Gherkin-style acceptance criteria.

1|Updated Nov 26, 2025
Search Tags:#requirements#prd#product-management#user-stories#acceptance-criteria#mvp-planning
One-click install
npx skills add https://github.com/niltsiar/kotlin_multiplatform_pokedex --skill product-designer-niltsiar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-designer
Source: https://github.com/niltsiar/kotlin_multiplatform_pokedex/tree/main/.agents/product-designer
Command: npx skills add https://github.com/niltsiar/kotlin_multiplatform_pokedex --skill product-designer-niltsiar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing product requirements, feature scopes, and acceptance criteria consistently across teams can be time-consuming and error-prone. This skill helps teams produce PRDs, define MVP boundaries, and establish measurable success criteria.

Core Features & Use Cases

  • PRD creation and structure guidance: define problem, solution, scope, success metrics, and references.
  • MVP vs future scope planning: identify Must Have, Should Have, Could Have, and create prioritization rationale.
  • Acceptance criteria authoring: generate testable, Gherkin-formatted criteria aligned to user stories.
  • Cross-functional alignment: produce user stories and mapping to features to facilitate handoffs.

Quick Start

Provide a feature concept and key requirements, and the AI will draft a PRD, define MVP scope, and generate acceptance criteria.

Frequently Asked Questions about product-designer

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

FAQPage Schema
How do I draft a product requirements document from a feature concept?▼

Drafting a product requirements document involves structuring your feature concept into clear problem statements, solution scopes, and success metrics. You provide the initial idea and key requirements to generate a structured PRD.

What is the best way to define MVP scope and prioritize features?▼

Defining MVP scope requires categorizing features into Must Have, Should Have, and Could Have tiers. This prioritization creates a clear rationale for MVP boundaries and separates immediate scope from future development phases.

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

Writing Gherkin-style acceptance criteria involves formatting testable conditions aligned to user stories. This structured approach ensures cross-functional teams have measurable, clear test scenarios for feature validation and handoffs.

Can I use a PRD template for cross-functional product team alignment?▼

A PRD template facilitates cross-functional alignment by mapping user stories directly to features. This structured documentation ensures engineering, design, and product teams share a unified understanding of scope and success criteria.

What should I include in MVP planning to establish measurable success criteria?▼

MVP planning should include structured problem statements, scope guardrails, and specific success metrics. Defining these elements early ensures the MVP has clear boundaries and measurable outcomes for evaluation.

Related Skills

Explore More Product & Management Skills→
thepriceisrightthepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community
Advanced
roberttmadsen13-delroberttmadsen13-del

user-story-mapping

Visualize user journeys into a story map with activities, steps, and tasks.

Community
Intermediate
MaVoid-TeamMaVoid-Team

user-stories

Create structured user stories with descriptions, design references, and acceptance criteria.

Official
Basic
coco-researchcoco-research
264

prd-generator

Generate structured product requirements documents with user stories and success metrics.

Community
Advanced