mikeparcewski/wicked-garden / skills/deliberate
wicked-garden-deliberate
VerifiedCritical 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| refs/architecture-lens.md | markdown | 1.4 KB |
| refs/assumptions-lens.md | markdown | 1.9 KB |
| refs/code-lens.md | markdown | 1.3 KB |
| refs/content-lens.md | markdown | 1.4 KB |
| refs/data-lens.md | markdown | 1.7 KB |
| refs/design-lens.md | markdown | 1.3 KB |
| refs/opportunity-patterns.md | markdown | 4.4 KB |
| refs/ops-lens.md | markdown | 1.7 KB |
| refs/product-lens.md | markdown | 1.9 KB |
| refs/rethink-framework.md | markdown | 2.8 KB |
| refs/run-workflow.md | markdown | 4.5 KB |
| refs/security-lens.md | markdown | 2.0 KB |
| refs/testing-lens.md | markdown | 1.9 KB |
| refs/timing-lens.md | markdown | 1.8 KB |
refs/data-lens.md
View on GitHub---
phase_relevance: ["clarify", "design"]
archetype_relevance: ["*"]
---
# Data Lens
Additional questions for the five lenses when the work involves data pipelines,
schemas, analytics, or data quality.
## Lens 1 Additions: Is This Real?
- Is the data actually wrong, or is the expectation wrong?
- Is this a data quality issue or a schema/contract issue?
- Is the "missing data" actually filtered out by a rule that's working correctly?
- Are we measuring the right thing, or is the metric definition flawed?
## Lens 2 Additions: What's Actually Going On?
- Is the issue at ingestion, transformation, or presentation?
- Is a schema change upstream silently breaking downstream consumers?
- Is this a timing issue? (data not yet available vs. actually missing)
- Is the pipeline idempotent? Could reruns have introduced duplicates?
## Lens 3 Additions: What Else Can We Fix?
- Are other pipelines consuming the same source with the same vulnerability?
- Is there missing data validation at ingestion boundaries?
- Are schema contracts documented and enforced, or assumed?
- Can we add data quality checks that catch this class of issue automatically?
## Lens 4 Additions: Should We Rethink?
- Should this be a streaming pipeline instead of batch (or vice versa)?
- Would schema evolution tooling prevent breaking changes?
- Should the data ownership boundary move? (who produces vs. consumes)
- Would a data contract between producer and consumer prevent this?
## Lens 5 Additions: Better Way?
- Can we fix the source instead of patching the consumer?
- Can we add a dead-letter queue instead of failing silently?
- Can we use schema registry to catch incompatibilities before deploy?
- Can we solve this with monitoring/alerting instead of code changes?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |