clarify

Ask structured clarifying questions to resolve ambiguities before task execution.

2|Updated Jul 11, 2024
One-click install
npx skills add https://github.com/nicograef/handbook --skill clarify-nicograef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/nicograef/handbook/tree/main/.claude/skills/clarify
Command: npx skills add https://github.com/nicograef/handbook --skill clarify-nicograef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents the agent from acting on ambiguous or underspecified instructions by forcing a structured, logical discovery process before execution.

Core Features & Use Cases

  • Structured Questioning: Uses a canonical decision-tree approach to resolve unknowns, edge cases, and conflicting constraints.
  • Assumption Documentation: Ensures that if a user forces an action despite ambiguity, all assumptions are explicitly recorded for transparency.
  • Use Case: When a user provides a vague request like "update the server," this skill forces the agent to ask for specific environment details and maintenance windows before attempting any changes.

Quick Start

Activate the clarify skill to analyze the current task and identify any missing information or ambiguities before proceeding.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I resolve ambiguities in software requirements before task execution?

Resolving ambiguities in software requirements requires structured clarifying questions that eliminate unknowns before execution. This approach uses a canonical decision-tree method to identify missing information, edge cases, and conflicting constraints, ensuring high-precision outcomes.

What's the best way to stop an AI agent from making assumptions on vague requests?

To stop an AI agent from making assumptions on vague requests, force a logical discovery process that requires structured questioning. This prevents acting on underspecified instructions and explicitly documents any remaining assumptions for transparency if execution is forced.

How does structured disambiguation improve decision-making for complex planning?

Structured disambiguation improves decision-making by forcing a thorough spec-gathering process that resolves unknowns and conflicting constraints. It replaces assumptive behavior with documented decisions, creating a transparent foundation for complex planning and logic.

When do I need structured clarification for software engineering tasks?

You need structured clarification for software engineering tasks when instructions are ambiguous or underspecified, such as receiving a request to update a server without environment details. It ensures critical maintenance windows and constraints are identified before changes occur.

Can I force task execution even if the disambiguation process finds missing information?

You can force task execution even if the disambiguation process finds missing information, but all critical assumptions will be explicitly recorded. This documentation ensures transparency and maintains a record of decisions made despite unresolved ambiguities in the requirements.