mikeparcewski/wicked-garden / skills/archetype
wicked-garden-archetype
Verifiedv11 work-shape archetype runner. When a prompt has been routed to one of the archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate, modernize), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or a direct per-archetype ask — "triage this prompt", "review this PR / artifact", "build this feature", "decide between these options", "explore this problem", "handle this incident", "run this migration", "modernize / port this legacy app", "ship this release", "write acceptance criteria" (invoke with archetype=<name> plus the user's args — see the Direct invocation table).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| refs/build.md | markdown | 7.5 KB |
| refs/decide.md | markdown | 6.1 KB |
| refs/explore.md | markdown | 2.3 KB |
| refs/incident.md | markdown | 8.2 KB |
| refs/migrate.md | markdown | 9.7 KB |
| refs/modernize.md | markdown | 11.6 KB |
| refs/review.md | markdown | 9.7 KB |
| refs/ship.md | markdown | 6.1 KB |
| refs/specify.md | markdown | 5.8 KB |
| refs/triage.md | markdown | 2.7 KB |
refs/explore.md
View on GitHub# explore — diverge then converge on open problems
When the problem space is genuinely open and a single answer would be
premature. Produces an option set or hypothesis, **not a decision** — that's
the `decide` archetype's job.
## Phase shape
| Phase | Goal |
|----------|----------------------------------------------------------|
| frame | Name the problem in one sentence. Surface assumptions. |
| diverge | Generate 4–8 distinct options. Aim for variety, not quality. |
| converge | Cluster, score qualitatively, and pick a top-3 to take forward. |
## Produces
- **Option set**: 3–8 named alternatives with one-line rationales.
- **Hypothesis** (when the prompt is research-shaped): testable statement
with a falsification condition.
## HITL
`continuous` — the user is a participant. Don't run explore as a closed
loop; check in after frame, after diverge, before convergence.
## How to run
### frame
1. Restate the problem in one sentence in your own words. Confirm with the user.
2. List 2–4 assumptions you're making. Get the user to mark them
"true / unknown / false".
3. If a critical assumption is "unknown", branch to `specify` to elicit
facts before continuing.
### diverge
1. Generate 4–8 options. **Variety beats quality.** Include at least one
"lazy" option (do nothing) and one "expensive" option (the over-built
answer).
2. Use `wicked-garden:jam:quick` or `wicked-garden:jam:brainstorm` for
structured ideation when the surface is unfamiliar.
3. Don't score yet. Just name them.
### converge
1. Cluster the options into 2–3 thematic groups.
2. Pick the top-3 to take forward. Each one needs:
- A one-line description.
- A risk note.
- A reversibility note.
3. Hand off to `decide` if the user wants a verdict, or to `specify` /
`build` if the path forward is now clear.
## When to stop
Explore is done when the user has a top-3 option set OR a falsifiable
hypothesis they can take forward. Don't keep diverging.
## Anti-patterns
- **Don't pick a winner inside explore.** That's the decide archetype.
- **Don't skip frame.** A bad problem statement makes diverge produce
noise.
- **Don't rank prematurely.** Convergence is qualitative clustering,
not quantitative scoring.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |