skills/product/analyze/SKILL.md
Sentiment analysis, theme extraction, and trend detection from customer feedback. Use when: analyzing customer feedback for sentiment, extracting themes from support or survey data, or detecting trends in voice-of-customer signal.
npx skillsauth add mikeparcewski/wicked-garden wicked-garden-product-analyzeInstall 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.
Extract themes, sentiment, and trends from aggregated customer feedback.
Tier-3 knowledge module behind the
analyzeaction of thewicked-garden-productdomain skill (skills/product/SKILL.md). Canonical invocation:/wicked-garden-product analyze [args]or plain natural language — the examples below use that form.
/wicked-garden-product listen# Analyze all recent feedback
/wicked-garden-product analyze
# Analyze specific theme
/wicked-garden-product analyze --theme "mobile experience"
# Analyze sentiment only
/wicked-garden-product analyze --sentiment negative
# Trend analysis
/wicked-garden-product analyze --trend "last-quarter"
# Segment analysis
/wicked-garden-product analyze --segment enterprise
Priority = (Frequency × Severity × Urgency) / Total_Feedback
See refs/algorithms.md for detailed scoring.
Load Feedback Data:
LOCAL_ROOT=$(sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_path.py" wicked-garden:product)
Then use the Glob tool to find feedback files:
Glob(pattern="**/*.md", path="${LOCAL_ROOT}/voice/feedback/")
Read individual files with the Read tool to load recent feedback.
Extract Themes:
Score Sentiment:
Detect Trends:
Segment Analysis:
## Analysis: {Topic or Timeframe}
### Sentiment Overview
- Net Sentiment: {+/-N} ({X}% positive, {Y}% negative)
- Strong Emotions: {count} highly positive, {count} highly negative
- Trend: {IMPROVING/DECLINING/STABLE} compared to previous period
### Top Themes (by priority)
1. **{Theme}** - Priority: {score}
- Frequency: {count} mentions ({%} of total)
- Sentiment: {positive/negative/mixed} ({intensity})
- Trend: {GROWING/STABLE/DECLINING} ({+/-X}% vs. baseline)
- Severity: {CRITICAL/HIGH/MEDIUM/LOW}
- Key quote: "{representative example}"
{Top 5 themes}
### Emerging Patterns
- **{New Theme}**: Recently appeared, {count} mentions
- **{Growing Theme}**: {X}% increase from last period
### Segment Insights
- **{Segment}**: {sentiment + top theme}
### Recommendations
{1-3 actionable recommendations based on analysis}
See refs/algorithms.md for detailed analysis algorithms.
# Triggered by product:requirements:started event
if event.type == "product:requirements:started":
# Analyze recent feedback for feature context
analysis = analyze(days=30, tags=["feature-request"])
emit_signal("voice:analysis:ready", analysis)
# Tag themes with related task IDs by reading native tasks from
# ${CLAUDE_CONFIG_DIR}/tasks/{session_id}/ and matching keywords
tasks = search_native_tasks(theme.keywords)
theme.related_tasks = tasks
Analysis results stored at: {local_root}/wicked-garden:product/voice/analysis/{theme}/{date}.md (resolve via resolve_path.py wicked-garden:product)
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).