mikeparcewski/wicked-garden / skills/deliberate
wicked-garden-deliberate
VerifiedCritical thinking framework applied before doing work. Challenges assumptions, reframes problems, identifies hidden opportunities, and validates whether the stated ask is the right ask. A way of approaching work, not a specialist discipline. Use when: challenging assumptions before implementation, reframing a stated problem, asking whether the right thing is being asked at all, "deliberate on this", "deliberate #42" (a GitHub issue number), "critically analyze this request before implementing", `--deep` (blast-radius analysis), `--batch` (multiple issues, shared root causes), or any former /wicked-garden:deliberate invocation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| refs/architecture-lens.md | markdown | 1.4 KB |
| refs/assumptions-lens.md | markdown | 1.9 KB |
| refs/code-lens.md | markdown | 1.3 KB |
| refs/content-lens.md | markdown | 1.4 KB |
| refs/data-lens.md | markdown | 1.7 KB |
| refs/design-lens.md | markdown | 1.3 KB |
| refs/opportunity-patterns.md | markdown | 4.4 KB |
| refs/ops-lens.md | markdown | 1.7 KB |
| refs/product-lens.md | markdown | 1.9 KB |
| refs/rethink-framework.md | markdown | 2.8 KB |
| refs/run-workflow.md | markdown | 4.5 KB |
| refs/security-lens.md | markdown | 2.0 KB |
| refs/testing-lens.md | markdown | 1.9 KB |
| refs/timing-lens.md | markdown | 1.8 KB |
refs/assumptions-lens.md
View on GitHub---
phase_relevance: ["clarify", "design"]
archetype_relevance: ["*"]
---
# Assumptions Lens
Additional questions for the five lenses that surface hidden assumptions and
fragile dependencies. Maps what we're taking for granted and what breaks if we're wrong.
## Lens 1 Additions: Is This Real?
- What assumption makes us believe this is a problem? Is that assumption verified?
- Are we assuming user behavior that we haven't observed?
- Are we assuming a dependency will remain stable (API, library, service)?
- Are we assuming this environment/context will stay the same?
## Lens 2 Additions: What's Actually Going On?
- What are the implicit assumptions in the current design that led to this issue?
- Is the problem caused by an assumption that was once true but no longer is?
- Are we assuming cause and effect, or just correlation?
- What would we discover if we questioned the constraint we think is fixed?
## Lens 3 Additions: What Else Can We Fix?
- Are there other parts of the system built on the same fragile assumption?
- Can we make assumptions explicit — document them so they're auditable?
- Can we add assertions or contracts that fail loudly when assumptions break?
- Are there undocumented dependencies between components?
## Lens 4 Additions: Should We Rethink?
- Would designing for the assumption being WRONG be more resilient?
- Can we eliminate the assumption entirely instead of coding around it?
- Should we build an abstraction layer so changing this assumption later is cheap?
- Would a different architecture have fewer hidden assumptions?
## Lens 5 Additions: Better Way?
- Can we validate the key assumption before building? (prototype, data check, user test)
- Can we design for graceful degradation when assumptions fail?
- Can we add monitoring that alerts us when an assumption is violated?
- Can we make the dependency explicit and versioned instead of implicit?
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: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |