Identify ambiguities in requirements, architecture, and design with structured questions.
npx skills add https://github.com/mei28/dotfiles --skill dig-mei28
Please help me install this Agent Skill. Skill: dig Source: https://github.com/mei28/dotfiles/tree/main/.claude/skills/dig Command: npx skills add https://github.com/mei28/dotfiles --skill dig-mei28
Ambiguities in requirements, architecture, and design can stall projects. This tool guides teams to surface and resolve gaps through structured questions across categories, helping ensure a clear plan before coding begins.
Run the dig analysis to identify ambiguities in your project requirements.
High-intent search queries and answers about installing and using this skill.
Identifying ambiguities requires generating targeted questions across architecture, data, API, UI/UX, testing, security, and deployment categories to resolve vague specs and reach stakeholder alignment before project planning.
Clarifying vague requirements involves loading project context files and producing organized questions across categories like architecture and security to ensure a clear plan before development starts.
You align stakeholders by generating structured questions across deployment, data management, and security categories, producing recommendations that resolve vague specifications and establish a clear project scope.
Loading project context files allows the structured questioning process to read existing standards, ensuring the generated architecture and API questions align with your current conventions before planning begins.
You should evaluate categories including Architecture & Design, Data & State Management, API & Integration, UI/UX, Testing & Quality, Security & Authorization, Performance & Scalability, and Deployment & Operations to resolve ambiguities.
Structured questioning is needed when handling new feature requests or complex projects with vague specs, as it surfaces gaps across categories like security and performance to establish scope before planning.
devstefanchoOrganize spec files under specs/{scope}/{work-name}.md with XML tag enforcement.
henrique-simoesAutomates workshop planning and synthesizes outputs into scored, referenced findings.
norbert-papAutomate structured engineering plan reviews covering architecture, data flow, and risks.
yuchenbigpen1Guide structured depth-first questioning to surface requirements and constraints.
