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

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

Additional questions for the five lenses when the work involves authentication,
authorization, data protection, compliance, or security posture.

## Lens 1 Additions: Is This Real?

- Is this an actual vulnerability, or a theoretical risk with no practical exploit?
- Is the security scanner correct, or is this a false positive?
- Is the risk in our code, or in a dependency we don't control?
- What's the actual threat model? Who would exploit this and how?

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

- Is the auth logic wrong, or is the trust boundary in the wrong place?
- Is this a missing check, or is the entire authorization model flawed?
- Is sensitive data exposed because of a code bug, or because the data flow
  shouldn't include it at all?
- Is the vulnerability in the feature, or in the error handling around it?

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

- Are other endpoints/surfaces vulnerable to the same class of attack?
- Are secrets managed consistently, or are there hardcoded values elsewhere?
- Is input validation applied uniformly at trust boundaries?
- Are there other places where we trust input we shouldn't?
- Can we add security headers, CSP rules, or rate limits broadly?

## Lens 4 Additions: Should We Rethink?

- Should we move to a zero-trust model instead of perimeter-based?
- Would a policy engine replace scattered authorization checks?
- Should secrets management be centralized instead of per-service?
- Would encryption at rest eliminate the risk class entirely?
- Should we use allowlists instead of denylists?

## Lens 5 Additions: Better Way?

- Can we eliminate the sensitive data instead of protecting it?
- Can we use a framework/library security primitive instead of custom code?
- Can we shift this to infrastructure (WAF, service mesh) instead of application?
- Can we make the secure path the default, so insecure requires explicit opt-in?
- Can automated scanning catch this class of issue going forward?
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