reversa-requirements

Convert feature ideas into requirements.md using Reversa pipeline artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reversa turns a free-form feature idea into a complete requirements document, grounded in the legacy pipeline artifacts, so you don’t start from a vague prompt or miss critical context.

Core Features & Use Cases

  • End-to-end requirements drafting: Converts the user’s description into a fully structured requirements.md that follows the Reversa template and section order.
  • Pipeline-aware context gathering: Reads _reversa_sdd/ architecture, domain rules, inventory, and targeted code analysis to anchor requirements in what already exists.
  • Active feature detection & safe re-execution policy: Detects whether a prior feature is physically in progress and always prompts the user before writing to avoid overwriting work.
  • Hook-aware execution: Loads .reversa/hooks.yml and runs/collects “before-requirements” hooks, optionally presenting available hooks when needed.
  • Atomic persistence to forward folder: Computes a new feature directory, updates .reversa/active-requirements.json atomically, and writes requirements.md to the correct place.
  • Supports parallel workflows: Can pause or abandon an existing in-progress feature while keeping previous artifacts intact.

Quick Start

Use the skill by typing /reversa-requirements and describing the feature you want to build in one or two paragraphs.

Frequently Asked Questions about reversa-requirements

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

FAQPage Schema
How do I turn a feature idea into a complete requirements document?

To turn a feature idea into a requirements document, you provide a free-form text description and the skill converts it into a fully structured requirements.md file. It reads existing architecture and domain rules to anchor the generated document in your current pipeline artifacts.

How does pipeline-aware context gathering work for feature planning?

Pipeline-aware context gathering works by reading architecture, domain rules, inventory, and targeted code analysis from your pipeline artifacts. This ensures the drafted requirements are anchored in existing system constraints rather than starting from a vague prompt.

Can I safely generate a new requirements.md without overwriting active feature artifacts?

Yes, you can safely generate requirements without overwriting artifacts because the skill detects physically in-progress features and prompts the user before writing. It computes a new feature directory and updates active-requirements.json atomically.

Do I need hooks configuration to draft requirements from text?

You do not strictly need hooks to draft requirements, but the skill loads .reversa/hooks.yml to run and collect before-requirements hooks if present. This enables optional pipeline automation and quality validation during the document generation process.

What happens to an in-progress feature when I start a new requirements cycle?

When starting a new requirements cycle with an in-progress feature, the skill supports parallel workflows by allowing you to pause or abandon the existing feature. It keeps previous artifacts intact while computing a new forward folder for the current requirements.

What is reverse-pipeline state management for requirement generation?

Reverse-pipeline state management for requirement generation is the process of reading .reversa/state.json and active-requirements.json to detect feature stages. It persists new requirements.md files to the computed forward folder to maintain continuous pipeline automation.