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

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

Additional questions for the five lenses when the work involves content, docs, or copy.

## Lens 1 Additions: Is This Real?

- Is the content actually wrong, or is the reader's context different than expected?
- Is this a gap in the content, or should the reader be directed elsewhere?
- Is the complaint about accuracy, clarity, or discoverability?

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

- Is the information correct but poorly structured?
- Is the audience assumption wrong? (writing for experts, read by beginners)
- Is the content stale because the source of truth changed but docs weren't updated?

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

- Are other docs making the same assumption about audience?
- Is there a pattern of content going stale? Can we automate freshness checks?
- Are related pages consistent in terminology, tone, and structure?

## Lens 4 Additions: Should We Rethink?

- Should this be a tutorial instead of reference docs (or vice versa)?
- Should this content be generated from code/schema instead of hand-written?
- Is the information architecture putting this in the wrong place?

## Lens 5 Additions: Better Way?

- Can we link to existing content instead of writing new?
- Can we use a diagram instead of three paragraphs?
- Can we add an example instead of more explanation?
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