reversa-requirements

Generates a requirements document from a natural-language feature idea anchored in reverse-engineering artifacts.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-requirements-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-requirements
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.agents/skills/reversa-requirements
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-requirements-tjsasakifln

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a loose feature idea into a structured requirements document is slow and error-prone, especially when the document must stay consistent with knowledge already extracted from a legacy system. This Skill converts a free-form sentence or paragraph into a complete requirements.md file grounded in the Reversa pipeline artifacts. ## Core Features & Use Cases - Requirements drafting from natural language: Reads the user's free-form argument and produces a requirements.md following the project template, with confidence markers (🟢/🟡/🔴) and up to three [DÚVIDA] markers for open questions. - Legacy context anchoring: Pulls context from _reversa_sdd artifacts (architecture.md, domain.md, inventory.md, code-analysis.md) and cites sources in every requirement. - In-progress feature detection: Detects an existing feature in flight via physical artifacts (requirements.md, roadmap.md, actions.md checkboxes) and asks the user whether to continue, pause in parallel, or abandon it before writing anything. - Use Case: A developer types "/reversa-requirements add supplier score history chart" and receives a fully structured requirements document under _reversa_forward/001-supplier-score-history/, with citations to the reverse-engineering docs and a suggested next step. ## Quick Start Type /reversa-requirements followed by a sentence describing the feature you want, and the Skill will create the feature directory and a complete requirements.md for you.

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 requirements document with AI?▼

Invoke /reversa-requirements followed by a sentence describing the feature. The Skill reads the Reversa extraction artifacts, applies the requirements template, and writes a requirements.md with source citations, confidence markers, and up to three [DÚVIDA] markers for open questions.

What is the Reversa forward pipeline for feature development?▼

The forward cycle runs requirements, clarify, plan, to-do, audit, quality, and coding stages. reversa-requirements is the first stage, producing requirements.md inside a numbered feature directory under the forward folder defined in .reversa/state.json.

What happens if a feature is already in progress when I start a new one?▼

The Skill detects the in-progress feature from physical artifacts like requirements.md, roadmap.md, and actions.md checkboxes, then asks you to choose: continue the previous feature, pause it in a paused-features list, or abandon it. It never overwrites without asking.

Does reversa-requirements work without the reverse-engineering extraction?▼

It reads _reversa_sdd artifacts such as architecture.md and domain.md for context, but skips any file that does not exist. The requirements document will simply have fewer source citations and may contain more [DÚVIDA] markers.

Which AI coding assistants support this Skill?▼

The frontmatter declares compatibility with Claude Code, Codex, Cursor, Gemini CLI, and other agents compatible with the Agent Skills format. It relies only on file reading and writing, so no special tooling is required.