skills.rest
180VRisLife
180VRisLifeCOMMUNITY
Explore all skills by this author →
GitHub

spec-clarify

Generate prioritized clarifying questions and encode answers into feature specs.

Updated Aug 23, 2026
Search Tags:#requirements#ambiguity#spec#questions#product-management#clarify
One-click install
npx skills add https://github.com/180VRisLife/.claude --skill spec-clarify-180vrislife
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-clarify
Source: https://github.com/180VRisLife/.claude/tree/main/skills/spc-clarify
Command: npx skills add https://github.com/180VRisLife/.claude --skill spec-clarify-180vrislife

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature spec and guide teams to resolve gaps by proposing up to 5 targeted clarification questions, encoding answers back into the spec.

Core Features & Use Cases

  • Detect ambiguous or missing aspects in the active feature spec and generate a prioritized list of clarifications.
  • Create or update a "## Clarifications" section in the spec with a dated session log, including Q&A pairs.
  • Help maintain consistency across related specs by cross-checking terminology and constraints when updating the spec.
  • Use cases: for a new feature, gather critical questions about scope, data model, UX, and acceptance criteria, then lock decisions in the spec.

Quick Start

Initiate clarification by generating up to five targeted questions for the active feature spec.

Frequently Asked Questions about spec-clarify

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

FAQPage Schema
How do I resolve ambiguity in a feature spec?▼

To resolve ambiguity in a feature spec, generate up to five targeted clarifying questions covering architecture, data modeling, UX, testing, and compliance, then encode the answers directly back into the spec.

What are the most critical requirements questions to ask for a new feature?▼

Critical requirements questions for a new feature target scope, data model, UX, and acceptance criteria to identify underspecified areas and lock decisions in the spec.

How do I document clarifications and Q&A sessions in a spec?▼

Document clarifications in a spec by adding a '## Clarifications' section with a dated '### Session YYYY-MM-DD' log, recording each resolved question and answer as Q: <question> -> A: <answer> entries.

What is the best way to find gaps in product management specifications?▼

The best way to find gaps in product management specifications is to cross-check terminology and constraints across related specs, producing a prioritized queue of questions that impact architecture and compliance.

How many clarifying questions should I generate for an active feature spec?▼

You should generate up to five clarifying questions for an active feature spec to effectively scope critical decisions without overwhelming the review process.

Does this spec clarification tool work with existing .spec directories?▼

Yes, this spec clarification tool works with existing .spec directories by navigating the structure, selecting the relevant feature, and updating the target file with resolved Q&A pairs.

Related Skills

Explore More Product & Management Skills→
usepowershellusepowershell
9

speckit-clarify

Scan feature specs for ambiguities and generate targeted clarification questions.

Community
Advanced
LISSConsultingLISSConsulting
1

speckit-clarify

Identifies gaps in project specs and generates clarifying questions for missing details.

Official
Advanced
deMGoncalvesdeMGoncalves
4

Documenter Skill

Update README, code comments, Arc42 specs, examples, and CHANGELOG after code changes.

Community
Intermediate
DiologIRDiologIR

triage

Triage feature ideas into structured spec documents with codebase grounding.

Official
Advanced