wicked-garden-core

Estrellas8

Forks2

Actualizado15 de julio de 2026 a las 06:05

Core utility surface for the wicked-garden plugin: help/overview, first-run setup + codebase onboarding, the wicked-* peer installer, selective state reset, the where-am-i path manifest, and structured issue filing. Use when: "wicked-garden help", "show wicked-garden commands", "what can wicked-garden do", "set up wicked-garden", "setup", "--reconfigure", "onboard this codebase", "install wicked tools", "add peers", "install layers", "reset wicked-garden", "clear state", "--list-projects", "where am I", "path manifest", "report issue", "file a bug", "--list-unfiled", or any former /wicked-garden:{help|setup|install|reset| where-am-i|report-issue} invocation.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

mikeparcewski

mikeparcewski/wicked-garden

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Otras ocupaciones informáticasOcupaciones informáticas y matemáticas·SOC 15-1299

Explorador de archivos

6 archivos

SKILL.md

readonly

Más de este repositorio

mismo repositorio

wicked-garden-archetype

mikeparcewski/wicked-garden

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

2026-07-218

wicked-garden-engineering-conformance-reviewer

mikeparcewski/wicked-garden

Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.

2026-07-168

wicked-garden-domain-coverage

mikeparcewski/wicked-garden

Coverage evaluator + pre-build threat model for the domain-extraction workflow (CONTRACT-3 §2). Emits `coverage-report.json` from the estate store, then adversarially reviews the extracted domain model: hunts missing error paths, ungrounded rules, reason-less drops, cross-cluster smears, and coverage holes. Use when: dispatched as the `coverage` phase of a domain-extraction workflow run. The phase runs in a git worktree; WICKED_ESTATE_DB points at the live estate store. NOT for mining rules (domain-extractor) or grouping domains (domain-modeler). This worker EMITS coverage evidence AND CRITIQUES the domain model.

2026-07-168

wicked-garden-domain-extractor

mikeparcewski/wicked-garden

Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).

2026-07-158

wicked-garden-domain-modeler

mikeparcewski/wicked-garden

Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).

2026-07-158

wicked-garden-domain

mikeparcewski/wicked-garden

The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the

2026-07-158

name	wicked-garden-core
description	Core utility surface for the wicked-garden plugin: help/overview, first-run setup + codebase onboarding, the wicked-* peer installer, selective state reset, the where-am-i path manifest, and structured issue filing. Use when: "wicked-garden help", "show wicked-garden commands", "what can wicked-garden do", "set up wicked-garden", "setup", "--reconfigure", "onboard this codebase", "install wicked tools", "add peers", "install layers", "reset wicked-garden", "clear state", "--list-projects", "where am I", "path manifest", "report issue", "file a bug", "--list-unfiled", or any former /wicked-garden:{help\|setup\|install\|reset\| where-am-i\|report-issue} invocation.
user-invocable	true
allowed-tools	["AskUserQuestion","Bash","Read","Write","Grep","Skill","Agent"]
phase_relevance	["*"]
archetype_relevance	["*"]

Wicked Garden Core

One entry point for the plugin's utility verbs. Never fork this skill — the setup / install / reset / report-issue actions are interactive wizards that must converse with the user (AskUserQuestion, or plain-text STOP-and-wait in dangerous mode). Run everything inline in the parent context.

Action router

Action	Trigger phrases / args	How
`help`	no args, "help", "overview"	Default — show the overview below
`setup`	"setup", "--reconfigure", "onboard this codebase"	`Read("${CLAUDE_PLUGIN_ROOT}/skills/core/refs/setup.md")` and follow it
`install`	"install", "add peers", "install layers"	`Read("${CLAUDE_PLUGIN_ROOT}/skills/core/refs/install.md")` and follow it
`reset`	"reset", "clear state", `--all` `--only` `--keep` `--force` `--list-projects` `--all-projects`	`Read("${CLAUDE_PLUGIN_ROOT}/skills/core/refs/reset.md")` and follow it
`where-am-i`	"where am I", "path manifest", `--fence` `--env`	Inline section below
`report-issue`	"report issue", "file a bug", `bug` `ux-friction` `unmet-outcome` `--list-unfiled`	`Read("${CLAUDE_PLUGIN_ROOT}/skills/core/refs/report-issue.md")` and follow it

Action: help (default)

Show this overview when invoked with no action or asked for help.

The Wicked Garden Marketplace — gap-filling capabilities for modern coding-agent harnesses. It reads each prompt as one or more work-shape archetypes (v11) and applies the right rigor/gate, re-derives "done" from evidence, surfaces relationships grep can't see, and otherwise stays out of the harness's way.

Headline skills

Skill	What it does
`wicked-garden-prove`	Re-derive "done" from recorded evidence (the produces-gate). Its `compile` action emits a self-contained, vault-backed gate into any repo.
`wicked-garden-core`	This skill — setup, install, reset, where-am-i, report-issue, help.
`wicked-garden-deliberate`	Critically analyze a request before doing the work — challenge assumptions, find root causes, propose better approaches.
`wicked-garden-smaht`	On-demand context assembly + session briefing; its `intent` action sets or inspects the active session intent.
`wicked-garden-archetype`	The v11 work-shape playbooks (below).

