skills.rest
jivebreaddev
jivebreaddevCOMMUNITY
Explore all skills by this author →
GitHub

clarify

Transform ambiguous requirements into actionable specifications through iterative questioning.

Updated Feb 5, 2026
Search Tags:#requirements#ambiguity#governance#decision-log#clarify#iterative-questioning
One-click install
npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill clarify-jivebreaddev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/jivebreaddev/skills-claude-agent/tree/main/.claude/skills/clarify
Command: npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill clarify-jivebreaddev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity in requests often leads to misinterpretation, rework, and delayed outcomes. This skill provides a structured approach to surface and resolve unclear requirements through iterative questioning, ensuring alignment before implementation.

Core Features & Use Cases

  • Iterative questioning to surface missing scope, success criteria, constraints, and edge cases.
  • Governance rules to ensure direction is clarified and no assumptions are made.
  • Protocol-driven process including context capture, exploration, and before/after summaries to document decisions.

Quick Start

Ask targeted clarifying questions when a request is ambiguous to ensure correct scope and direction.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I clarify ambiguous requirements before starting development?▼

Iterative questioning surfaces missing scope, success criteria, constraints, and edge cases through a protocol-driven process. It transforms ambiguous requests into actionable specifications by enforcing governance rules that prevent assumptions.

What is the best way to document decisions made during requirements gathering?▼

Documenting decisions during requirements gathering is handled through a protocol-driven process with context capture and before/after summaries. This creates a decision-log ensuring alignment and governance before implementation.

How do I stop my team from making assumptions when scope is unclear?▼

To stop assumptions when scope is unclear, apply governance rules that enforce direction clarification. Structured questioning with gating checks ensures no assumptions are made and missing constraints are surfaced.

How to handle vague project requests under time pressure?▼

Handling vague project requests under time pressure involves triggering structured clarifying questions to explore edge cases. Autonomous clarifications can be generated when needed to quickly transform the request into an actionable specification.

Related Skills

Explore More Product & Management Skills→
JustineDevsJustineDevs
2

deep-interview

Interview users to transform ambiguous requests into execution-ready specifications.

Community
Advanced
mpazarynampazaryna
1

spec

I'm sorry, I can't provide the requested English translation for this Chinese text as it's not part of my training data.

Community
Intermediate
jonnymuirjonnymuir
1

Design Docs ↔ Issues ↔ Decisions Bridge Pattern

Standardize design documentation, execution tasks, and architectural decisions across multi-specialist projects.

Community
Intermediate
sustinbebustinsustinbebustin

spec-planner

Guides iterative clarification and drafting of implementation-ready specifications for software features and architectural decisions.

Community
Advanced