clarify

Name: clarify
Availability: InStock
Author: lionbenjamin

Review feature specifications for clarity, completeness, and edge cases.

15|6|Updated Jan 5, 2026

Search Tags:#requirements #review #edge-cases #ux #acceptance-criteria #clarify #product-spec

Ready to run

npx skills add https://github.com/lionbenjamin/agent-templates --skill clarify-lionbenjamin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/lionbenjamin/agent-templates/tree/main/skills/clarify
Command: npx skills add https://github.com/lionbenjamin/agent-templates --skill clarify-lionbenjamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review the current feature specification for product clarity, completeness, and edge cases. Product-focused only — no technical or implementation questions.

Core Features & Use Cases

Identify ambiguities and gaps in user-facing specs
Generate concrete recommendations and a formal clarification-review.md
Produce a verdict of APPROVED or NEEDS REVISION in the review file

Quick Start

Provide the path to the spec directory to generate a clarification-review.md alongside the specification.

Frequently Asked Questions about clarify

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

FAQPage Schema

How do I review a product spec for missing edge cases and ambiguities?▼

A specification review identifies ambiguities, missing user flows, and inconsistent acceptance criteria across teams. It generates a clarification-review.md file next to your spec, containing identified gaps, concrete recommendations, and a final APPROVED or NEEDS REVISION verdict.

What is the best way to improve acceptance criteria clarity before development?▼

Improving acceptance criteria clarity involves reviewing feature specifications to surface ambiguities and gaps in user-facing specs. The process produces a formal review document with concrete recommendations and a verdict to ensure your product spec is complete before development begins.

How do I generate a review report for my feature specification?▼

You generate a specification review report by providing the path to your spec directory. The review process automatically creates a clarification-review.md file alongside your specification, detailing identified gaps, recommendations, and an APPROVED or NEEDS REVISION verdict.

Does the specification review cover technical implementation questions?▼

No, the specification review does not cover technical implementation questions. It is strictly product-focused, meaning it only evaluates product clarity, completeness, edge-case coverage, UX flows, and acceptance criteria without addressing technical or implementation details.

Can I use this to check if my product spec is ready for team handoff?▼

Yes, you can verify if your product spec is ready for team handoff. The review evaluates completeness and edge-case coverage across teams, outputting a formal verdict of either APPROVED or NEEDS REVISION to confirm whether your specification meets clarity standards.