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/timing-lens.md

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

Additional questions for the five lenses that challenge WHEN to act, not just
what to do. Catches premature optimization, false urgency, and wrong sequencing.

## Lens 1 Additions: Is This Real?

- Is this a "right now" problem, or are we solving for something 6+ months away?
- Is the urgency real, or manufactured by recency bias? (just saw it, so it feels urgent)
- Are we optimizing for the wrong phase? (pre-MVP polish, scaling before traction)
- Would waiting a week give us better information to make this decision?

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

- Is the sequencing wrong? Should something else happen first?
- Are we blocked on a decision we don't have enough data to make yet?
- Is this a time-sensitive window (security fix, compliance deadline) or self-imposed urgency?
- Are we conflating "this is important" with "this must happen now"?

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

- Are there quick wins we should do first that unblock this work?
- Is there prerequisite work that would make this change cheaper later?
- Can we ship a partial solution now and iterate, instead of building the full thing?

## Lens 4 Additions: Should We Rethink?

- Would deferring this 2 weeks let us batch it with related changes?
- Would making this decision incrementally (reversible steps) be safer than
  committing to the full approach now?
- Are we trying to predict the future? Can we build for adaptability instead?

## Lens 5 Additions: Better Way?

- Can we set a time-boxed experiment instead of a permanent decision?
- Can we build a toggle/flag so this is reversible if our timing is wrong?
- Can we validate the assumption that this is urgent before investing?
- Is "do nothing and monitor" a legitimate option?
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