Skip to content

secondsky/claude-skills / plugins/unknowns-discovery/skills/unknowns-discovery

unknowns-discovery

Verified

Discover and reduce task unknowns — blindspots, missing context, and unknown unknowns — before committing to a plan, implementation, review, or merge.

references/OUTPUT_SCHEMAS.md

View on GitHub
# Output Schemas

## Unknowns matrix

```markdown
# Unknowns Matrix: [Task]

## Known knowns
- [Explicit fact/requirement]

## Known unknowns
| Question | Why it matters | Resolution path | Owner |
|---|---|---|---|

## Unknown knowns
| Tacit criterion | Artifact to reveal it | Feedback needed |
|---|---|---|

## Unknown unknown candidates
| Area | Why hidden risk may exist | Discovery method |
|---|---|---|

## Highest-blast-radius unknown
[One sentence]

## Recommended artifact mode
[blindspot-pass / prototype / interview / etc.]
```

## Blindspot card

```markdown
## Blindspot [n]: [Name]
- Type: [landmine / convention / prior failed attempt / missing concept / hidden dependency]
- Severity: [low / medium / high / critical]
- Evidence inspected: [files/docs/commits/tests]
- Map assumption: [what the prompt implied]
- Territory revealed: [constraint]
- Why it bites: [failure mode]
- Conservative instruction: [what to do if proceeding]
- Prompt upgrade sentence: [copyable sentence]
- Stop condition: [when to pause]
```

## Tweakable plan

```markdown
# Tweakable Plan: [Task]

## Summary
- Effort:
- Files touched:
- Risk:
- Migration/API/user-facing changes:

## A. Decisions you may want to change
| Decision | Default | Alternative | Tradeoff | One-line override |
|---|---|---|---|---|

## B. Execution order
1. [step]
2. [step]

## C. Mechanical work I will handle
- [refactor/plumbing]

## Approval gate
[What the user must approve before implementation]
```

## Implementation notes

```markdown
# Implementation Notes: [Task]

## Summary counters
- Entries:
- Deviations:
- Needs human judgment:

## Log

### [time] Plan-confirmed: [Step]
[What matched the plan]

### [time] Deviation: [Name]
- What the plan said:
- What the code revealed:
- Conservative choice:
- Revisit:

## Fold back into next attempt
1. [learning]
```

## Buy-in doc

```markdown
# Ship Proposal: [Feature]

## Demo / result
[Lead with demo, screenshot, GIF, or crisp description]

## Ask
[Who should approve what by when]

## Reviewer objections answered
| Objection | Answer | Evidence |
|---|---|---|

## Rollout and rollback
- Rollout:
- Metrics:
- Rollback:

## Sign-offs
| Person/team | What they approve | Status |
|---|---|---|
```

## Merge-readiness report and quiz

```markdown
# Merge Readiness: [Change]

## Mental model
[Before -> after]

## What changed
| Area | Change | Why |
|---|---|---|

## Non-obvious behaviors
1. [behavior]

## Quiz
1. [question]
   - Correct answer:
   - Why it matters:
   - Reread if missed:

## Pass criteria
[Example: all correct before merge]
```
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall