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/triage.md
View on GitHub# triage — classify and route
The entry archetype. Every prompt that doesn't already carry an archetype tag
starts here. Triage is not a workflow on its own — it's a routing decision.
## Phase shape
| Phase | Goal |
|----------|-----------------------------------------------|
| classify | Pick the right archetype (or set of archetypes) and hand off. |
## Produces
- A routing decision: which archetype(s) this prompt belongs in.
## HITL
`none` — fully automated. The detector runs, the directive emits, the
agent picks up the playbook from there.
## How to run
1. **Read the prompt.** What is the user actually asking for? When the
prompt is empty, run the detector against the conversation context
instead.
2. **Run the detector.** Call `wicked-garden run scripts/crew/archetypes_v11.py detect` with
the prompt and any known signals.
3. **Inspect the matches.**
- Single high-confidence match (≥ 0.7): hand off to that archetype's
playbook.
- Multiple medium matches (0.5–0.7): pick the one with the strongest
evidence; if you can't, ask the user which shape they want.
- Only triage matched: ask a clarifying question naming what's
missing — usually the work isn't ambiguous, the prompt is.
## When to stop in triage
Triage exits as soon as you've named the next archetype. Do **not**
do work inside triage — every minute spent here is a minute the
real work isn't moving.
## Examples
| Prompt | Routes to |
|---------------------------------------------------|----------------------|
| "implement caching for the dashboard" | build |
| "drop legacy_id column" | build + migrate |
| "checkout is down — 5xx spiking" | incident |
| "redis or memcached for sessions?" | decide |
| "review the new auth middleware" | review |
| "what should we do about rate limiting?" | explore |
| "write acceptance criteria for the export" | specify |
| "kick off canary for the pricing change" | ship |
| "fix typo in README" | (suppressed — simple-edit, no archetype) |
## Anti-patterns
- **Don't classify into a tier.** "standard rigor" is not an archetype.
Triage picks a *shape*, not a depth dial.
- **Don't stack triage onto an active archetype.** If the user is already
inside `build`, a follow-up "and also run the migration" doesn't restart
triage — it adds `migrate` as a co-archetype.
- **Don't write code in triage.** If your hands are at the keyboard,
you've already left triage.
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 |