reversa-clarify

Generate up to five clarifying questions and merge answers into requirements.md.

Updated Nov 4, 2025

Search Tags:#planning #requirements #product-management #stakeholders #clarify #requirements-management

Ready to run

npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-clarify-markson22

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate up to five targeted clarifying questions to resolve ambiguities in feature requirements, integrating answers back into the active requirements document.

Core Features & Use Cases

Generate up to five clarifying questions directed at resolving missing details in requirements.
Merge user responses into the feature's requirements.md to maintain a single source of truth.
Acts as an optional step in the forward planning cycle between /reversa-requirements and /reversa-plan to tighten scope before planning.

Quick Start

Run /reversa-clarify to generate up to five targeted questions that resolve missing information and merge answers into the active feature's 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 requirements to resolve ambiguities before product planning?▼

To clarify requirements, you generate up to five targeted questions that resolve missing details and merge the answers back into the active feature requirements document to maintain a single source of truth.

What is the best way to manage unresolved gaps in feature requirements?▼

The best way to manage unresolved gaps in feature requirements is by tracking them during the clarification cycle and merging resolved answers into the requirements.md file.

How do I generate clarifying questions for stakeholders to tighten scope?▼

You generate clarifying questions for stakeholders by running an automated clarification step that produces a maximum of five targeted inquiries to resolve missing information before planning.

Does this requirements clarification tool limit the number of questions asked?▼

Yes, this requirements clarification tool enforces a maximum of five targeted questions to ensure focused stakeholder communication and prevent scope creep during the forward planning cycle.

Can I merge stakeholder responses directly into my requirements document?▼

You can merge stakeholder responses directly into your requirements document by integrating the answers back into the active feature's requirements.md file to maintain a single source of truth.

When do I need to use a clarification step in the product management cycle?▼

You need a clarification step in the product management cycle when moving between requirements gathering and planning, serving as an optional process to tighten scope and resolve ambiguities before finalizing plans.