skills.rest
yangsi7
yangsi7COMMUNITY
Explore all skills by this author →
GitHub

Specification Clarification

Identify and resolve specification ambiguities through structured questioning.

1|Updated Oct 24, 2025
Search Tags:#documentation#specification#requirements#clarification#ambiguity resolution#product definition#user stories
One-click install
npx skills add https://github.com/yangsi7/skill-builder --skill specification-clarification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Specification Clarification
Source: https://github.com/yangsi7/skill-builder/tree/main/.claude/skills/clarify-specification
Command: npx skills add https://github.com/yangsi7/skill-builder --skill specification-clarification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Read, Write, Edit, project-intel.mjs, and includes examples (resource) and references (resource) and workflows (resource) components.

What problem does it solve?

This Skill eliminates ambiguous or incomplete specifications that lead to misinterpretations, rework, and delays during development. It systematically resolves unknowns before implementation begins, ensuring clarity and alignment.

Core Features & Use Cases

  • Systematic Ambiguity Detection: Scans specifications against 10+ categories (e.g., functional scope, edge cases, non-functional requirements) to identify gaps.
  • Prioritized, Structured Questioning: Generates up to 5 high-impact questions per iteration, with options and recommendations, to guide the user to clear answers.
  • Incremental Specification Updates: Updates the spec.md file after each answer, ensuring consistency and preventing contradictions.
  • Use Case: Your feature specification has [NEEDS CLARIFICATION] markers or feels vague. Use this Skill to engage in a focused dialogue, resolve all ambiguities, and refine your spec.md into a clear, actionable document, ready for planning.

Quick Start

To clarify an existing specification with ambiguities:

Ensure your spec.md is in specs/<feature-id>/spec.md

Then, simply invoke the skill:

/clarify specs/my-feature/spec.md

Frequently Asked Questions about Specification Clarification

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

FAQPage Schema
How do I resolve ambiguities in my product specification before development starts?▼

Specification clarification systematically identifies gaps across functional scope, edge cases, and non-functional requirements, then guides you through structured questioning to resolve each ambiguity. Load your spec.md, and the Skill prioritizes unclear areas, generates up to 5 high-impact questions per iteration, and incrementally updates your document after each answer to ensure consistency before implementation begins.

What should I do when my specification has [NEEDS CLARIFICATION] markers?▼

Invoke the Skill against your spec.md to enter a focused dialogue that eliminates vague requirements. The Skill detects ambiguities, asks prioritized questions with options, records your answers, and updates the specification incrementally, preventing contradictions and ensuring your document is actionable and ready for planning.

Can I clarify requirements incrementally rather than all at once?▼

Yes. Specification clarification enforces a phased process: load your spec, prioritize ambiguities by impact, ask up to five questions per iteration, update the spec after each answer, and validate for contradictions. This incremental approach lets you resolve the highest-impact unknowns first and refine iteratively until clarity is complete.

How do I detect what's missing from my specification?▼

The Skill scans specifications against 10+ ambiguity categories—functional scope, edge cases, non-functional requirements, and others—to surface gaps systematically. Rather than manual review, it identifies which areas need clarification and prioritizes them so you address the most impactful unknowns first.

What file format and structure does this Skill work with?▼

Specification clarification operates on spec.md files located in specs/<feature-id>/spec.md. It reads and edits your Markdown specification directly, updating it with clarified requirements after each Q&A cycle while tracking contradictions to maintain consistency throughout the document.

Does this approach work for user stories and requirements documents?▼

Yes. The Skill is designed for any specification containing unclear requirements—feature specs, user stories, and requirements documents all benefit. It applies the same systematic ambiguity detection and prioritized questioning to any product definition document to eliminate vagueness before implementation.

Related Skills

Explore More Product & Management Skills→
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
gmliaogmliao
1

specify

Create structured feature specs with user stories and acceptance criteria.

Community
Basic
eternnoireternnoir
6

update-content

Update knowledge base files while preserving frontmatter and markdown structure.

Community
Basic
v1bh0rv1bh0r

nw-po-review-dimensions

Evaluate requirements documents against five quality dimensions and produce YAML feedback.

Community
Advanced