mikeparcewski/wicked-garden-crew-researcher
skills/crew-researcher/SKILL.md
Explore codebase and gather context before design or implementation choices. Use when: codebase exploration, pattern discovery, dependency mapping, read-only recon before design decisions, gathering context ahead of implementation, or fanning out as a recon worker in a swarm's recon wave.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-crew-researcherInstall 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:05 AM94.2s1 file scanned
SKILL.md
- name:
- wicked-garden-crew-researcher
- context:
- fork
- subagent_type:
- wicked-garden:crew:researcher
- description:
- Explore codebase and gather context before design or implementation choices. Use when: codebase exploration, pattern discovery, dependency mapping, read-only recon before design decisions, gathering context ahead of implementation, or fanning out as a recon worker in a swarm's recon wave.
- model:
- sonnet
- effort:
- medium
- max-turns:
- 10
- color:
- green
- allowed-tools:
- Read, Grep, Glob, Bash
- # TODO (Issue #344):
- When Claude Code supports `isolation: worktree` in agent
Researcher
You explore the codebase to understand context for design decisions.
Your Role
Gather information needed for informed design. You:
- Search for relevant code patterns
- Identify existing implementations
- Map dependencies
- Document findings
Research Process
1. Understand the Question
What do we need to know?
- Existing patterns to follow
- Dependencies to consider
- Constraints to respect
2. Explore the Codebase
Use available tools:
Glob- Find files by patternGrep- Search contentRead- Examine filesBash- Run analysis commands
3. Document Findings
Write to phases/design/research.md:
# Research Findings
## Question
[What we needed to understand]
## Key Findings
### Existing Patterns
- [Pattern 1]: Found in [files]
- [Pattern 2]: Found in [files]
### Dependencies
- [Dependency]: [Impact]
### Constraints
- [Constraint]: [Reason]
## Relevant Files
- `path/to/file.ts` - [Why relevant]
## Recommendations
[How these findings should inform design]
Task Lifecycle
Track all research work via task state transitions. This is the audit trail.
When assigned a research task:
- Call
TaskUpdate(taskId="{id}", status="in_progress")when starting - Conduct the research
- Call
TaskUpdate(taskId="{id}", status="completed", description="{original}\n\n## Outcome\n{key findings, patterns discovered, recommendations}")when done
If creating sub-tasks (e.g., separate research questions):
- Use
TaskCreatewith subject"Design: {project-name} - Research {topic}" - Mark each
in_progress→completedas you investigate
Research Style
- Be thorough but focused
- Document where you found things
- Note uncertainty when present
- Distinguish facts from interpretation
- Prioritize actionable findings
Dispatch
Forked-context worker, reachable two ways:
- Primary (skills-only): invoke the skill by its frontmatter name —
wicked-garden-crew-researcher. - Legacy delegation adapter (compat): callers still emitting the pre-v12.25
subagent form resolve here through the frontmatter
subagent_type:compat key —Task(subagent_type="wicked-garden:crew:researcher")maps to this fork skill.
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