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/run-workflow.md
View on GitHub# Run Workflow — operational runbook
How to run a user-invoked deliberation end-to-end. The five lenses, the brief
template, and the domain lens refs live in `SKILL.md` — this ref covers only
the operational steps around them. Works for bugs, features, content, design,
architecture — anything.
## Arguments
- `description` (required): Issue description, GitHub issue number (e.g., `#42`), or quoted text
- `--deep`: Run blast-radius and lineage analysis for affected areas
- `--batch`: Process multiple issues (comma-separated numbers)
## Steps
### 1. Parse Input
If the argument is a GitHub issue number (`#N` or just a number):
```bash
gh issue view {number} --json title,body,labels,comments 2>/dev/null
```
Extract title, body, and any discussion context. If not a GH issue, use the raw description.
### 2. Gather Context
**Read project descriptors** (if they exist):
- `CLAUDE.md`, `README.md` for project context
- Recent git log for related changes:
```bash
git log --oneline -20
```
**Search for affected areas**:
- Extract key references from the description
- Use the estate MCP `SearchEntity` tool (or Grep) for symbol search
- If `--deep` flag: use the `wicked-garden-search` skill's `blast-radius` action on key symbols
**Recall relevant memories**:
**Hand-off** — open the `wicked-garden-mem` skill and run its `recall` action with `{key terms}` as the query; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.
### 3. Detect Context and Load Lens
Determine what kind of work this is (code, content, design, architecture, or mixed) and load the appropriate domain lens from this skill's refs:
- Code changes → `refs/code-lens.md`
- Content/docs → `refs/content-lens.md`
- Design/UX → `refs/design-lens.md`
- Architecture/system → `refs/architecture-lens.md`
Multiple lenses can apply. Load what's relevant.
### 4. Apply Five Lenses
**Hand-off** — if your harness has a codebase-exploration agent, hand it the
prompt below (do NOT restate the five lenses — the agent loads them from the
`wicked-garden-deliberate` skill's SKILL.md); on a harness without one, run the
five-lens analysis inline, keeping its output separate from your own:
```
Analyze this work request through the five-lens deliberate framework.
Load the wicked-garden-deliberate skill (skills/deliberate/SKILL.md) and apply
its five lenses ('Is This Real?', 'What's Actually Going On?', 'What Else Can
We Fix While We're Here?', 'Should We Rethink the Design?', 'Is There a Better
Way?') exactly as defined there. Read relevant files to ground your analysis.
REQUEST: {title}
DESCRIPTION: {body}
AFFECTED AREAS: {files/pages/components from context gathering}
CONTEXT TYPE: {code/content/design/architecture}
RELEVANT LENS REFS: {the refs selected in Step 3 — load these too}
Return a structured Deliberation Brief (template in the skill's SKILL.md) with:
- Assessment (validity, root cause, blast radius)
- Opportunities (cleanup, generalization, rethink)
- Recommendation (fix/redesign/generalize/defer/close + rationale)
- Scope change (expand/contract/same)
- Guidance (specific next steps)
```
### 5. Present Deliberation Brief
Format the agent's findings using the **Deliberation Brief** template from
`SKILL.md` (Assessment / Opportunities / Recommendation / Guidance).
### 6. Store Deliberation
Store as a memory for future reference:
**Hand-off** — open the `wicked-garden-mem` skill and run its `store` action with the memory text `Deliberation: {title} — {strategy}: {one-line rationale}` and `kind=fact, about=[deliberation, {project}]`; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.
### 7. Crew Integration
If a crew project is active, update the project with resolution findings:
```bash
wicked-garden run scripts/_run.py scripts/crew/phase_manager.py {project} update \
--data '{"deliberations": [{"issue": "{title}", "strategy": "{strategy}", "scope_change": "{change}"}]}' \
--json
```
## Batch Mode
When `--batch` is used with multiple issue numbers:
1. Fetch all issues in parallel
2. Run the five-lens analysis on each
3. Cross-reference: do any issues share root causes?
4. Present a consolidated deliberation table with individual briefs
## Examples
Invoke the `wicked-garden-deliberate` skill with:
```
"Auth tokens expire too early on mobile"
#281
--batch "280,281"
--deep "Navigation feels confusing on the settings page"
"README is outdated and contradicts the API docs"
```
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: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |