skills.rest
dinoudon
dinoudonCOMMUNITY
Explore all skills by this author →
GitHub

sdlc-requirements-engineering

Clarify software requirements using structured practices like user-story mapping and BDD/Gherkin.

Updated Jun 5, 2026
Search Tags:#requirements#bdd#gherkin#acceptance-criteria#jtbd#impact-mapping#user-story-mapping
One-click install
npx skills add https://github.com/dinoudon/sdlc-skills --skill sdlc-requirements-engineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-requirements-engineering
Source: https://github.com/dinoudon/sdlc-skills/tree/main/full/sdlc-requirements-engineering
Command: npx skills add https://github.com/dinoudon/sdlc-skills --skill sdlc-requirements-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured methods to define, validate, and trace software requirements, reducing ambiguity and misalignment across product, design, and engineering teams.

Core Features & Use Cases

  • User-story mapping to structure backlog around user activities and create MVP slices.
  • BDD / Gherkin workflows to convert requirements into executable scenarios.
  • Acceptance criteria formats to specify testable outcomes and quality gates.
  • Impact mapping & RICE/WSJF prioritization to link goals to deliverables and optimize delivery.
  • Specification by example / JTBD to turn business rules into concrete, testable specifications.

Quick Start

Outline your top product goal, then run a rapid Example Mapping session with the team to derive concrete rules and examples.

Frequently Asked Questions about sdlc-requirements-engineering

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

FAQPage Schema
How do I write acceptance criteria using BDD and Gherkin?▼

To write acceptance criteria using BDD and Gherkin, convert software requirements into executable scenarios. This structured approach reduces ambiguity by specifying testable outcomes and clear quality gates for engineering teams.

What is the best way to prioritize a product backlog using RICE and WSJF?▼

Prioritizing a product backlog using RICE and WSJF involves linking business goals to deliverables to optimize delivery value. This method ensures measurable outcomes and supports traceability across product and engineering teams.

How does user story mapping help structure an MVP?▼

User story mapping structures your backlog around user activities to create MVP slices. It aligns teams by organizing software needs into clear, actionable deliverables that reduce misalignment.

Can I use impact mapping and JTBD to validate software requirements?▼

Impact mapping and JTBD validate software requirements by turning business rules into concrete, testable specifications. This reduces ambiguity and clarifies software needs across product, design, and engineering teams.

When do I need specification by example for software requirements?▼

Specification by example is needed when you must reduce ambiguity in software requirements by converting them into concrete, testable specifications. It supports domain-driven design patterns and ATDD workflows.

Related Skills

Explore More Product & Management Skills→
anderson-0anderson-0
4

create-prd

Create structured product requirements documents from product ideas and discovery inputs.

Community
Advanced
Ahnd6474Ahnd6474

accelint-ac-to-playwright

Convert acceptance criteria into validated JSON test plans and Playwright spec files.

Community
Advanced
AsiaOstrichAsiaOstrich
70

forward-derivation

Generate BDD scenarios, TDD skeletons, and ATDD tables from SDD specifications.

Community
Intermediate
lotosbinlotosbin
14

product-manager

Coordinate product management tasks across planning, requirements, design, and competitive research.

Community
Intermediate