Verified:GitHub

reversa-clarify

Generate targeted clarification questions and update requirements.md from answers.

Updated May 5, 2026

Search Tags:#planning #ambiguity resolution #requirements management #documentation update #requirements clarification #reversa

Ready to run

npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-clarify-alexandrepontesjr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-clarify
Source: https://github.com/AlexandrePontesjr/calculadora-Juridica/tree/main/.agents/skills/reversa-clarify
Command: npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-clarify-alexandrepontesjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill clarifies ambiguous or missing requirements so planning can proceed with fewer assumptions and fewer rework cycles.

Core Features & Use Cases

Requirement De-ambiguation: Identifies unclear sections in the active requirements and turns them into up to five targeted questions.
State-Driven Context: Uses .reversa/state.json and .reversa/active-requirements.json to locate the correct feature and apply the standard before-clarify hooks.
Requirements Update Loop: Writes answers back into requirements.md under ## Esclarecimentos, updates ## Lacunas, and preserves unresolved items.

Quick Start

Use this Skill by asking an assistant to run it when you type /reversa-clarify (or say “esclarecer dúvidas”) to generate and collect clarifying answers for the current feature requirements.

Frequently Asked Questions about reversa-clarify

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

FAQPage Schema

How do I resolve ambiguous requirements before starting project planning?▼

Requirement de-ambiguation identifies undefined constraints and missing edge cases in active requirements, generating up to five ranked clarification questions. It processes vague language and missing details to ensure planning proceeds with fewer assumptions and reduced rework cycles.

How do I update a requirements document with clarified answers from stakeholders?▼

You update requirements.md atomically by writing collected answers under the Esclarecimentos section and updating Lacunas. This requirements update loop preserves unresolved items while integrating clarified details directly into the active document.

How does state-driven context work for resolving missing requirement details?▼

State-driven context uses .reversa/state.json and .reversa/active-requirements.json to locate the correct feature and apply before-clarify hooks. This ensures clarification questions target the accurate active requirements context before generating outputs.

What is the maximum number of clarification questions generated for vague requirements?▼

The maximum is five ranked, optioned questions generated for vague requirements. The Skill enforces this limit to keep the de-ambiguation process focused, ensuring stakeholders address only the most critical missing details or undefined constraints.

Can I use this clarification process for requirements with specific doubt markers?▼

Yes, this clarification process applies to forward planning workflows where requirements contain [DÚVIDA] markers, vague language, or undefined constraints. It identifies these specific markers and missing edge cases to generate targeted clarification questions.