skills.rest
houke
houkeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requirements-engineering

Generate structured product requirements templates with Given-When-Then criteria.

Updated Jan 25, 2026
Search Tags:#templates#documentation#requirements#prd#invest#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/houke/nexus-playground --skill requirements-engineering-houke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-engineering
Source: https://github.com/houke/nexus-playground/tree/main/.github/skills/requirements-engineering
Command: npx skills add https://github.com/houke/nexus-playground --skill requirements-engineering-houke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured templates and guidelines for writing clear product requirements.

Core Features & Use Cases

  • Standardized User Story format (As a, I want, So that)
  • Acceptance Criteria patterns (Given-When-Then, checklist, rules)
  • PRD templates and planning artifacts (PRD, epic, goals, success metrics)
  • Quick Start examples and ready-to-copy templates for teams building software products.

Quick Start

To begin, copy the User Story Template from templates/user-story.md, use REFERENCE.md as a cheatsheet, and draft a minimal P0 user story with Given/When/Then criteria. For example: As a user, I want to [goal], so that [benefit].

Frequently Asked Questions about requirements-engineering

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

FAQPage Schema
How do I write a user story using the standard As a I want So that format?▼

To write a user story using the As a I want So that format, define the user role, their goal, and the benefit. This standardized format ensures clear product needs and aligns cross-functional teams.

What is the Given-When-Then pattern for acceptance criteria?▼

The Given-When-Then pattern for acceptance criteria structures test scenarios by defining initial context, an action, and expected results. This enforces formal formats for clear product requirements.

How do I prioritize product roadmap features using RICE scoring and MoSCoW?▼

Prioritize product roadmap features using RICE scoring and MoSCoW methods by evaluating reach, impact, confidence, and effort, then categorizing requirements into must-have and should-have tiers.

Does this provide a PRD template with success metrics and release plans?▼

Yes, this provides PRD templates and planning artifacts including goals, success metrics, epics, and release plans. These ready-to-copy templates help teams standardize software product documentation.

What is the Definition of Ready and Definition of Done in software requirements?▼

Definition of Ready and Definition of Done in software requirements are formal checklists ensuring user stories meet entry criteria before development and completion criteria before release.

Can I use these requirement templates for cross-functional team planning?▼

Yes, you can use these requirement templates for cross-functional team planning. They apply to product management, software engineering, and design teams to standardize user stories and PRDs.

Related Skills

Explore More Product & Management Skills→
clovernguyen1010-ship-itclovernguyen1010-ship-it

bmad-agent-pm

Guide user interviews and requirements discovery to draft PRDs.

Community
Intermediate
wtthorntonwtthornton
4

planner

Creates user stories, epics, and tasks with Fibonacci point estimates.

Community
Advanced
gmliaogmliao
1

specify

Create structured feature specs with user stories and acceptance criteria.

Community
Basic
vadimcomanescuvadimcomanescu
24

agile-product-owner

Generate INVEST-compliant user stories and plan sprints with capacity.

Community
Intermediate