dig

Generates clarifying questions to identify ambiguities in design and project plans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sendo-kakeru/family-photo --skill dig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dig
Source: https://github.com/sendo-kakeru/family-photo/tree/main/.claude/skills/dig
Command: npx skills add https://github.com/sendo-kakeru/family-photo --skill dig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams turn vague plans into clear, actionable requirements by generating structured questions that uncover gaps and ambiguities. It drives thorough, collaborative planning and reduces miscommunication.

Core Features & Use Cases

  • Structured questioning: systematically identifies uncertainties in product specs, technical details, and UI/UX plans.
  • Iterative refinement: guides through multiple rounds of questions until all critical points are resolved.
  • Decision documentation: outputs concrete decisions and missing items ready for inclusion in plan files.

Quick Start

Provide the current plan or requirements document and ask the system to start a targeted interview to surface ambiguities.

Frequently Asked Questions about dig

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

FAQPage Schema
How do I clarify ambiguous product specifications and uncover missing requirements?

Structured requirement clarification works by generating targeted questions that systematically identify uncertainties in product specs, technical details, and UI/UX plans to uncover hidden gaps before development begins.

What is the best way to conduct a targeted interview for plan clarification?

The best way to conduct a targeted interview for plan clarification is to apply iterative questioning, guiding through multiple rounds of structured questions until all critical missing items and ambiguities are fully resolved.

Does structured requirement clarification work for UI/UX plans and technical details?

Yes, structured requirement clarification works for UI/UX plans and technical details by systematically identifying uncertainties across various plan documents and generating targeted questions to extract the missing information.

How do I document decisions and missing items after a requirements interview?

To document decisions after a requirements interview, the system outputs concrete finalized decisions and identified missing items that are ready for direct inclusion in your product specification and plan files.

When should I use iterative questioning for product management planning?

You should use iterative questioning for product management planning when you have a vague plan that needs to be turned into clear, actionable requirements, helping drive thorough collaborative planning and reduce team miscommunication.