Skip to content

mikeparcewski/wicked-garden / skills/deliberate

wicked-garden-deliberate

Verified

Critical 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.

FileKindSize
SKILL.mdskill md6.4 KB
refs/architecture-lens.mdmarkdown1.4 KB
refs/assumptions-lens.mdmarkdown1.9 KB
refs/code-lens.mdmarkdown1.3 KB
refs/content-lens.mdmarkdown1.4 KB
refs/data-lens.mdmarkdown1.7 KB
refs/design-lens.mdmarkdown1.3 KB
refs/opportunity-patterns.mdmarkdown4.4 KB
refs/ops-lens.mdmarkdown1.7 KB
refs/product-lens.mdmarkdown1.9 KB
refs/rethink-framework.mdmarkdown2.8 KB
refs/run-workflow.mdmarkdown4.5 KB
refs/security-lens.mdmarkdown2.0 KB
refs/testing-lens.mdmarkdown1.9 KB
refs/timing-lens.mdmarkdown1.8 KB

refs/product-lens.md

View on GitHub
---
phase_relevance: ["clarify", "design"]
archetype_relevance: ["*"]
---
# Product Lens

Additional questions for the five lenses when the work involves features, user needs,
prioritization, or product strategy.

## Lens 1 Additions: Is This Real?

- Does anyone actually want this? What's the evidence of demand?
- Is this one user's request or a pattern across many?
- Is the pain real and frequent, or mild and rare?
- Would users notice if we did nothing?
- Are we building this because a stakeholder asked, or because users need it?

## Lens 2 Additions: What's Actually Going On?

- Is the user struggling with our product, or with the underlying problem?
- Is the feature request actually a workaround for a missing capability?
- Is the complaint about the feature, or about how they discovered it?
- Are users asking for what they want, or describing what they think the solution is?
  (What's the job-to-be-done behind the request?)

## Lens 3 Additions: What Else Can We Fix?

- Are there related user pain points in the same workflow?
- Would improving onboarding/docs reduce the need for this feature?
- Are there power-user workarounds that indicate a broader need?
- Can we improve the existing feature instead of adding a new one?

## Lens 4 Additions: Should We Rethink?

- Should this be a configuration option instead of a feature?
- Should this feature exist at all, or does it add complexity without proportional value?
- Would simplifying the product (removing features) solve the underlying confusion?
- Is this the right product to solve this problem, or should it be a separate tool?

## Lens 5 Additions: Better Way?

- Can we solve this with better defaults instead of a new setting?
- Can we solve this with documentation/education instead of code?
- Can we let users solve it themselves with an extension/API/integration?
- Is there a 10% effort solution that delivers 80% of the value?
- Can we validate the approach with a prototype before full investment?
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: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated 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: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall