skills.rest
auleewilliams
auleewilliamsCOMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

Generate clarifying questions and update feature spec sections with answers.

Updated Nov 23, 2023
Search Tags:#planning#requirements#ambiguity#spec#update#clarify
One-click install
npx skills add https://github.com/auleewilliams/Skillscape --skill speckit-clarify-auleewilliams
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/auleewilliams/Skillscape/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/auleewilliams/Skillscape --skill speckit-clarify-auleewilliams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-clarify helps product teams identify underspecified areas in feature specs by generating up to 5 focused clarification questions and encoding the answers back into the spec.

Core Features & Use Cases

  • Up to 5 targeted clarification questions to surface ambiguities before planning
  • Inline updates to the spec with traceable decisions
  • Prioritized ambiguity risk with a structured progression to planning

Quick Start

Run the clarifications workflow on your active feature spec to surface and embed clarifications.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I clarify ambiguous requirements in a feature spec?▼

To clarify ambiguous requirements, generate up to 5 concise questions targeting underspecified areas. Answers are then encoded directly into the spec to ensure traceability and resolve ambiguity before planning.

What is the best way to update functional requirements after resolving spec ambiguities?▼

Updating functional requirements involves recording clarification answers back into the spec. Relevant sections including Data Model, User Interactions, and Non-functional criteria are updated to ensure decisions are testable and traceable.

How do I identify and resolve underspecified areas in my product spec?▼

Identifying underspecified areas uses a structured workflow that generates targeted clarification questions. Resolving them involves embedding the answers directly into the spec file for review and planning.

Does clarifying spec ambiguities help with testable and traceable requirements?▼

Clarifying spec ambiguities ensures requirements are testable and traceable. Generated clarifications are saved back into the spec file, prioritizing ambiguity risk and structuring the progression to planning.

When do I need to generate clarifying questions for a feature spec?▼

You need to generate clarifying questions for a feature spec when ambiguities surface before planning. This targets up to 5 underspecified areas, encoding traceable decisions inline to update the spec.

Can I use spec clarification for updating non-functional criteria?▼

Spec clarification can be used for updating non-functional criteria. The process resolves ambiguities and saves answers back into the spec, ensuring all functional and non-functional updates are testable.

Related Skills

Explore More Product & Management Skills→
GenerativeAgentsGenerativeAgents

prd-writing

Generate a review-ready PRD from initial-requirements.md using the PRD template.

Official
Advanced
cchrisvcchrisv

to-issues

Break development plans into dependency-aware implementation issues with acceptance criteria.

Community
Intermediate
jayteealaojayteealao

documentation-sync

Synchronize version numbers across project files and documentation references.

Community
Advanced
dawsonblockdawsonblock

doc-coauthoring

Manage collaborative document editing with version control, comment resolution, and merge strategies.

Community
Intermediate