reversa-clarify

Generate up to five clarifying questions for feature requirements and update the requirements document.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-clarify-stribus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-clarify
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-clarify
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-clarify-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams and developers resolve ambiguities in feature requirements by generating up to five targeted clarifying questions and integrating the answers back into the requirements document, reducing planning delays and misinterpretations. It activates when users request clarifications via /reversa-clarify or equivalent phrases and serves as an optional step in the forward cycle between /reversa-requirements and /reversa-plan.

Core Features & Use Cases

  • Generate up to five clarifying questions focused on missing details in a feature's requirements.
  • Integrate the answers back into the feature's requirements.md, updating the Esclarecimentos section and removing resolved questions.
  • Triggered by commands like /reversa-clarify, "reversa-clarify", "esclarecer dúvidas", or requests to remove open points before planning.
  • Acts as a structured intervention in the forward planning cycle between /reversa-requirements and /reversa-plan.

Quick Start

Ask clarifying questions about the current feature's requirements and embed the user responses back into the requirements document.

Frequently Asked Questions about reversa-clarify

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

FAQPage Schema
How do I clarify ambiguous feature requirements before planning?

Clarifying feature requirements involves generating up to five targeted questions to identify missing details, then integrating the answers directly back into the requirements document to resolve ambiguities and reduce planning delays.

What is the best way to remove open points from a requirements document?

The best way to remove open points from a requirements document is by generating multiple-choice or short-answer clarifying questions, then updating the document's clarification section with the resolved answers.

When do I need to generate clarifying questions for my product requirements?

You need to generate clarifying questions for your product requirements when you signal ambiguity or request clarification, serving as an optional structured intervention step before moving into the planning phase.

Does this requirements clarification process update the original requirements.md file?

Yes, the requirements clarification process updates the original requirements document by embedding the answers into the clarification section and automatically removing the resolved open questions.

How do I format questions when resolving ambiguities in feature requirements?

When resolving ambiguities in feature requirements, questions are formatted as either multiple-choice items or short-answer entries to target specific missing details and prepare updates for the document.