mikeparcewski/wicked-garden-jam
skills/jam/SKILL.md
Orchestrates AI-powered brainstorming sessions with dynamic focus groups. quick sessions are ephemeral (no storage). brainstorm and council sessions are tracked as native tasks (process) and stored in wicked-brain:memory (outcome). Use when: "brainstorm this", "explore ideas", "get different perspectives", "focus group", "what do you think about", "pros and cons", "quick check", "jam quick <idea>", "jam brainstorm <topic>", "jam council <topic> with options A/B/C", "multi-model evaluation", "council verdict", "jam revisit <decision>", "how did that decision work out".
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-jamInstall 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: Jul 12, 2026, 7:08 AM99.7s6 files scanned
SKILL.md
- name:
- wicked-garden-jam
- user-invocable:
- true
- description:
- |
- are tracked as native tasks (process) and stored in wicked-brain:
- memory (outcome).
- Use when:
- brainstorm this", "explore ideas", "get different perspectives",
- phase_relevance:
- ["clarify", "design"]
- archetype_relevance:
- ["*"]
Brainstorming Skill
Generate diverse perspectives through structured focus group sessions. This is the single entry point for the jam domain — route the user's request to one of the sub-actions below.
Routing
| Sub-action | When | How it runs |
|------------|------|-------------|
| quick | Gut-check, rapid exploration (~60s) | Inline — apply refs/quick.md directly |
| brainstorm | Important decisions, complex problems | Fork → wicked-garden-jam-brainstorm-facilitator |
| council | Defined options needing a rigid verdict | Fork → wicked-garden-jam-council |
| revisit | Record the outcome of a past decision | Inline — follow refs/revisit.md |
Progression:
quick(60s gut-check, ephemeral) →brainstorm(full session with evidence + decision storage) →council(structured verdict with external LLMs, final step). Key distinction:quick= ideation,brainstorm= free-form exploration,council= rigid evaluation of defined options.
Quick-Start
# Fast gut-check (ephemeral, ~60s)
jam quick "Should we use feature flags or config files here?"
# Full session with evidence and decision storage
jam brainstorm "Architecture approach for the new event bus"
# High-stakes council with external LLM challenge
jam council "Go/no-go on the v9 storage migration" --options "go, no-go"
# Record how a past decision worked out
jam revisit "event bus architecture"
Sub-action: quick
Args: <idea or question>
Quick 60-second exploration with 4 personas and 1 round. Run it inline — no dispatch:
Read("${CLAUDE_PLUGIN_ROOT}/skills/jam/refs/quick.md")— the single-pass rubric: 4 personas, 1 forced round, synthesis format (Key Insights / Action Items / Open Questions), hard constraints (no storage, no multi-AI, ≤200 words).- Apply the rubric directly to the topic. Do NOT run additional rounds. Do NOT store.
Sub-action: brainstorm
Args: <topic> [--personas list] [--rounds n] [--converge fast]
Full brainstorm with evidence-backed perspectives. The facilitator gathers evidence from the ecosystem (past decisions, code context, brainstorm outcomes) before assembling personas, so they argue from data — not just opinions. After synthesis, a structured decision record is automatically stored via wicked-brain:memory for organizational memory.
Convergence modes (pass through as convergence_mode):
- normal (default): Run all requested rounds (2-3), then synthesize.
- fast (
--converge fast): After each round, assess whether there is enough signal to synthesize; skip remaining rounds when personas converge.
Dispatch to the forked facilitator skill (it owns the convergence checks, native-task tracking, transcript storage, and bus events):
Skill(skill="wicked-garden-jam-brainstorm-facilitator",
args="Run a full brainstorm session on: {topic}. Options: {personas}, {rounds}, convergence_mode={converge|'normal'}.")
Sub-action: council
Args: <topic> --options "A, B, C" [--criteria "perf, cost, risk"]
Structured evaluation tool that uses real external LLM CLIs — registry-driven
(20+ CLIs: Codex, Gemini, Copilot, OpenCode, Pi, Aider, Goose, Amp, Droid, …;
see scripts/jam/agentic_cli_registry.py) — to get genuinely independent
model perspectives. Installed CLIs are detected AND usability-probed via
scripts/jam/detect_clis.py --probe (auth-revoked / unconfigured /
daemon-down CLIs are excluded). When fewer than 2 usable external CLIs are
present, council seats are filled with forked subagent seats so deliberation
always happens. Unlike brainstorm (free-form creative exploration), council is
a rigid evaluation tool for when you have defined options and need a
verdict.
Natural workflow: brainstorm → identify candidates → council → decide
Dispatch to the forked council skill:
Skill(skill="wicked-garden-jam-council",
args="Run a council evaluation on: {topic}. Options: {options}. Criteria: {criteria}.")
After the fork returns: read
${CLAUDE_PLUGIN_ROOT}/skills/jam/refs/council-verdict.md — it holds the
caller-side heuristics for acting on the verdict (when to proceed, when to
surface raw votes and pause for human adjudication, hard-gate archetype rules)
and the raw_votes output envelope contract
(consensus.py::build_council_output, WG_COUNCIL_OUTPUT=both|synth|raw).
Sub-action: revisit
Args: <topic or decision keyword>
Revisit a past brainstorm decision to record whether it was validated, invalidated, or modified. Light workflow — run it inline, no fork:
Read("${CLAUDE_PLUGIN_ROOT}/skills/jam/refs/revisit.md")— the 5-step workflow: recall the decision via wicked-brain:memory (--filter_type decision), display the decision summary, ask validated/invalidated/modified, store the outcome (tagsjam,outcome, importance high), report. Degrades gracefully when wicked-brain is absent.- Follow it step by step, waiting for the user's outcome answer in step 3.
Workers (forked skills)
skills/jam-brainstorm-facilitator/SKILL.md— multi-round, evidence gathering, transcript storage, decision recordskills/jam-council/SKILL.md— registry-driven multi-model council with isolation-enforced parallel dispatch
(jam quick runs inline via refs/quick.md — the former quick-facilitator
agent was retired; the ref is the sole, up-to-date rubric.)
References
refs/quick.md— the single-pass quick-jam rubric (personas, round, synthesis shape, hard constraints)refs/revisit.md— the decision-outcome revisit workflowrefs/council-verdict.md— caller-side verdict heuristics + raw_votes output contractrefs/facilitation-patterns.md— persona archetype pool, session length guidance, anti-patternsrefs/synthesis-patterns.md— synthesis structure, quality checklist, decision record format
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
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.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
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.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
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).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
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).
8SKILL.mdUpdated Jul 15, 2026