Archetypes (v11 work-shape model)

Invoke the wicked-garden-archetype skill with a work-shape name to run its playbook. Each prompt classifies into one or more of these; run them in dependency order.

Archetype	Shape
`triage`	classify → routing decision
`explore`	frame → diverge → converge
`specify`	elicit → structure → validate (SMART acceptance criteria)
`decide`	brief → options → score → record (ADR)
`ship`	canary → ramp → full → soak (rollout verdict)
`review`	scope → assess → findings → remediate-or-accept (hard verdict)
`incident`	triage → investigate → mitigate → resolve → followup
`build`	plan → implement → test → review
`migrate`	plan → expand → backfill → cutover → contract

Domain skills

Each domain is one consolidated skill that routes to its actions.

Skill	Description	Key actions
`wicked-garden-agentic`	Design, review, and audit agentic AI systems	review · design · audit · frameworks
`wicked-garden-data`	Data analysis, pipelines, ML, and ontology recommendations	analyze · pipeline · ml · ontology
`wicked-garden-engineering`	Architecture, code review, debugging, docs, planning, and deterministic multi-file code transformations	review · debug · arch · plan · apply
`wicked-garden-jam`	Multi-model brainstorming + structured council (independent second opinion)	council · brainstorm · quick · revisit
`wicked-garden-domain`	Extract a codebase's domain model — business rules + provenance, entities, requirements on the estate graph — a foundational substrate build/migrate/review/modernize all consume (none own)	extractor · modeler · coverage
`wicked-garden-persona`	Define and invoke named personas to perform work with a specific lens	as · define · list
`wicked-garden-platform`	Security, infrastructure, compliance, CI/CD, incidents, traces, and plugin diagnostics	security · compliance · incident · health
`wicked-garden-product`	Requirements, customer feedback, strategy, UX, accessibility, and design review	elicit · acceptance · analyze · strategy · ux-review
`wicked-garden-search`	Structural code search, lineage, blast-radius, and codebase intelligence	blast-radius · lineage · hotspots · service-map · index
`wicked-garden-smaht`	On-demand context assembly + session briefing from brain, search, and the event log	briefing · state · events-import · intent

Memory & search are provided by sibling plugins, not a wicked-garden domain: use wicked-brain:memory / wicked-brain:query for cross-session memory, and wicked-brain:search / wicked-brain:graph for code search and relationship graphs.

Quick start

Orient: invoke this skill's where-am-i action.
Build a feature: wicked-garden-archetype with build "add a user authentication system".
Re-derive "done" from evidence: wicked-garden-prove.
Review code: wicked-garden-engineering with review ./src.
Independent multi-model second opinion: wicked-garden-jam with council "should we adopt event sourcing here?".
Search code relationships: wicked-brain:search "handlePayment", then wicked-garden-search with blast-radius src/payments.py.
Store a decision: wicked-brain:memory (store mode).

How it works

Every prompt is classified into one or more archetypes by the UserPromptSubmit hook; each archetype owns its own phase shape, HITL discipline, and cost band (steering, not a fixed pipeline).
smaht assembles context on demand (pull-model) from brain, search, and the unified event log — there is no per-prompt push.
Specialist domains (engineering, platform, product, data, agentic, jam, search) provide deep expertise the harness routes into.
wicked-garden-prove re-derives an archetype's "done" through the evidence gate rather than trusting a "tests pass" claim.
State persists across sessions via wicked-brain memory, search indexes, the event log, and native tasks.

Getting more help

Invoke any domain skill with an action name (e.g. wicked-garden-engineering with review). Invoke wicked-garden-core with no action to return to this overview.

Action: where-am-i

Read-only query that prints a single compact manifest of the five storage roots used by wicked-garden dispatches. Subagents should include "invoke wicked-garden-core where-am-i first" as a directive instead of hand-enumerating paths — it costs fewer tokens and closes a class of path-mismatch bugs. Provenance: Issue #576.

Arguments: --json (JSON manifest, default) · --fence (wrap the JSON in a ```json fence for paste) · --env (substitute env-var forms such as $CLAUDE_PLUGIN_ROOT where the corresponding environment variable is present).

Invoke the helper script and stream its stdout to the user verbatim. This action is a thin wrapper — do not re-interpret the manifest.

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/where_am_i.py" "$@"

Output shape:

{
  "plugin_root": "/abs/path",
  "source_cwd": "/abs/path",
  "active_project_id": "string-or-null",
  "project_artifacts": "/abs/path/to/projects-or-specific-project",
  "brain": {"path": "/abs/path", "port": 4243},
  "bus_db": "/abs/path"
}

Any field that cannot be resolved emits null and logs a one-line note to stderr. The script never raises and is safe to invoke from any cwd. Graceful degradation: missing CLAUDE_PLUGIN_ROOT falls back to the checkout inferred from the script location; missing brain config emits "brain": null; missing bus DB emits "bus_db": null; no active crew project emits "active_project_id": null and points project_artifacts at the crew projects domain root.