skills.rest
pgermishuys
pgermishuysCOMMUNITY
Explore all skills by this author →
Website𝕏@pgermishuysGitHub

sdd-clarify

Detect ambiguities in feature specifications and guide a structured clarifications workflow.

143|10|Updated Feb 24, 2026
Search Tags:#planning#specification#ambiguity#risk-management#product-management#questioning#clarifications
One-click install
npx skills add https://github.com/pgermishuys/opencode-weave --skill sdd-clarify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-clarify
Source: https://github.com/pgermishuys/opencode-weave/tree/main/examples/config/github-speckit/skills/sdd-clarify
Command: npx skills add https://github.com/pgermishuys/opencode-weave --skill sdd-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguities in feature specifications stall planning and introduce risk. This skill provides a structured taxonomy and a clarifications workflow to surface, prioritize, and resolve gaps.

Core Features & Use Cases

  • Ambiguity Taxonomy with 11 categories to classify spec gaps.
  • Prioritization heuristic for remediation work.
  • Structured questioning protocol to collect answers, with a maximum of five questions.
  • Spec update mechanism and inline documentation of clarifications.
  • Coverage reporting detailing resolved and deferred areas.
  • Useful in early-stage product planning, requirements refinement, and risk mitigation.

Quick Start

Start a guided clarifications session on the provided spec to surface ambiguities and generate a prioritized Q&A plan.

Frequently Asked Questions about sdd-clarify

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

FAQPage Schema
How do I detect ambiguities in a feature specification?▼

Ambiguity detection in a feature specification involves classifying spec gaps across functional scope, domain, data, UX, constraints, and integrations using an 11-category taxonomy, then applying a scoring heuristic to prioritize remediation.

What is the best way to structure clarifying questions for product requirements?▼

Structuring clarifying questions for product requirements is best done using a constrained questioning protocol that limits inquiries to a maximum of five prioritized questions, ensuring focused and traceable resolution of specification ambiguities.

How does a structured questioning protocol manage risk in early-stage product planning?▼

A structured questioning protocol manages risk in early-stage product planning by surfacing specification gaps, prioritizing them via a scoring heuristic, and documenting inline spec updates to ensure traceable decisions and reduce planning delays.

Can I generate coverage reports for resolved and deferred specification gaps?▼

Yes, you can generate coverage reports detailing resolved and deferred specification areas, providing a workflow that ensures traceable decisions and tracks the status of ambiguities found during early-stage spec reviews.

Does this ambiguity taxonomy approach apply to early-stage spec reviews for risk mitigation?▼

Yes, the ambiguity taxonomy approach applies directly to early-stage spec reviews for risk mitigation, scanning functional scope, domain, data, UX, constraints, and integrations to surface and resolve specification gaps.

Related Skills

Explore More Product & Management Skills→
prof-danielcprof-danielc

speckit.clarify

Identify and resolve ambiguities in feature specifications by asking targeted questions.

Community
Intermediate
OpenLaborOpenLabor
4

Sprint Planning

Plan development sprints with velocity-based scope and blocker tracking.

Official
Intermediate
ncptuanncptuan

bmad-edit-prd

Edit existing product requirements documents through a structured discovery, review, planning, and update workflow.

Community
Advanced
nocnocgroupnocnocgroup

plan-ceo-review

Analyze strategic product plans to surface risks, gaps, and expansion options.

Official
Advanced