mikeparcewski/wicked-garden:archetype
skills/archetype/SKILL.md
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), 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 when one of the per-archetype slash commands resolves to this skill.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden:archetypeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 26, 2026, 7:10 AM26.6s10 files scanned
SKILL.md
- name:
- wicked-garden:archetype
- description:
- |
- Use when:
- a `<wg archetype="X">` or `<wg archetypes>` system-reminder
- allowed-tools:
- ["*"]
/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.
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 9 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 |
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:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" \
"${CLAUDE_PLUGIN_ROOT}/scripts/crew/archetypes_v11.py" \
detect --prompt "<text>" --signals '{"production_impact": true}' --steering
Refs
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
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.
Related Skills
mikeparcewski/skills/engineering/large-scale-migration
development
VerifiedTrustedCommunity
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
8SKILL.mdUpdated Jun 3, 2026
mikeparcewski/wicked-garden:classify
testing
VerifiedTrustedCommunity
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
8SKILL.mdUpdated May 26, 2026
mikeparcewski/intent
development
VerifiedTrustedCommunity
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".
8SKILL.mdUpdated May 6, 2026
mikeparcewski/worktrees
development
VerifiedTrustedCommunity
Git worktree hygiene — when to create, how to clean up, and what fails silently. Captures three classes of bug that recur with worktree-based agent isolation: subagent dangling commits, orphan branches with unique work, and time-sensitive dangling-commit garbage collection. Includes detection commands, the salvage decision flow, and the trust-but-verify rule for subagent commit reports. Use when: a subagent reports a commit SHA, after a worktree-based agent finishes, cleaning up `.claude/worktrees/`, salvaging old crew worktrees, "is this branch in main?", verifying agent-claimed commits actually landed, planning multi-agent parallel work in worktrees.
8SKILL.mdUpdated Apr 29, 2026