.claude/skills/scaffolding/SKILL.md
Component scaffolding toolkit for creating skills, agents, commands, and hooks within the unified wicked-garden plugin. Generates complete, valid structures that pass validation out-of-the-box. Use when creating new domain components, setting up boilerplate, or ensuring proper structure from the start.
npx skillsauth add mikeparcewski/wicked-garden scaffoldInstall 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.
Quick-start generator for wicked-garden domain components.
Generates production-ready component structures within the unified plugin:
All scaffolded components pass validation immediately.
python .claude/skills/scaffolding/scripts/scaffold.py
# Interactive prompts:
# > Component type? (skill/agent/command/hook)
# > Domain? (crew, engineering, platform, ...)
# > Name? (kebab-case)
# > Description?
# Result:
# Skill created: skills/crew/my-skill/
# Namespace: wicked-garden:crew:my-skill
# Skill
python .claude/skills/scaffolding/scripts/scaffold.py skill \
--name my-skill \
--domain crew \
--description "What this skill does"
# Agent
python .claude/skills/scaffolding/scripts/scaffold.py agent \
--name my-agent \
--domain platform \
--description "What this agent does" \
--tools "Read,Write,Bash"
# Command
python .claude/skills/scaffolding/scripts/scaffold.py command \
--name my-command \
--domain engineering \
--description "What this command does"
# Hook
python .claude/skills/scaffolding/scripts/scaffold.py hook \
--event PreToolUse \
--script validate-tool-use \
--description "Validates tool usage"
Components are placed in domain-specific subdirectories:
wicked-garden/ # Plugin root
├── skills/{domain}/{name}/ # Skills
│ └── SKILL.md
├── agents/{domain}/{name}.md # Agents
├── commands/{domain}/{name}.md # Commands
├── hooks/scripts/{name}.py # Hook scripts
└── hooks/hooks.json # Hook bindings (updated)
wicked-garden:{domain}:{command} (colon-separated)wicked-garden:{domain}/{agent} (slash for agent path)wicked-garden:{domain}:{skill} (colon-separated)When scaffolding a command, the tool checks if agents/{domain}/*.md exists:
command-with-agent.md template with Task(subagent_type=...) dispatchcommand.md templateThis ensures new commands follow the delegation standard from the start.
---
name: {skill-name}
description: |
What this skill does (capabilities).
Use when [trigger conditions and keywords].
---
# {Skill Title}
Brief introduction to the skill's purpose.
## Purpose
What problem this skill solves.
## Usage
### Example 1
\`\`\`python
# Code example
\`\`\`
## Patterns
Common patterns this skill enables:
- Pattern 1
- Pattern 2
## References
- Related docs
- Source files
---
description: What this agent specializes in
tools: ["Read", "Write", "Bash"]
---
# {Agent Name}
You are {agent-name}, specialized in {domain}.
## Expertise
Your core capabilities:
- Capability 1
- Capability 2
- Capability 3
## Working Style
How you approach tasks:
1. Step 1
2. Step 2
3. Step 3
## Quality Standards
What defines success:
- Standard 1
- Standard 2
## Constraints
What you avoid:
- Constraint 1
- Constraint 2
{
"hooks": [
{
"event": "{event}",
"script": "scripts/{script-name}.py",
"description": "{description}",
"enabled": true
}
]
}
#!/usr/bin/env python3
"""
{Event} hook for {plugin-name}.
Exit codes:
0 - Success, continue
2 - Blocking error (message sent to Claude)
Other - Non-blocking error (logged)
"""
import sys
import json
import os
def main():
# Read hook data from stdin
try:
data = json.loads(sys.stdin.read())
except json.JSONDecodeError:
print("Error: Invalid JSON input", file=sys.stderr)
sys.exit(1)
# Hook logic here
# Access: data['tool'], data['arguments'], data['context']
# Example validation
if data.get('tool') == 'Bash':
command = data.get('arguments', {}).get('command', '')
if 'rm -rf /' in command:
print("Blocked dangerous command: rm -rf /")
sys.exit(2) # Block execution
# Allow execution
sys.exit(0)
if __name__ == "__main__":
main()
The 16 domains in wicked-garden:
Workflow & Intelligence: crew, smaht, mem, search, jam, kanban Specialist Disciplines: engineering, product, platform, qe, data, delivery, agentic, persona
Domains are discovered dynamically from commands/ — new domains are valid immediately.
Available in all .tpl files:
| Variable | Description | Example |
|----------|-------------|---------|
| {name} | Component name (kebab-case) | risk-assessor |
| {Name} | Component name (Title Case) | Risk Assessor |
| {NAME} | Component name (UPPER_CASE) | RISK_ASSESSOR |
| {description} | Brief description | Assess project risks |
| {domain} | Domain name | qe |
claude-code-, anthropic-, official-)wicked- for marketplace consistencyscripts/commands/ for user-facing operationsskills/ for Claude expertiseagents/ for specialized subagents${CLAUDE_PLUGIN_ROOT} for paths"$VAR"python scripts/scaffold.py plugin \
--name wicked-perf-analyzer \
--description "Performance analysis and optimization" \
--with-commands analyze,optimize \
--with-skills analysis,optimization \
--with-agents optimizer \
--author "Your Name"
# Result:
# plugins/wicked-perf-analyzer/
# ├── .claude-plugin/plugin.json
# ├── commands/
# │ ├── analyze.md
# │ └── optimize.md
# ├── agents/
# │ └── optimizer.md
# ├── skills/
# │ ├── analysis/SKILL.md
# │ └── optimization/SKILL.md
# ├── scripts/
# │ └── setup.sh
# └── README.md
python scripts/scaffold.py skill \
--name validation-patterns \
--plugin wicked-memory \
--description "Input validation patterns for cache keys"
# Result:
# plugins/wicked-memory/skills/validation-patterns/
# └── SKILL.md
python scripts/scaffold.py hook \
--name PreToolUse \
--plugin wicked-crew \
--description "Validate tool use before execution" \
--script validate-tool-use.py
# Result:
# plugins/wicked-crew/hooks/
# ├── hooks.json (updated)
# └── scripts/
# └── validate-tool-use.py
.something-wicked/wicked-feature-dev/specs/something-wicked-v2/requirements.md (FR-005).something-wicked/wicked-feature-dev/specs/something-wicked-v2/design.md (tools/ section)CLAUDE.md (Naming Conventions section)CLAUDE.md (Component Patterns section)AGENTS.md before CLAUDE.md (general → specific). AGENTS.md is read-only.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).