clarify

Audits a spec.md or slice file for ambiguities across six defined categories and generates prioritized questions.

5|Updated May 12, 2026

Search Tags:#workflow #documentation #qa #ambiguity #spec #frontmatter #clarify

Ready to run

npx skills add https://github.com/ramboz/jig --skill clarify-ramboz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguities in a Jig spec slow teams and introduce risk; this skill provides a lightweight, repeatable ambiguity audit that surfaces gaps before reviews.

Core Features & Use Cases

Six-category ambiguity audit aligned with Jig's slice template (Scope & Boundaries, Acceptance Criteria Testability, Dependencies & Blockers, Non-functional Requirements, Edge Cases & Failure Modes, Terminology Consistency).
Up to five prioritized questions written verbatim and appended to a Clarifications section with a coverage summary for audit traceability.
Standalone baseline that can run on a single draft spec (spec.md) or a single slice file, enabling pre-review clarification without deferring to other workflow steps.

Quick Start

Run clarify on a draft spec to surface ambiguities and append a Clarifications section.

Frequently Asked Questions about clarify

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

FAQPage Schema

How do I identify ambiguities in a draft spec before review?▼

To identify ambiguities in a draft spec before review, run a structured six-category audit that analyzes the document and generates prioritized questions to append to a Clarifications section.

What categories should a spec ambiguity audit cover?▼

A spec ambiguity audit should cover Scope & Boundaries, Acceptance Criteria Testability, Dependencies & Blockers, Non-functional Requirements, Edge Cases & Failure Modes, and Terminology Consistency.

Can I run an ambiguity scanner on a single slice file independently?▼

Yes, you can run an ambiguity scanner on a single slice file independently. The standalone baseline processes one document at a time without deferring to other workflow steps.

How many clarification questions are generated for a spec audit?▼

A spec audit generates up to five prioritized questions written verbatim. These questions are appended to a Clarifications section alongside a coverage summary for audit traceability.

What is the best way to track spec readiness across cross-skill workflows?▼

The best way to track spec readiness across cross-skill workflows is to use a coverage summary with Clear, Partial, or Missing ratings to guide Ready-for-Review decisions and output a Q&A trace.

Does Jig spec clarification require external workflow dependencies?▼

Jig spec clarification does not require external workflow dependencies. The audit operates as a standalone baseline to surface gaps and append clarifications directly to the document.