skills.rest
eyadsibai
eyadsibaiCOMMUNITY
Explore all skills by this author →
Website𝕏@eyadsibaiGitHub

requirements-engineering

Define software requirements using EARS and User Stories templates.

7|1|Updated Jan 14, 2026
Search Tags:#specification#requirements#product management#acceptance criteria#user stories#EARS
One-click install
npx skills add https://github.com/eyadsibai/ltk --skill requirements-engineering-eyadsibai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-engineering
Source: https://github.com/eyadsibai/ltk/tree/main/plugins/ltk-engineering/skills/requirements-engineering
Command: npx skills add https://github.com/eyadsibai/ltk --skill requirements-engineering-eyadsibai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides structured methods for clearly defining project requirements before development begins, ensuring everyone understands what needs to be built and why.

Core Features & Use Cases

  • Structured Requirements: Utilizes formats like EARS and User Stories for clarity.
  • Scope Definition: Helps define what is in and out of scope for a project.
  • Use Case: When starting a new feature, use this Skill to draft clear user stories and acceptance criteria, ensuring the development team builds the right functionality.

Quick Start

Use the requirements-engineering skill to draft user stories and acceptance criteria for a new login feature.

Frequently Asked Questions about requirements-engineering

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

FAQPage Schema
What is the EARS syntax for writing software requirements?▼

User stories capture product requirements from an end-user perspective. This Skill provides templates to draft user stories and acceptance criteria, ensuring development teams build the right functionality for new features.

How do I write acceptance criteria for a new product feature?▼

Acceptance criteria define the boundaries and success metrics for a feature. This Skill helps you draft clear criteria using structured formats like EARS and user stories, ensuring the development team understands what needs to be built.

What is the best way to define project scope and prevent scope creep?▼

Defining project scope requires structured specification of what is in and out of bounds. This Skill helps capture functional and non-functional requirements using methodologies like EARS to ensure clarity and prevent ambiguous specifications.

Can I use this for both functional and non-functional requirements?▼

Yes, you can define both functional and non-functional requirements. The Skill provides best practices and templates to capture all project specifications, ensuring complete clarity on scope, acceptance criteria, and success metrics.

When should I use EARS instead of user stories for requirement specification?▼

Use EARS for precise, unambiguous requirement specifications and user stories for capturing functionality from an end-user perspective. This Skill facilitates both methodologies to address the problem of incomplete or ambiguous project specifications.

Related Skills

Explore More Product & Management Skills→
ydnikolaevydnikolaev
8

product-analyst

Translate product vision into user stories, requirements, and roadmaps.

Community
Advanced
shwilliamsonshwilliamson

user-stories

Write user stories with acceptance criteria and INVEST guidelines.

Community
Basic
edwardmonteiroedwardmonteiro

delivery.roadmap

Translate strategy into a sequenced delivery roadmap with risks and stakeholder communication.

Community
Basic
windyskywindysky

moai-workflow-spec

Orchestrate SPEC workflows with EARS format and Plan-Run-Sync lifecycle.

Community
Basic