skills/smaht/intent/SKILL.md
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".
npx skillsauth add mikeparcewski/wicked-garden wicked-garden-smaht-intentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Session intent is the keystone of v10's steer-not-block model. It's auto-detected from the first turn's prompt and made sticky for the rest of the session. This skill lets you (or another skill on your behalf) override that auto-detection without using flags or fighting validators.
Four values, locked. To change the vocabulary, run a brainstorm — don't add ad-hoc.
| Intent | When to set | What fires |
|---|---|---|
| simple-edit | Trivial turns, status checks, continuations | Nothing — silent |
| feature | Building / fixing / refactoring code | Synthesis directive (wicked-brain pull) |
| research | Conceptual questions, "explain how", "why does" | Synthesis directive (wicked-brain pull) |
| rigor | Crew sessions, multi-phase work, audit trail required | Synthesis directive + active-chain context |
Invoke this skill (naturally — "set intent", "force rigor", "make the framework quiet", "what's my intent") with an optional value:
| Value passed | Effect |
|---|---|
| (none) | Show the effective current intent |
| rigor | Set an explicit override to full-crew rigor |
| simple-edit | Quiet the framework |
The value must be one of the four locked vocabulary terms above; anything else is rejected.
state.intent and state.intent_explicit=True in session state via scripts/_session.py::SessionState.update.<wg intent="X" t=N /> label in the next system-reminder so the model knows the user (or another skill) steered the framework.# Show or set session intent. Pass nothing to display; pass a value to override.
# Heredoc is single-quoted (<<'PY') so the shell does NOT expand $variables
# inside the Python source — the script reads CLAUDE_PLUGIN_ROOT via
# os.environ instead, which is inherited by the subprocess.
ARG="${1:-}"
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" - "$ARG" <<'PY'
import os
import sys
plugin_root = os.environ.get("CLAUDE_PLUGIN_ROOT")
if not plugin_root:
print("error: CLAUDE_PLUGIN_ROOT not set", file=sys.stderr)
sys.exit(1)
sys.path.insert(0, os.path.join(plugin_root, "scripts"))
from _session import SessionState
VALID = ("simple-edit", "feature", "rigor", "research")
arg = (sys.argv[1] if len(sys.argv) > 1 else "").strip()
state = SessionState.load()
if not arg:
eff = state.intent or "(not set; auto-detect runs on next turn)"
src = "explicit" if state.intent_explicit else "auto-detected" if state.intent else "n/a"
print(f"intent: {eff} ({src})")
sys.exit(0)
if arg not in VALID:
print(f"error: '{arg}' not in {VALID}", file=sys.stderr)
sys.exit(1)
state.update(intent=arg, intent_explicit=True)
print(f"intent set: {arg} (explicit override; sticky until session end)")
PY
crew:start skill could invoke this skill with rigor to ensure the rigor directive fires from turn 1, even if the user's first prompt was short.development
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.
tools
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 DOMAIN MODEL, not new code.
development
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).
tools
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).