dig
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Clarify ambiguities in plans with structured questions and auto-decide rules
7 other projects use a version of this.
Adopted by
Most recently taken up by
- crsmithdev/alephtheir own version, first seen Nov 16, 2026
- apify/apify-mcp-servertheir own version, first seen Nov 12, 2026
- uwonu606/claude-skillstheir own version, first seen Nov 1, 2026
- WeAIClub/resume-skillstheir own version, first seen Oct 25, 2026
- l3rowniecakez/Claude_Skilltheir own version, first seen Oct 19, 2026
- tim-mcdonnell/skillstheir own version, first seen Jul 29, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- apify/apify-mcp-server★ 16ksame name
- Soul-Brews-Studio/arra-oracle-skills-cli★ 121same name
- WeAIClub/resume-skills★ 4same name
- crsmithdev/aleph★ 0same name
- l3rowniecakez/Claude_Skill★ 0same name
- tim-mcdonnell/skills★ 0same name
- uwonu606/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- auditSkill
- decomposeSkill
- dev-allSkill
- dev-investigateSkill
- devSkill
- investigateSkill
- prSkill
- reviewSkill
- tech-debtSkill
- update-docsSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
After investigation is complete but before decomposition
- Distinctive: line 16
When there are design choices, trade-offs, or unclear requirements
- Distinctive: line 17
When the approach could go multiple valid directions
- Distinctive: line 34
Check if CLAUDE.md or rules/ explicitly defines a convention for this decision
- Distinctive: line 35
Check if the codebase has an established pattern (Grep for similar implementations)
- Distinctive: line 36
If a clear, consistent pattern exists → auto-decide and record the rule
- Distinctive: line 44
Naming: Follow project naming conventions (Check CLAUDE.md or rules/)
- Distinctive: line 50
Use Explore agent to find existing patterns in the codebase
- Distinctive: line 51
Check if similar features already exist and how they handle the same decision
- Distinctive: line 52
Read relevant documentation or ADRs
- Very specific: line 90
If ToolSearch fails to find Codex or the call errors:
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dig — Structured Ambiguity Resolution
Resolve ambiguities before implementation by generating structured questions with options. Auto-decides choices that follow established project patterns.
When to Use
- After investigation is complete but before decomposition
- When there are design choices, trade-offs, or unclear requirements
- When the approach could go multiple valid directions
Process
Step 1: Extract Ambiguities
From the investigation results, identify every decision point:
| # | Ambiguity | Category | Auto-decidable? |
| 1 | ... | architecture / api-design / data-flow / concurrency / error-handling / naming / testing | yes/no |
Step 2: Apply Auto-Decide Rules
For auto-decidable ambiguities, check the project's CLAUDE.md, rules/*.md, and existing codebase patterns to determine the answer.
How to auto-decide:
- Check if CLAUDE.md or rules/ explicitly defines a convention for this decision
- Check if the codebase has an established pattern (Grep for similar implementations)
- If a clear, consistent pattern exists → auto-decide and record the rule
Common decision categories:
- Architecture: Where does this code belong? (Check CLAUDE.md architecture section)
- API Design: Public or internal? What return type? (Check existing public API patterns)
- Data Flow: Sync or async? Callback or stream? (Check established patterns)
- Concurrency: Thread safety approach? (Check existing locking/synchronization patterns)
- Error Handling: Exception, Result type, or null? (Check existing error patterns)
- Naming: Follow project naming conventions (Check CLAUDE.md or rules/)
- Testing: Unit, integration, or both? (Check existing test patterns)
Step 3: Investigate Remaining Unknowns
For non-auto-decidable ambiguities:
- Use Explore agent to find existing patterns in the codebase
- Check if similar features already exist and how they handle the same decision
- Read relevant documentation or ADRs
Step 3.5: Codex Design Review (Optional)
For non-auto-decidable ambiguities in the architecture, api-design, or concurrency categories, consult Codex for alternative approaches before asking the user.
Skip this step for: naming, testing, error-handling, data-flow categories (these are resolved by codebase patterns or user preference).
Load Codex
ToolSearch("select:mcp__codex__codex")Call Codex (if available)
mcp__codex__codex(
prompt: "Given these unresolved design decisions, explore alternatives:
## Ambiguities
{list of non-auto-decidable architecture/api-design/concurrency ambiguities with their options}
## Codebase Context
{relevant patterns from Step 2, existing conventions}
For each ambiguity:
1. Evaluate the proposed options
2. Suggest any additional alternatives not yet considered
3. Recommend the best option with reasoning
4. Flag any risks or trade-offs"
)Incorporate Codex recommendations into the options presented to the user in Step 4.
Fallback (Codex unavailable)
If ToolSearch fails to find Codex or the call errors:
- Skip this step — proceed to Step 4 with Step 3 results only (traditional flow)
Step 4: Ask User (max 3 rounds, max 4 questions per round)
Present remaining unknowns with AskUserQuestion:
- Context from investigation
- 2-4 concrete options with trade-offs
- Recommend the option matching existing codebase patterns
Step 5: Output Decision Matrix
## Dig Results: {requirement}
### Auto-Decided
| # | Decision | Rule | Result |
|---|----------|------|--------|
| 1 | Where to place X | CLAUDE.md: "feature code in src/features/" | src/features/x/ |
### Investigated
| # | Decision | Finding | Result |
|---|----------|---------|--------|
| 2 | Error handling approach | Existing pattern in src/api/client.kt uses Result<T> | Result<T> |
### User-Decided
| # | Decision | Choice | Reason |
|---|----------|--------|--------|
| 3 | Public API surface | Option A: minimal | user preference |
### Assumptions (if any)
| # | Assumption | Risk |
|---|-----------|------|Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

