skills.rest
tjisousa
tjisousaCOMMUNITY
Explore all skills by this author β†’
𝕏@tjisousaGitHub

reqs

Creates sprint-based functional and non-functional requirements with acceptance criteria and traceability to tasks.

Updated Aug 23, 2026
Search Tags:#requirements#validation#backlog#traceability#acceptance-criteria
One-click install
npx skills add https://github.com/tjisousa/gensem --skill reqs-tjisousa
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: reqs
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/reqs
Command: npx skills add https://github.com/tjisousa/gensem --skill reqs-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The reqs skill provides a structured method to define, validate, and trace both functional and non-functional requirements for software projects, ensuring they are testable and aligned with sprint goals.

Core Features & Use Cases

  • Elicitation planning for sprint scope and backlog items
  • Drafting functional and non-functional requirements with clear acceptance criteria
  • Open questions tracking and traceability to tasks
  • Validation, coverage analysis, and quality gate notes to improve requirement quality

Quick Start

Describe the goals for your next sprint and watch the tool translate them into testable requirements.

Frequently Asked Questions about reqs

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

FAQPage Schema
How do I structure sprint goals into testable functional and non-functional requirements?β–Ό

Structuring sprint goals into testable requirements involves formalizing them into functional and non-functional entries with clear acceptance criteria, open questions, and traceability to project tasks.

What is requirements traceability and how does it apply to Agile backlog items?β–Ό

Requirements traceability maps structured functional and non-functional requirements directly to backlog tasks, ensuring sprint scope coverage and producing validation-ready artifacts.

How do I write acceptance criteria for project requirements to ensure they are validation-ready?β–Ό

Writing validation-ready acceptance criteria requires translating sprint goals into structured functional and non-functional requirements paired with open questions and quality gate notes.

Can I use this approach for backlog elicitation and validation in Agile projects?β–Ό

Backlog elicitation and validation in Agile projects benefit from formalizing sprint goals into structured, testable requirements with traceability and coverage analysis.

What is the best way to track open questions during requirements elicitation?β–Ό

Tracking open questions during requirements elicitation is handled by embedding them directly into structured requirement entries alongside acceptance criteria and traceability links.

How does coverage analysis improve the quality of software requirements?β–Ό

Coverage analysis improves software requirements by validating that all sprint goals map to testable functional and non-functional entries, identifying gaps, and generating quality gate notes.

Related Skills

Explore More Software Engineering Skills→
anthropicsanthropics
23.4k

sprint-planning

Generate a detailed sprint plan with goals, capacity, and backlog scoping.

Official
Intermediate
JunrootJunroot
3

verify

Validate GitHub issue requirements, designs, and plans against the codebase.

Community
Advanced
bychrisrbychrisr

aiox-sm

Manage user story creation, backlog grooming, and local branch operations.

Community
Advanced
rahmatullahbossrahmatullahboss

bmad-tea-testarch-trace

Automates traceability matrix creation and quality gate analysis from XML/YAML configs.

Community
Advanced