Does it support Given/When/Then acceptance criteria?

Yes, it automatically generates detailed acceptance criteria using the Given/When/Then syntax to facilitate testing and quality assurance.

What format does this skill use for user stories?

It follows the industry-standard format: 'As a [role], I want [feature], so that [benefit]' to ensure clarity and user-centricity.

How does it help ensure requirements are ready for development?

The skill applies the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) to validate that user stories are actionable for developers.

Where are the PRD artifacts saved?

Generated documents are saved as Markdown files in the ./artifacts/ directory with a naming convention of prd_[feature].md for easy version control.

Product Requirement Engineer

Name: Product Requirement Engineer
Author: dralgorhythm

bydralgorhythm

•

コラボレーションツール

Generates comprehensive Product Requirements Documents (PRDs) including user stories, acceptance criteria, and project scoping.

概要

The Product Requirement Engineer skill transforms Claude into a technical product manager to streamline the transition from high-level ideas to actionable engineering specifications. It enforces a structured workflow for defining business goals, identifying stakeholders, and drafting INVEST-compliant user stories with detailed Given/When/Then acceptance criteria. By automating the creation of PRD artifacts and saving them to standardized directories, it ensures project teams maintain a consistent source of truth regarding scope, success metrics, and functional requirements.

主な機能

Automated user story creation following standard role-based templates.
Detailed acceptance criteria generation using Given/When/Then syntax.
1 GitHub stars
INVEST criteria validation to ensure requirements are testable and estimable.
Structured PRD generation with goals, metrics, and scope definitions.
Automated artifact management for saving specifications to project directories.

ユースケース

Facilitating stakeholder reviews with professional, standardized project artifacts.
Defining the technical scope and functional requirements for new software features.
Translating business requests into structured documentation for engineering teams.

概要

主な機能

Automated user story creation following standard role-based templates.
Detailed acceptance criteria generation using Given/When/Then syntax.
1 GitHub stars
INVEST criteria validation to ensure requirements are testable and estimable.
Structured PRD generation with goals, metrics, and scope definitions.
Automated artifact management for saving specifications to project directories.

ユースケース

Facilitating stakeholder reviews with professional, standardized project artifacts.
Defining the technical scope and functional requirements for new software features.
Translating business requests into structured documentation for engineering teams.