Convert ambiguous implementation plans into structured questions with options.
npx skills add https://github.com/rioX432/live-translate --skill dig-riox432
Please help me install this Agent Skill. Skill: dig Source: https://github.com/rioX432/live-translate/tree/main/.claude/skills/dig Command: npx skills add https://github.com/rioX432/live-translate --skill dig-riox432
This Skill removes uncertainty from plans before implementation by identifying unclear decisions, turning them into structured questions, and selecting safe defaults when project patterns are clear.
Ask the dig skill to review the plan, identify ambiguities, and return structured questions with recommended decisions.
High-intent search queries and answers about installing and using this skill.
To resolve ambiguity in a software architecture plan, you can extract unclear decision points and turn them into structured questions with options and safe defaults. This narrows unresolved trade-offs before implementation begins.
The best way to decide on API design and error handling choices is to review existing codebase patterns and project conventions. This allows you to auto-decide safe defaults and surface only unresolved structural trade-offs for review.
You identify decision points for concurrency and testing scope by analyzing the plan against architecture, data flow, and testing requirements. Unclear choices are extracted and presented as concise options with recommendations.
Yes, you can use project conventions to auto-decide naming and data flow decisions. When existing codebase patterns are clear, straightforward choices are resolved automatically without user back-and-forth.
Yes, this approach works for any codebase by applying project conventions and existing patterns to resolve straightforward choices. It only surfaces unresolved trade-offs in error handling and architecture as structured options.
You should not rely on auto-deciding safe defaults when project conventions are unclear or existing codebase patterns do not provide a clear direction. In these cases, unresolved API design and concurrency trade-offs require structured manual review.
babuallyInterrogate plans and designs to expose missing assumptions and weak decision points.
kartikkabadiChallenge proposed plans against codebase language and documented decisions.
I2olanDAnalyze repository structure to detect naming, architecture, and testing patterns.
jungmini0601Plan technical implementations and design system architectures with roadmaps.
