Verified:GitHub

reversa-clarify

Generate targeted clarification questions and update active requirements documents.

Updated Mar 31, 2026

Search Tags:#ambiguity resolution #question generation #requirements clarification #requirements documentation #forward planning #hooks orchestration

Ready to run

npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-clarify-afsjr

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves ambiguous or missing requirement details by asking up to five targeted questions and merging the answers back into the active requirements document.

Core Features & Use Cases

Requirements ambiguity discovery: Identifies [DÚVIDA] markers, vague phrases, undefined terms, and obvious coverage gaps in requirements.
Ranked question generation: Produces no more than five questions, ordered by their impact on the eventual plan.
Direct requirements update: Writes answers into the appropriate ## Esclarecimentos → ### Sessão YYYY-MM-DD section and removes resolved [DÚVIDA] entries and corresponding gaps from ## Lacunas.

Quick Start

Use /reversa-clarify to generate clarifying questions and apply your answers directly to requirements.md for the currently active feature.

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 and identify missing details in my project documentation?▼

To resolve ambiguous requirements, you generate targeted clarification questions that identify vague phrases and undefined terms in your requirements documentation. This process asks up to five ranked questions to uncover missing details and obvious coverage gaps before forward planning begins.

What is the best way to generate clarification questions for requirement gaps before forward planning?▼

Generating clarification questions involves scanning your active requirements document for [DÚVIDA] markers and obvious coverage gaps. The system ranks these ambiguities by their impact on the eventual plan, producing no more than five targeted questions to ensure critical forward planning decisions are resolved.

How do I update a requirements document after clarifying open points with stakeholders?▼

You update a requirements document by integrating answers into the appropriate ## Esclarecimentos section and removing resolved [DÚVIDA] entries from ## Lacunas. This direct requirements update ensures your active feature documentation remains accurate and free of open points.

Do I need an active-requirements.json file to resolve ambiguities in my workflow?▼

Yes, you need an active-requirements.json file and a valid state.json for folder paths to resolve ambiguities. The workflow validates these prerequisites and applies before-clarify hooks before generating targeted questions for your requirements documentation.

Why does my requirements clarification process stop before generating any questions?▼

Your requirements clarification process stops when state.json folder paths are missing or active-requirements.json existence validation fails. The system enforces these prerequisites and applies before-clarify hooks before it can generate ranked questions and update your active feature requirements.

Can I use targeted question generation for requirements documentation in a forward-cycle workflow?▼

Yes, you can use targeted question generation for requirements documentation in a forward-cycle workflow. It applies specifically to scenarios between requirements and planning phases, applying hooks orchestration to merge answers directly into your active document and remove existing gaps.