skills.rest
archibate
archibateCOMMUNITY
Explore all skills by this author →
Website𝕏@archibateGitHub

defining-requirements

Translate user needs into testable user stories with Gherkin acceptance criteria.

103|21|Updated Feb 12, 2026
Search Tags:#acceptance criteria#user stories#product requirements#lean startup#story mapping#gherkin#spec-lite
One-click install
npx skills add https://github.com/archibate/dotfiles-opencode --skill defining-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: defining-requirements
Source: https://github.com/archibate/dotfiles-opencode/tree/main/skills/defining-requirements
Command: npx skills add https://github.com/archibate/dotfiles-opencode --skill defining-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you turn vague ideas into shared, outcome-focused requirements that teams can build and verify without ambiguity.

Core Features & Use Cases

  • Collaborative, iterative requirements: shifts from one-time PRDs to continuous discovery with stakeholders and users.
  • Testable structure: expresses user needs with user stories and acceptance criteria using Given-When-Then (Gherkin) scenarios.
  • Better scoping and prioritization: uses story mapping and related frameworks to align on MVP slices and reduce fragmentation.
  • Practical PM workflow: supports “spec-lite” prototypes and hypothesis framing so requirements can be validated early.

Quick Start

Ask the AI to convert your product idea into user stories plus Given-When-Then acceptance criteria, including edge cases and an MVP story map.

Frequently Asked Questions about defining-requirements

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

FAQPage Schema
How do I write user stories and acceptance criteria for an MVP scope?▼

To write user stories and acceptance criteria for an MVP scope, you should translate user needs into testable outcomes by applying story mapping to align on slices and using Gherkin Given-When-Then scenarios.

What is the best way to convert vague product ideas into shared, testable requirements?▼

The best way to convert vague product ideas into shared requirements is shifting to continuous discovery with stakeholders, framing hypotheses, and translating outcomes into artifact-ready handover structures.

How do I use Gherkin Given-When-Then scenarios for product discovery?▼

Use Gherkin Given-When-Then scenarios during product discovery to author acceptance criteria that express user needs as clear, unambiguous, and testable outcomes for cross-functional execution.

Can I use spec-lite prototypes to validate product requirements early?▼

Yes, you can use spec-lite prototypes and hypothesis framing to validate product requirements early, reducing fragmentation by ensuring user needs are tested before full cross-functional execution.

Does defining lean startup requirements work for both web and mobile features?▼

Defining lean startup requirements works across web, mobile, and platform features by applying continuous discovery, user-story framing, and MVP story mapping to translate needs into shared outcomes.

Related Skills

Explore More Product & Management Skills→
chenluhanchenluhan

pm-normalized-brief

Converts raw product input into a structured brief with defined components.

Community
Advanced
matteocervellimatteocervelli
25

user-story-generator

Convert feature descriptions into INVEST-compliant user stories with YAML and Markdown exports.

Community
Advanced
SaharCarmelSaharCarmel
2

plan-collab

Enable inline comments and structured feedback on implementation plans via a web UI.

Community
Advanced
skycruzerskycruzer

Launch Planner

Transform unvalidated app ideas into actionable MVP plans with lean PRD structures.

Community
Basic