reversa-requirements

Generate requirement documents from natural language feature descriptions.

Updated May 19, 2026
One-click install
npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-requirements-silaslopes100
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-requirements
Source: https://github.com/silaslopes100/lojacarmenedaniel/tree/main/.agents/skills/reversa-requirements
Command: npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-requirements-silaslopes100

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between high-level feature ideas and structured technical requirements by leveraging existing project knowledge and legacy documentation.

Core Features & Use Cases

  • Automated Requirement Drafting: Converts natural language feature requests into standardized requirement documents.
  • Context-Aware Analysis: Integrates insights from existing architecture, domain rules, and code analysis to ensure consistency.
  • Lifecycle Management: Tracks feature progress, handles dependencies, and manages state transitions across the development pipeline.

Quick Start

Initiate a new feature requirement by typing the command reversa-requirements followed by a brief description of the functionality you wish to implement.

Frequently Asked Questions about reversa-requirements

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

FAQPage Schema
How do I generate technical requirements from natural language feature descriptions?

This skill converts natural language feature requests into standardized project requirement documents by analyzing existing architecture and domain rules to ensure technical alignment and structural consistency.

Can I generate requirement documentation that aligns with my existing legacy codebase?

Yes, the skill integrates insights from existing architecture and legacy documentation to maintain consistency across legacy and new codebases within a defined forward-engineering pipeline.

How do I track feature progress and state transitions during the requirement pipeline?

The skill implements strict state tracking and validation cycles to manage feature progress, handle dependencies, and execute state transitions across the development pipeline for quality assurance.

What is the best way to draft architecture requirements for new domain features?

The best way to draft architecture requirements is to input a brief natural language functionality description, allowing context-aware analysis to map domain rules and architecture constraints into structured documentation.

Does this requirement generation pipeline support forward-engineering workflows?

Yes, the skill explicitly operates within a defined forward-engineering pipeline to maintain technical alignment and quality assurance across both legacy and new codebases.