clarification-analyst

Identify ambiguities, missing edge cases, and hidden assumptions in PRDs and specifications.

55|11|Updated Dec 11, 2025

Search Tags:#clarification #requirements engineering #product requirements #systematic analysis #technical specifications

Ready to run

npx skills add https://github.com/GulajavaMinistudio/awesome-copilot-id --skill clarification-analyst

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarification-analyst
Source: https://github.com/GulajavaMinistudio/awesome-copilot-id/tree/main/.opencode/skills/clarification-analyst
Command: npx skills add https://github.com/GulajavaMinistudio/awesome-copilot-id --skill clarification-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps identify ambiguities, missing edge cases, and hidden assumptions in Product Requirements (PRD), Technical Specifications, and Implementation Plans, ensuring a clear foundation for the next SDLC phase.

Core Features & Use Cases

Systematic Clarification: Analyzes documents for ambiguities, negative conditions, hidden dependencies, and code contradictions.
Question Formulation: Formulates sharp, actionable questions to deepen understanding and resolve issues.
Iterative Interrogation: Engages in an iterative process of clarification, reporting, and artifact generation.
Use Case: Before starting development on a new feature, use this Skill to review the PRD to ensure no critical assumptions are overlooked.

Quick Start

Use the clarification-analyst skill to analyze the PRD for the new feature 'Feature X' and identify any ambiguities.

Frequently Asked Questions about clarification-analyst

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

FAQPage Schema

How do I identify ambiguities and missing edge cases in a PRD?▼

To identify ambiguities and missing edge cases in a PRD, you need systematic clarification to analyze documents for negative conditions, hidden dependencies, and code contradictions. This process ensures a clear foundation for the next SDLC phase.

What is systematic clarification for technical specifications?▼

Systematic clarification for technical specifications is an iterative interrogation process that formulates sharp, actionable questions to resolve hidden assumptions. It deepens requirements understanding by reporting issues and generating artifacts for enhanced clarity.

How do I check technical specifications for hidden dependencies before development?▼

To check technical specifications for hidden dependencies before development, analyze the documents for negative conditions and code contradictions. Formulating sharp questions during this stage ensures no critical assumptions are overlooked before starting the next SDLC phase.

Can I use systematic analysis to review implementation plans for missing conditions?▼

Yes, you can use systematic analysis to review implementation plans for missing conditions. It analyzes the plans to expose hidden assumptions and ambiguities, formulating actionable questions to deepen understanding and resolve potential issues.

What is the best way to formulate actionable questions from product requirements?▼

The best way to formulate actionable questions from product requirements is through iterative interrogation. This approach systematically targets ambiguities and hidden assumptions, generating clear artifacts that deepen requirements understanding.