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

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

Additional questions for the five lenses when the work involves test failures,
test strategy, coverage gaps, or quality processes.

## Lens 1 Additions: Is This Real?

- Is the test failing because the code is wrong, or because the test is wrong?
- Is this a flaky test, or is there a real intermittent bug?
- Is the coverage gap real, or is the code already tested indirectly?
- Is the quality concern based on evidence (bugs, incidents) or on metrics (coverage %)?

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

- Is the test testing behavior, or testing implementation details?
- Is the flakiness from timing, ordering, shared state, or environment?
- Is the test pyramid balanced, or are we heavy on the wrong level?
- Is the test infrastructure the problem, not the tests themselves?

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

- Are other tests in this suite suffering from the same fragility?
- Are there test utilities/helpers that could reduce duplication?
- Is there missing test infrastructure (fixtures, factories, mocks) that would
  make testing easier across the board?
- Can we add property-based tests or fuzzing to catch classes of bugs?

## Lens 4 Additions: Should We Rethink?

- Should this be tested at a different level? (unit vs. integration vs. e2e)
- Would making the code more testable (DI, pure functions) be better than
  writing more complex tests?
- Should we replace manual test orchestration with a test framework feature?
- Would contract tests replace fragile integration tests?

## Lens 5 Additions: Better Way?

- Can we use snapshot/golden-file testing instead of manual assertions?
- Can we use the type system to eliminate the need for this test?
- Can we test this via a linter/static analysis rule instead of a runtime test?
- Can we make the untestable code testable instead of working around it?
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