wicked-garden-archetype
Skill9 starsChanged 7 months agoMITView on GitHub
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`.
- Installs packages
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- releaseSkill
- scaffoldSkill
- wicked-garden-agentic-agentic-patternsSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-frameworksSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-dataSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domain-modelerSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-architectureSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-memSkill
- wicked-garden-personaSkill
- wicked-garden-platform-auditSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
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 …
- Distinctive: line 43
Do not use this skill for:
- Very specific: line 86
Identify the archetype: Read the <wg archetype> tag in the system reminder OR ask the user which archetype they want when ambiguous.
- Very specific: line 88
Load the playbook: Read refs/{archetype}.md for the phase-by-phase playbook, the produces contract, and the HITL discipline.
- Distinctive: line 90
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.
- Very specific: line 92
Honor HITL: When the playbook marks a gate as hard:*, stop and ask the user before proceeding.
- Very specific: line 95
Multi-archetype prompts: When the hook emitted <wg archetypes> with two co-firing matches (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
triageto 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-editintent.
The archetypes
| Archetype | Phases | Produces | HITL |
| triage | classify | routing decision | none |
| explore | frame → diverge → converge | option set / hypothesis | continuous |
| specify | elicit → structure → validate | SMART acceptance criteria | discrete:validate |
| decide | brief → options → score → record | ADR / decision artifact | discrete:select |
| ship | canary → ramp → full → soak | rollout verdict / SLO snapshot | discrete:ramp |
| review | scope → assess → findings → remediate-or-accept | verdict / remediation list | hard:final-verdict |
| incident | triage → investigate → mitigate → resolve → followup | mitigation / RCA / followup | hard:mitigate |
| build | plan → implement → test → review | shipped code / test report | discrete:review |
| migrate | plan → expand → backfill → cutover → contract | shape change / rollback proof | hard:cutover |
| modernize | discover → extract → blueprint → transform → parity → cutover | modernization blueprint / parity proof | hard: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.
| archetype | argument hint | description |
| 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
- Identify the archetype. Read the
<wg archetype>tag in the system reminder OR ask the user which archetype they want when ambiguous. - Load the playbook. Read
refs/{archetype}.mdfor the phase-by-phase playbook, the produces contract, and the HITL discipline. - 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.
- 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.noneandcontinuouscarry no gate. - Multi-archetype prompts. When the hook emitted
<wg archetypes>with two co-firing matches (e.g.build + migratefor a schema-change feature), run them in dependency order:migrateshape work first, thenbuildintegration work. The dependency graph lives in each archetype'snext_archetypesfield 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}' --steeringRefs
refs/triage.md— entry classificationrefs/explore.md— diverge/converge for open problemsrefs/specify.md— elicit + structure + validate ACsrefs/decide.md— ADR-shaped option scoringrefs/ship.md— canary/ramp rolloutrefs/review.md— independent assessment with verdictrefs/incident.md— live-fire responserefs/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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

