secondsky/claude-skills / plugins/unknowns-discovery/skills/unknowns-discovery
unknowns-discovery
VerifiedDiscover and reduce task unknowns — blindspots, missing context, and unknown unknowns — before committing to a plan, implementation, review, or merge.
assets/templates/unknowns-matrix.md
View on GitHub# Unknowns Matrix: [Task]
## Task map
- User goal:
- User starting point / familiarity:
- Territory to inspect:
- Constraints already known:
## Known knowns
| Fact / requirement | Source | Must preserve? |
|---|---|---:|
| | | |
## Known unknowns
| Question | Why it matters | Resolution path | Owner | Needed before implementation? |
|---|---|---|---|---:|
| | | | | |
## Unknown knowns
| Tacit criterion | Artifact to reveal it | Feedback needed |
|---|---|---|
| | | |
## Unknown unknown candidates
| Area | Why hidden risk may exist | Discovery method | Severity guess |
|---|---|---|---|
| Code/history | Prior failed/reverted attempts may exist | Search PRs/commits/issues | |
| Auth/permissions | Invisible security assumptions may exist | Inspect middleware/tests/policies | |
| Data model | Legacy rows/migrations may violate assumptions | Inspect migrations/fixtures/prod notes | |
| UX/taste | User may know it only when shown | Prototype/mock directions | |
| Stakeholders | Reviewers may raise objections late | Buy-in doc / sign-off map | |
## Highest-blast-radius unknown
[One sentence]
## Recommended artifact mode
[blindspot-pass / teach-me-my-unknowns / brainstorm-prototype / mock-before-wire / option-space-brainstorm / one-question-interview / reference-semantics-map / tweakable-plan / implementation-notes / buy-in-doc / merge-readiness-quiz]
## Stop conditions
- [security/data-loss/migration/API/compliance/billing condition]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |