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

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

Additional questions for the five lenses when the work involves code changes.

## Lens 1 Additions: Is This Real?

- Is this a bug or a misunderstanding of the API contract?
- Does the error message accurately describe the problem, or is it misleading?
- Is the "fix" already in place but behind a flag or config?

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

- Is the error handling the problem, not the error itself?
- Is a race condition or timing issue masquerading as a logic bug?
- Is the test wrong rather than the code?

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

- Are exception handlers swallowing errors that should propagate?
- Is there dead code adjacent to the change that should be removed?
- Can we add types or validation to prevent this class of bug?
- Are there missing tests that would have caught this?

## Lens 4 Additions: Should We Rethink?

- Would a Result type replace scattered try/catch?
- Would dependency injection replace the tight coupling causing the bug?
- Would an event-driven approach replace the fragile sequential flow?

## Lens 5 Additions: Better Way?

- Can we use a library/stdlib function instead of custom code?
- Can we make the compiler/type system catch this automatically?
- Can we add a linter rule to prevent recurrence?
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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated 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: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall