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/opportunity-patterns.md
View on GitHub---
phase_relevance: ["clarify", "design"]
archetype_relevance: ["*"]
---
# Opportunity Patterns
Common patterns where a single issue reveals broader improvement opportunities.
These are domain-agnostic — they apply to code, content, design, and systems alike.
## Pattern: Shotgun Surgery
**Signal**: A single change requires edits in many places.
**Opportunity**: Extract the scattered concern into a shared abstraction.
**Examples**:
- Code: Date formatting fix needed in 12 controllers → extract DateFormatter
- Content: Brand voice update required across 30 pages → extract style tokens
- Design: Color change needed in 15 components → extract design tokens
## Pattern: Silent Failure
**Signal**: Problem caused by something failing silently — no error, no log, no feedback.
**Opportunity**: Audit the area for other silent failures. Add observability.
**Examples**:
- Code: Exception swallowed, returns None → add structured error types
- Content: Broken link returns 200 with wrong page → add link validation
- Design: Form submits but nothing happens → add feedback states
## Pattern: Duplication
**Signal**: Fix needs to be applied in multiple places with similar logic.
**Opportunity**: Consolidate into a single source of truth.
**Examples**:
- Code: Validation logic copy-pasted across endpoints → extract Validator
- Content: Same instructions written differently in 3 guides → single source
- Design: Same component built differently in 4 views → shared component
## Pattern: Missing Abstraction
**Signal**: Multiple consumers implement the same multi-step process inline.
**Opportunity**: Name the process and give it a proper interface.
**Examples**:
- Code: Three services each query→transform→save → extract Pipeline
- Content: Writers each invent their own tutorial structure → extract template
- Design: Each page builds its own nav → extract navigation pattern
## Pattern: Leaky Boundary
**Signal**: Consumers need internal knowledge to use something correctly.
**Opportunity**: Redesign the interface to hide the complexity.
**Examples**:
- Code: Must call init() before use() → use context manager
- Content: Reader must know jargon to understand docs → add glossary/simplify
- Design: User must know hidden gesture to access feature → improve discoverability
## Pattern: Config Drift
**Signal**: Problem from inconsistent settings across environments or components.
**Opportunity**: Centralize with validation and parity checks.
**Examples**:
- Code: Two services define timeouts independently → shared config
- Content: Style guide says one thing, templates do another → sync
- Design: Mobile and desktop use different spacing scales → unify
## Pattern: Temporal Coupling
**Signal**: Problem caused by doing things in the wrong order.
**Opportunity**: Make invalid sequences impossible.
**Examples**:
- Code: Must call connect() before query() → auto-connect on first query
- Content: Must read Part 1 before Part 2 but nothing says so → add prereqs
- Design: Must complete Step A before Step B but UI allows skipping → enforce flow
## Pattern: Primitive Obsession
**Signal**: Problem from using generic types where domain types would prevent errors.
**Opportunity**: Introduce named types that carry meaning.
**Examples**:
- Code: User ID and session ID both strings, swapped in call → typed IDs
- Content: All metadata stored as free text → structured fields
- Design: All buttons look the same regardless of action → semantic variants
## Pattern: Feature Envy
**Signal**: Something reaches deep into another area's internals to get what it needs.
**Opportunity**: Move the logic to where the data lives, expose a proper interface.
**Examples**:
- Code: Report reads 5 private fields → add summary method on the owner
- Content: FAQ duplicates info from other pages → link instead of copy
- Design: Dashboard rebuilds data viz from raw data → expose chart-ready API
## Evaluation
When reviewing an issue, check which patterns apply:
| Pattern | Present? | Severity (0-3) | Fix Effort | Payoff |
|---------|----------|-----------------|------------|--------|
| Shotgun surgery | | | | |
| Silent failure | | | | |
| Duplication | | | | |
| Missing abstraction | | | | |
| Leaky boundary | | | | |
| Config drift | | | | |
| Temporal coupling | | | | |
| Primitive obsession | | | | |
| Feature envy | | | | |
**Priority**: High severity + low effort + high payoff = do it now alongside the fix.
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 |