skills.rest
B4san
B4sanCOMMUNITY
Explore all skills by this author →
GitHub

spec_clarification

Identify and resolve ambiguities in feature specifications through targeted clarification questions.

Updated Feb 19, 2026
Search Tags:#documentation#specification#requirements#product management#clarification#ambiguity
One-click install
npx skills add https://github.com/B4san/Calix-Pass --skill spec-clarification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec_clarification
Source: https://github.com/B4san/Calix-Pass/tree/main/.gemini/skills/spec-clarification
Command: npx skills add https://github.com/B4san/Calix-Pass --skill spec-clarification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses ambiguity and missing information in feature specifications, ensuring clarity before implementation begins.

Core Features & Use Cases

  • Ambiguity Detection: Scans specifications for unclear or incomplete sections.
  • Targeted Question Generation: Creates concise, actionable questions to resolve ambiguities.
  • Interactive Resolution: Guides users through answering questions with multiple-choice or short-answer formats.
  • Use Case: A product manager is finalizing a spec for a new feature. This Skill helps identify areas needing more detail, like specific user interaction flows or data validation rules, before handing off to engineering.

Quick Start

Use the spec_clarification skill to identify and resolve ambiguities in the attached specification document.

Frequently Asked Questions about spec_clarification

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

FAQPage Schema
How do I identify and resolve ambiguities in a feature specification?▼

To resolve ambiguities in a feature specification, the Skill scans attached documents for unclear sections and generates targeted, actionable questions to iteratively refine functional scope, data models, and interaction flows.

What is the best way to clarify missing information in product requirements documentation?▼

Clarifying missing information in product requirements involves an interactive resolution process, guiding users through multiple-choice or short-answer questions to define precise, actionable specifications before engineering handoff.

How do I refine functional scope and data models before engineering handoff?▼

You refine functional scope and data models by applying an iterative questioning process to your spec, ensuring all interaction flows and validation rules are explicitly defined prior to implementation.

Can I use this to check if my specification is ready for product development workflows?▼

Yes, it applies directly to product development workflows by scanning your specification document to detect incomplete sections and ensure clear, actionable requirements are defined before implementation begins.

What are the limitations of using automated questioning for specification clarification?▼

Automated specification clarification relies entirely on the provided document's content; it cannot infer external business logic or unstated user needs beyond the boundaries of the attached specification text.

Related Skills

Explore More Product & Management Skills→
ch-yang1273ch-yang1273

speckit-clarify

Scan feature specifications for ambiguities and record clarifications in a session log.

Community
Advanced
tkstangtkstang

oat-project-spec

Formalize project discovery into a structured specification document with requirements and acceptance criteria.

Community
Advanced
bacchus-labsbacchus-labs
4

refining-specifications

Scan specifications against a taxonomy for ambiguity and coverage gaps.

Official
Intermediate
Prat011Prat011
1.5k

notion-spec-to-implementation

Convert Notion specs into implementation plans with tasks and milestones.

Community
Advanced