skills.rest
nicolasguelfi
nicolasguelfiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reqs

Aggregate and formalize software requirements with acceptance criteria and traceability.

4|1|Updated Apr 11, 2026
Search Tags:#requirements#validation#backlog#traceability#sprint#acceptance-criteria
One-click install
npx skills add https://github.com/nicolasguelfi/gensem --skill reqs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reqs
Source: https://github.com/nicolasguelfi/gensem/tree/main/gse-one/plugin/skills/reqs
Command: npx skills add https://github.com/nicolasguelfi/gensem --skill reqs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define functional and non-functional requirements for software projects. Triggered by the /gse:reqs command to start requirements elicitation and validation.

Core Features & Use Cases

  • Elicitation-driven requirement capture: Step 0 Open Questions Gate, Step 0.5 Conversational elicitation, and Step 1 scope determination.
  • Test-driven requirements: Each requirement includes acceptance criteria and traces back to backlog items.
  • Validation and coverage: Steps 5 and 6 assess completeness, consistency, and coverage, with a quality guardrail before persistence.
  • Persistence: Persist finalized requirements to docs/sprints/sprint-{NN}/reqs.md with proper traces and metadata.

Quick Start

To begin, run the /gse:reqs command and follow the guided prompts to generate, validate, and persist sprint requirements.

Frequently Asked Questions about reqs

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

FAQPage Schema
How do I define sprint requirements with verifiable acceptance criteria?▼

Sprint requirements with verifiable acceptance criteria are defined through guided elicitation, scope determination, and validation steps that enforce testable criteria before persisting to the sprint document. Each requirement traces back to backlog items.

What is requirements traceability across tasks, code, and tests?▼

Requirements traceability links each functional and non-functional requirement to backlog items, code, and tests. It ensures completeness and coverage during validation by mapping acceptance criteria directly to implementation tasks.

How do I validate software requirements for completeness and consistency?▼

Software requirements validation assesses completeness, consistency, and coverage through dedicated validation steps. A quality guardrail checks structured requirements and their testable acceptance criteria before allowing persistence to the sprint document.

Can I capture unresolved technical decisions during requirements elicitation?▼

Unresolved technical decisions are captured during requirements elicitation using open questions. An initial open questions gate and conversational elicitation process formalizes these items alongside functional and non-functional requirements.

How do I structure functional and non-functional requirements for sprint planning?▼

Functional and non-functional requirements for sprint planning are structured with testable acceptance criteria, open questions, and traceability metadata. The finalized requirements are persisted to docs/sprints/sprint-NN/reqs.md.

Related Skills

Explore More Software Engineering Skills→
devmuslimdevmuslim

backlog-grooming

Facilitate structured backlog grooming sessions using the 3 R's framework.

Community
Intermediate
qlawmarqqlawmarq

sdd-validate-impl

Validate software implementations against requirements, design, and tasks.

Community
Advanced
Lobbi-DocsLobbi-Docs
18

scrum

Plan sprints, coordinate standups, and manage backlogs for Agile teams.

Official
Basic
fabiolpgomesfabiolpgomes

aiox-qa

Review test architecture and enforce quality gate decisions.

Community
Advanced