my-clarify

Identify ambiguities and unstated assumptions in specs and research documents.

4|1|Updated May 31, 2015

Search Tags:#planning #specification #requirements #clarification #ambiguity #risk-analysis

Ready to run

npx skills add https://github.com/samcdavid/dotfiles --skill my-clarify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: my-clarify
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/my-clarify
Command: npx skills add https://github.com/samcdavid/dotfiles --skill my-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically surface ambiguities, unstated assumptions, and underspecified areas in specs or research documents before downstream work begins. Acts as a second-pass quality gate between authoring and planning.

Core Features & Use Cases

Identify vague, unstated, or contradictory requirements in specifications or research papers.
Produce a structured list of issues for the author to resolve, enabling safer and faster planning.
Cross-document analysis to surface inconsistencies and missing context before downstream work.

Quick Start

Provide the document to analyze and I will surface ambiguities as a structured clarifications report.

Frequently Asked Questions about my-clarify

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

FAQPage Schema

How do I identify ambiguities and unstated assumptions in technical specifications?▼

To identify ambiguities in technical specifications, provide the document for analysis to surface vaguely defined, unstated, or contradictory requirements. This produces a structured clarifications report with categorized issues and suggested decisions for the author to resolve before planning begins.

What is specification clarification and when do I need it?▼

Specification clarification is a second-pass quality gate that detects underspecified areas in research documents or planning materials. You need it before downstream work begins to prevent misinterpretations, acting as a structured checkpoint between authoring and active project planning.

How do I resolve underspecified requirements before project planning?▼

To resolve underspecified requirements before planning, analyze the document to surface missing context and inconsistencies. This generates a structured clarifications report containing categorized issues and suggested decisions, enabling safer and faster planning by addressing risks upstream.

Can I use this to check research reports for missing context and inconsistencies?▼

Yes, you can analyze research reports to perform cross-document analysis that surfaces inconsistencies and missing context. This identifies underspecified areas within the research materials, outputting a structured list of issues for the author to resolve before downstream interpretation.

Does this tool support risk-analysis for vague or contradictory requirements?▼

Yes, it supports risk-analysis by systematically surfacing vague or contradictory requirements in specifications. It outputs a structured clarifications report with clearly categorized issues and suggested decisions, mitigating the risk of downstream misinterpretations during execution.