Skip to content

mikeparcewski/wicked-garden / skills/archetype

wicked-garden-archetype

Verified

v11 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).

wicked-garden-archetype

v11 entry point for work-shape archetypes. Each archetype is a complete unit with its own phase shape, produces, HITL discipline, and cost band. There is no universal pipeline.

Runtime

Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden". If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output. Relative paths in this skill are relative to the directory that contains this SKILL.md.

When to use this skill

Invoke when:

  • A <wg archetype="X"> or <wg archetypes> system-reminder tag appears (emitted by the v11 prompt hook).
  • The user explicitly asks to "run the {archetype} archetype" or "do this as a {archetype}" workflow.
  • You're routing from triage to a real archetype after classifying the work.

Do not use this skill for:

  • Continuation tokens ("yes", "ok", "do it"). Those carry no new shape; keep going on the current archetype.
  • Simple-edit work (typos, single-line fixes, cosmetic changes). The v11 hook already suppresses archetype tags on simple-edit intent.

The archetypes

ArchetypePhasesProducesHITL
triageclassifyrouting decisionnone
exploreframe → diverge → convergeoption set / hypothesiscontinuous
specifyelicit → structure → validateSMART acceptance criteriadiscrete:validate
decidebrief → options → score → recordADR / decision artifactdiscrete:select
shipcanary → ramp → full → soakrollout verdict / SLO snapshotdiscrete:ramp
reviewscope → assess → findings → remediate-or-acceptverdict / remediation listhard:final-verdict
incidenttriage → investigate → mitigate → resolve → followupmitigation / RCA / followuphard:mitigate
buildplan → implement → test → reviewshipped code / test reportdiscrete:review
migrateplan → expand → backfill → cutover → contractshape change / rollback proofhard:cutover
modernizediscover → extract → blueprint → transform → parity → cutovermodernization blueprint / parity proofhard:cutover

Direct invocation

This skill is also the user-facing entry point for each archetype (replacing the former per-archetype slash commands). Invoke it with archetype=<name> plus the user's arguments; the skill loads refs/{name}.md and runs that playbook.

archetypeargument hintdescription
triage[prompt]Classify a prompt into a work-shape archetype and route to its playbook. When the prompt is empty, run the detector against the conversation context.
explore[problem statement]Explore an open problem space — diverge then converge. Produces an option set or hypothesis, NOT a decision.
specify[ask]Turn an ask into SMART acceptance criteria.
decide[decision context]Pick between options with an ADR-shaped decision artifact.
ship[release / change ref]Roll out an already-built change with widening blast radius.
review[artifact / PR / commit]Independent assessment with hard verdict (APPROVE/CONDITIONAL/REJECT) — the only review producing a binding verdict (scope notes in refs/review.md).
incident[INC-id or symptom]Live-fire production incident response — mitigate first, RCA second.
build[work description]Implement and ship a feature or fix — test rigor scales with signals.
migrate[migration description]Schema/API/data shape change with expand-contract pattern.
modernize[modernization target, e.g. "port this AngularJS app to Angular"]Port a legacy codebase to a new stack — legacy→new-stack porting, NOT in-place shape change (that is migrate).

Procedure

  1. Identify the archetype. Read the <wg archetype> tag in the system reminder OR ask the user which archetype they want when ambiguous.
  2. Load the playbook. Read refs/{archetype}.md for the phase-by-phase playbook, the produces contract, and the HITL discipline.
  3. Execute the phases. Run each phase in order. At each phase boundary ask: "do I have what this phase produces?" Don't move on until yes.
  4. Honor HITL. When the playbook marks a gate as hard:*, stop and ask the user before proceeding. discrete:* gates may auto-pass when the produces contract is met. none and continuous carry no gate.
  5. Multi-archetype prompts. When the hook emitted <wg archetypes> with two co-firing matches (e.g. build + migrate for a schema-change feature), run them in dependency order: migrate shape work first, then build integration work. The dependency graph lives in each archetype's next_archetypes field in the catalog.

Catalog source of truth

.claude-plugin/archetypes.json is canonical. The detector lives at scripts/crew/archetypes_v11.py. The CLI shim:

wicked-garden run \
  scripts/crew/archetypes_v11.py \
  detect --prompt "<text>" --signals '{"production_impact": true}' --steering

Refs

  • refs/triage.md — entry classification
  • refs/explore.md — diverge/converge for open problems
  • refs/specify.md — elicit + structure + validate ACs
  • refs/decide.md — ADR-shaped option scoring
  • refs/ship.md — canary/ramp rollout
  • refs/review.md — independent assessment with verdict
  • refs/incident.md — live-fire response
  • refs/build.md — plan/implement/test/review (the common case)
  • refs/migrate.md — expand/backfill/cutover/contract (in-place shape change)
  • refs/modernize.md — discover/extract/blueprint/transform/parity/cutover (legacy→new-stack port)

What v11 archetypes are NOT

  • They are not the v6.3 target-kind archetypes (code-repo, docs-only, config-infra, etc.). Those classify what is being changed; v11 classifies what shape of work is happening. Both stay; they answer different questions.
  • They are not rigor tiers (minimal | standard | full). v11 obsoletes the rigor-tier dial: each archetype owns its own cost band and HITL.
  • They are not phase slots in a universal pipeline. Each archetype's phases live only inside that archetype.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall