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/rethink-framework.md
View on GitHub---
phase_relevance: ["clarify", "design"]
archetype_relevance: ["*"]
---
# Rethink Framework
When to step back from fixing and consider redesigning. Not every issue needs a
rethink — but every issue deserves the question.
## The Rethink Test
Answer these five questions. If 3+ are "yes", consider a structural change:
1. **Recurrence**: Has this type of issue come up before in this area?
2. **Complexity**: Is the fix more complex than the thing it patches?
3. **Fragility**: Would the fix make things harder to change next time?
4. **Workaround**: Are we working around the design rather than with it?
5. **Regret**: If we'd known this need earlier, would we have built it differently?
## Rethink Strategies
### Invert the Dependency
**When**: A depends on B's internals, and the problem is in the coupling.
**How**: Have B expose what A needs. Or invert — have B call A.
**Risk**: Touches both sides. Test carefully.
### Split the Responsibility
**When**: One thing does too many jobs, and the problem is in their interaction.
**How**: Separate into distinct pieces with clear interfaces.
**Risk**: More pieces, but each is simpler. Split along natural boundaries.
### Replace Conditionals with Structure
**When**: Problem in a complex if/else chain handling different cases.
**How**: Define a base type and specialized variants. Route via registry/factory.
**Risk**: Over-engineering if only 2-3 cases. Good when cases grow.
### Make Invalid States Impossible
**When**: Problem from something being in a state that shouldn't exist.
**How**: Use types, enums, or state machines to constrain what's possible.
**Risk**: May require interface changes. Worth it for core concepts.
### Extract the Policy
**When**: Rules are embedded in infrastructure.
**How**: Pull rules into a separate, testable policy object.
**Risk**: Adds indirection. Justified when rules change frequently.
### Simplify by Removing
**When**: Problem is in unused or rarely-used functionality.
**How**: Delete it. Check usage, deprecate if needed, then remove.
**Risk**: Low — less surface area = fewer problems.
## Cost-Benefit Check
Before proposing a rethink, estimate:
```
Rethink Cost = (things touched x complexity) + (test rewrite) + (review overhead)
Ongoing Cost = (similar issues per quarter x fix time) + (confusion x ramp-up time)
If annualized Ongoing Cost > 2x Rethink Cost → rethink now
If Ongoing Cost < Rethink Cost → fix and document the debt
```
## Scope Control
Rethinks can expand without bounds. Constrain them:
1. **Time-box**: Set a maximum. If it takes longer, it's a separate project.
2. **Blast radius cap**: Touch at most N things. If more, split into phases.
3. **Quality parity**: New approach must have equal or better coverage before shipping.
4. **Rollback plan**: Ensure the old approach can be restored if needed.
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 |