wicked-garden 12.27.0

package/skills/product/listen/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: listen
+description: |
+  Aggregate customer feedback from discovered sources across support, surveys,
+  social, and direct channels. This skill should be used when the user needs to
+  gather customer voice data to inform product decisions or understand sentiment.
+
+  Use when: aggregating customer feedback from discovered sources, gathering
+  voice-of-customer data, or surveying sentiment across channels.
+phase_relevance: ["clarify", "design", "review"]
+archetype_relevance: ["*"]
+---
+
+# Listen Skill
+
+Aggregate customer feedback from multiple channels with automatic source discovery.
+
+## When to Use
+
+- Starting product requirements (gather customer needs)
+- Investigating customer pain points
+- Reviewing recent feedback
+- User asks to "listen to customers" or "what are customers saying"
+
+## Capability Discovery
+
+The skill automatically discovers available feedback capabilities and routes to whichever are present:
+
+| Capability | Discovers | Examples |
+|------------|-----------|----------|
+| `support-tickets` | CLI tools, APIs, exports providing ticket data | Ticket system CLIs, support platform exports, help desk APIs |
+| `customer-feedback` | Feedback platforms, voting systems, feature request tools | Feedback exports, product board files, customer labels in issue trackers |
+| `surveys` | Survey response exports (CSV, JSON) | Survey platform exports, NPS data files, form responses |
+| `conversations` | Chat and messaging data sources | Chat exports, messaging platform data |
+| `issue-tracking` | Bug/issue trackers with customer-reported items | Issue tracker CLIs with customer labels or tags |
+
+## Usage
+
+```bash
+# Listen to all available capabilities (auto-discovers sources)
+/wicked-garden:product:listen
+
+# Specific capability type
+/wicked-garden:product:listen --capability support-tickets
+
+# Time window
+/wicked-garden:product:listen --days 30
+/wicked-garden:product:listen --since "2026-01-01"
+
+# Filter by tags
+/wicked-garden:product:listen --tags bug,feature-request
+
+# Limit results
+/wicked-garden:product:listen --limit 50
+```
+
+## Aggregation Strategy
+
+1. **Discover Available Capabilities**
+   - Check for support-tickets capability (CLI tools, APIs)
+   - Check for customer-feedback capability (exports, voting systems)
+   - Check for surveys capability (CSV/JSON exports)
+   - Check for conversations capability (chat/messaging data)
+   - Check for issue-tracking capability (customer-labeled issues)
+   - Look for saved feedback in voice store
+
+2. **Fetch Recent Feedback**
+   - Default: Last 30 days
+   - Configurable timeframe
+   - Filter by source, tag, or keyword
+
+3. **Normalize Format**
+   - Extract: ID, source, date, author, content, sentiment
+   - Tag with categories (bug, feature, praise, complaint)
+   - Store in unified format
+
+4. **Store for Analysis**
+   ```
+   # Resolved via: sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_path.py" wicked-garden:product
+   {local_root}/wicked-garden:product/voice/feedback/{source}/{date}/{id}.md
+   ```
+
+## Unified Feedback Format
+
+```yaml
+---
+id: fb_abc123
+capability: support-tickets
+source_tool: detected-cli-tool
+source_id: ticket_456
+date: 2026-01-20T10:30:00Z
+author: customer@example.com
+segment: enterprise
+tags: [bug, mobile, performance]
+sentiment: negative
+priority: high
+---
+
+# {Title/Subject}
+
+## Original Feedback
+{Raw customer quote}
+
+## Context
+- Platform: iOS 16
+- Plan: Enterprise
+- User since: 2025-06-01
+```
+
+## Output
+
+Concise summary of aggregated feedback:
+
+```markdown
+## Listening Report: {Timeframe}
+
+### Capabilities Discovered
+- support-tickets: {X} items from {N} source(s)
+- customer-feedback: {Y} items from {N} source(s)
+- surveys: {Z} responses from {N} source(s)
+- Total: {N} feedback items across {M} capabilities
+
+### Quick Stats
+- Sentiment: {%pos} positive, {%neg} negative, {%neu} neutral
+- Top tags: {tag1} ({count}), {tag2} ({count})
+- Critical items: {count}
+
+### Recent Highlights
+1. **{Title}** - {source} - {date}
+   - Sentiment: {sentiment}
+   - Quote: "{excerpt}"
+
+{Top 5-10 items}
+
+### Next Steps
+Run /wicked-garden:product:analyze to extract themes and trends.
+```
+
+See [channels.md](refs/channels.md) for detailed capability integration patterns.
+
+## Integration
+
+### With wicked-brain
+```python
+# Recall past customer insights
+Skill(skill="wicked-brain:memory", args="recall \"customer feedback about {topic}\"")
+# Provide historical context
+```
+
+### With wicked-crew
+```python
+# Auto-trigger during product:requirements phase
+if event == "product:requirements:started":
+    feedback = listen(days=30, tags=["feature-request"])
+    inject_context(feedback)
+```
+
+## Storage
+
+Feedback stored at: `{local_root}/wicked-garden:product/voice/feedback/{source}/{YYYY-MM}/{id}.md` (resolve via `resolve_path.py wicked-garden:product`)
+
+## Error Handling
+
+- Source unavailable: Skip gracefully, report in summary
+- No recent feedback: Report "No feedback found in timeframe"
+- API rate limits: Cache and resume
+- Invalid format: Log warning, continue with valid items
+
+## Rules
+
+- Never expose customer PII beyond what's already in feedback
+- Respect source rate limits
+- Cache API responses when possible
+- Report source availability in output
+- Keep summaries concise (top 10 items max)

package/skills/product/listen/refs/channels.md

@@ -0,0 +1,220 @@
+---
+phase_relevance: ["clarify", "design", "review"]
+archetype_relevance: ["*"]
+---
+# Capability Integration Patterns
+
+Detailed integration patterns for customer voice capabilities.
+
+## support-tickets Capability
+
+Discovers tools that provide customer support ticket data.
+
+### Discovery Pattern
+
+```bash
+# Check for CLI tools with ticket management capabilities
+for cmd in zd zendesk intercom freshdesk desk; do
+  which "$cmd" 2>/dev/null && echo "support-tickets: $cmd available"
+done
+
+# Check for ticket export files
+find ~/Downloads -name "*tickets*.csv" -o -name "*support*.json" -mtime -90
+```
+
+### Data Extraction Pattern
+
+```bash
+# Generic CLI pattern (tool-agnostic)
+{discovered_cli} tickets list --status {states} --created_since {timeframe}
+{discovered_cli} ticket show {id}
+
+# Generic export pattern
+# Parse CSV/JSON for: id, created_date, customer, subject, description, status, tags
+```
+
+**Normalization**:
+- `id`: unique ticket identifier
+- `capability`: support-tickets
+- `source_tool`: discovered CLI/tool name
+- `author`: customer identifier
+- `date`: creation timestamp
+- `content`: subject + description + comments
+- `tags`: extracted from ticket metadata
+- `sentiment`: analyze from text
+
+## customer-feedback Capability
+
+Discovers tools that provide customer feedback, feature requests, and voting data.
+
+### Discovery Pattern
+
+```bash
+# Check for issue trackers with customer labels
+which gh 2>/dev/null && gh issue list --label customer --limit 1 2>/dev/null
+
+# Check for feedback platform exports
+find ~/Downloads -name "*feedback*.csv" -o \
+                 -name "*productboard*.csv" -o \
+                 -name "*canny*.json" -o \
+                 -name "*uservoice*.json" -mtime -90
+```
+
+### Data Extraction Pattern
+
+```bash
+# Issue tracker pattern (with customer labels)
+gh issue list --label customer --state all --limit 100
+gh issue view {number} --json body,comments,createdAt,author
+
+# Export file pattern
+# Parse for: title, description, votes, author, created_date, status
+```
+
+**Normalization**:
+- `id`: unique feedback identifier
+- `capability`: customer-feedback
+- `source_tool`: discovered source name
+- `votes`: if available (indicates priority)
+- `tags`: extracted from labels/categories
+- `sentiment`: analyze from content
+
+## surveys Capability
+
+Discovers survey and NPS response data from export files.
+
+### Discovery Pattern
+
+```bash
+# Check for survey exports (platform-agnostic)
+find ~/Downloads -name "*survey*.csv" -o \
+                 -name "*typeform*.csv" -o \
+                 -name "*nps*.csv" -o \
+                 -name "*responses*.csv" -mtime -90
+```
+
+### Data Extraction Pattern
+
+```bash
+# Generic CSV pattern
+# Look for columns: timestamp/submitted_at, email/respondent, question columns
+
+# Common structures:
+# - First column: timestamp
+# - Second column: respondent identifier
+# - Remaining columns: question responses
+```
+
+**Normalization**:
+- `id`: generated from timestamp + respondent
+- `capability`: surveys
+- `source_tool`: inferred from filename
+- `date`: submission timestamp
+- `content`: concatenated responses
+- `sentiment`: analyze from open-ended responses
+
+## conversations Capability
+
+Discovers chat and messaging platform data.
+
+### Discovery Pattern
+
+```bash
+# Check for conversation exports or cached data
+find $(sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_path.py" <domain>)/wicked-garden:product/voice/feedback/conversations/ -name "*.md" -o -name "*.json"
+
+# Check for messaging platform exports
+find ~/Downloads -name "*slack*.json" -o \
+                 -name "*discord*.json" -o \
+                 -name "*chat*.csv" -mtime -90
+```
+
+### Data Extraction Pattern
+
+```bash
+# Look for: timestamp, author, channel, message content, thread context
+```
+
+**Normalization**:
+- `id`: message or thread identifier
+- `capability`: conversations
+- `source_tool`: platform name
+- `date`: message timestamp
+- `content`: message text + thread context
+- `sentiment`: analyze from conversation tone
+
+## Direct Feedback
+
+Manually saved customer feedback from various channels.
+
+### Discovery Pattern
+
+```bash
+# Check voice store for direct feedback
+ls $(sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_path.py" <domain>)/wicked-garden:product/voice/feedback/direct/
+ls $(sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_path.py" <domain>)/wicked-garden:product/voice/feedback/social/
+```
+
+**Note**: Direct feedback and social mentions are typically manually collected and saved to the voice store.
+
+## Discovery Process
+
+1. **Check for support-tickets Capability**:
+   ```bash
+   # Discover ANY CLI tool that provides ticket data
+   for cmd in zd zendesk intercom freshdesk desk support; do
+     which "$cmd" 2>/dev/null && echo "support-tickets: $cmd"
+   done
+
+   # Check for ticket exports
+   find ~/Downloads -name "*ticket*.csv" -o -name "*support*.json" -mtime -90
+   ```
+
+2. **Check for customer-feedback Capability**:
+   ```bash
+   # Discover feedback platforms
+   which gh 2>/dev/null && gh issue list --label customer --limit 1
+
+   # Check for feedback exports
+   find ~/Downloads -name "*feedback*.csv" -o \
+                    -name "*productboard*.csv" -o \
+                    -name "*canny*.json" -mtime -90
+   ```
+
+3. **Check for surveys Capability**:
+   ```bash
+   # Discover survey exports
+   find ~/Downloads -name "*survey*.csv" -o \
+                    -name "*typeform*.csv" -o \
+                    -name "*nps*.csv" -mtime -90
+   ```
+
+4. **Check Voice Store**:
+   ```bash
+   ls -la $(sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_path.py" <domain>)/wicked-garden:product/voice/feedback/
+   ```
+
+5. **Report Availability**:
+   ```markdown
+   ### Available Capabilities
+   - support-tickets: 2 source(s) discovered
+   - customer-feedback: 1 source(s) discovered
+   - surveys: 3 export file(s) found
+   - Cached feedback: 150 items
+   ```
+
+## Rate Limiting
+
+Respect API limits for discovered tools:
+- Most support platforms: 100-500 req/min
+- Most issue trackers: 5000 req/hour
+- Always check tool-specific documentation
+
+Cache responses for 1 hour to avoid re-fetching.
+
+## Data Privacy
+
+- Never log full PII (hash emails if needed)
+- Redact sensitive content (credentials, payment info)
+- Store only feedback content, not personal data
+- Follow GDPR/privacy guidelines

package/skills/product/mockup/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: mockup
+description: |
+  Use when you need a quick ASCII wireframe or HTML mockup in-chat without Figma overhead.
+  NOT for production design work — use the figma plugin for that.
+portability: portable
+phase_relevance: ["clarify", "design", "review"]
+archetype_relevance: ["*"]
+---
+
+# Mockup Skill
+
+Generate wireframes and mockup designs in multiple fidelity levels — from quick
+ASCII sketches to HTML/CSS previews ready for developer handoff.
+
+## Output Format Selection
+
+| Format | Fidelity | Best For |
+|--------|---------|----------|
+| ASCII wireframe | Low | Quick ideation, flow discussion |
+| Markdown spec | Medium | Annotated layouts, component inventory |
+| HTML/CSS preview | High | Stakeholder review, dev handoff |
+| Component spec | Medium-High | Design system documentation |
+
+## ASCII Wireframes
+
+Fast, text-based layout sketches. Use for early ideation and flow discussion.
+
+```
+┌─────────────────────────────────────────┐
+│  [Logo]          [Nav Item] [Nav Item]  │
+│─────────────────────────────────────────│
+│                                         │
+│  ┌──────────────┐  ┌──────────────┐    │
+│  │              │  │              │    │
+│  │   [Image]    │  │   [Image]    │    │
+│  │              │  │              │    │
+│  │  Card Title  │  │  Card Title  │    │
+│  │  Description │  │  Description │    │
+│  │  [Button]    │  │  [Button]    │    │
+│  └──────────────┘  └──────────────┘    │
+│                                         │
+│  ─────── Section Heading ───────────   │
+│                                         │
+│  ████████████████████ [CTA Button]     │
+└─────────────────────────────────────────┘
+```
+
+### ASCII Symbol Guide
+
+```
+┌─┬─┐  Box borders
+│ │ │  Vertical dividers
+└─┴─┘  Box bottoms
+[...]   Button or interactive element
+{...}   Input field
+████   Image placeholder
+~~~~   Text content placeholder
+────   Horizontal rule / divider
+```
+
+## HTML/CSS Preview
+
+For higher-fidelity mockups, generate minimal HTML with embedded CSS using design tokens. Match the project's existing tokens if available (check `styles/tokens.css` or equivalent).
+
+Full template: `refs/templates.md` § HTML/CSS Preview.
+
+## Component Specs (Markdown)
+
+For developer handoff without visual preview, use the spec template. Sections: Anatomy, States table, Spacing tokens, Responsive Behavior, Accessibility Notes.
+
+Full template: `refs/templates.md` § Component Spec (Markdown).
+
+## Wireframe from Description
+
+When given a description, generate a wireframe in this sequence:
+
+1. **Identify layout pattern**: Single column, two-column, grid, sidebar+main
+2. **List components**: Header, nav, cards, forms, tables, modals
+3. **Arrange hierarchy**: Most important content first (F-pattern or Z-pattern)
+4. **Add interactions**: Buttons, links, inputs, toggles
+5. **Annotate**: Notes on behavior, states, responsive changes
+
+## Integration with Frontend Design
+
+When handing off to developers, attach handoff notes covering: design tokens to use, closest existing component, new patterns required, assets needed, animation specs.
+
+Template: `refs/templates.md` § Handoff Notes.
+
+## Output Checklist
+
+Before delivering a mockup:
+
+- [ ] All states shown (default, hover, error, empty, loading)
+- [ ] Mobile and desktop layouts included
+- [ ] Spacing annotated with token names (not pixel values)
+- [ ] Interactive elements clearly marked
+- [ ] Accessibility notes included
+- [ ] Open questions flagged for stakeholder input
+
+## Integration
+
+- **ux-review skill**: Pair mockups with the UX flow they support
+- **screenshot skill**: Compare mockup against built implementation
+- **visual-review skill**: Mockups set the standard for visual review
+- **engineering/frontend-design skill**: Coordinate component implementation

package/skills/product/mockup/refs/templates.md

@@ -0,0 +1,95 @@
+---
+phase_relevance: ["clarify", "design", "review"]
+archetype_relevance: ["*"]
+---
+# Mockup Templates
+
+Copy-paste templates for three common mockup deliverables: HTML/CSS preview, component spec, and handoff notes. See the SKILL.md selection table for when to use each output format.
+
+## HTML/CSS Preview
+
+Minimal HTML with embedded CSS using design tokens. Match the project's existing tokens if available (check `styles/tokens.css` or equivalent).
+
+```html
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="UTF-8">
+<meta name="viewport" content="width=device-width, initial-scale=1.0">
+<title>Mockup: {component name}</title>
+<style>
+  /* Design tokens */
+  :root {
+    --color-primary: #3b82f6;
+    --color-surface: #f9fafb;
+    --space-4: 1rem;
+    --space-6: 1.5rem;
+    --text-sm: 0.875rem;
+    --text-base: 1rem;
+    --text-lg: 1.125rem;
+    --radius: 0.5rem;
+  }
+  /* Component styles */
+  .card {
+    background: var(--color-surface);
+    border-radius: var(--radius);
+    padding: var(--space-6);
+  }
+</style>
+</head>
+<body>
+  <!-- mockup content -->
+</body>
+</html>
+```
+
+## Component Spec (Markdown)
+
+For developer handoff without visual preview:
+
+```markdown
+## Component: {Name}
+
+### Anatomy
+- **Container**: {background, border, border-radius, padding}
+- **Header**: {font-size, font-weight, color}
+- **Body**: {font-size, line-height, color}
+- **Action**: {button variant, size}
+
+### States
+| State | Visual Change |
+|-------|--------------|
+| Default | {description} |
+| Hover | {description} |
+| Active | {description} |
+| Disabled | {opacity: 0.5, cursor: not-allowed} |
+
+### Spacing
+- Internal padding: {token}
+- Gap between elements: {token}
+- External margin: {token or "handled by parent"}
+
+### Responsive Behavior
+- Mobile (<768px): {layout change}
+- Tablet (768–1024px): {layout change}
+- Desktop (>1024px): {base layout}
+
+### Accessibility Notes
+- Role: {semantic element or ARIA role}
+- Focus: {keyboard interaction}
+- Labels: {aria-label or visible label}
+```
+
+## Handoff Notes
+
+When handing off a mockup to developers:
+
+```markdown
+## Handoff Notes for {component}
+
+**Design tokens to use**: See `styles/tokens.css`
+**Closest existing component**: {component name in codebase}
+**New patterns required**: {list any novel patterns}
+**Assets needed**: {icons, images, fonts}
+**Animation**: {transition type, duration}
+```

package/skills/product/refs/a11y.md

@@ -0,0 +1,109 @@
+# Accessibility Audit Rubric (WCAG 2.1 AA)
+
+Apply this inline. Audit UI code/components against WCAG 2.1 Level AA. The four
+principles are **POUR**. For exhaustive checklists, ARIA patterns, keyboard and
+screen-reader guides, see the `accessibility` skill (`skills/product/accessibility/`).
+
+## Read the target first
+
+Focus on: HTML structure + semantic elements, ARIA attributes/roles, interactive
+element patterns, form labels + error handling, color definitions (for contrast).
+
+## POUR checklist
+
+**Perceivable**
+- [ ] Images have alt text (descriptive, or `alt=""` for decorative)
+- [ ] Color is not the sole information conveyor
+- [ ] Text contrast >=4.5:1 (normal), >=3:1 (large text 18pt+ / 14pt bold)
+- [ ] UI component / graphical-object contrast >=3:1
+- [ ] Content survives 200% zoom / text resize
+
+**Operable**
+- [ ] All interactive elements reachable via Tab
+- [ ] Tab order follows visual/logical order
+- [ ] No keyboard traps; modals have ESC exit + focus trap
+- [ ] Visible focus indicators on all interactive elements (`:focus-visible`)
+- [ ] No content flashing >3x/second
+- [ ] `tabindex` is 0 or -1 (avoid positive values)
+- [ ] Skip-to-main link present
+
+**Understandable**
+- [ ] `lang` attribute on `<html>`
+- [ ] Form errors identify the field and explain the fix
+- [ ] Labels describe purpose (not just appearance); inputs have associated `<label>`
+- [ ] Consistent navigation + identification
+- [ ] No unexpected context changes; required-field indicators
+- [ ] Confirmation on destructive actions
+
+**Robust**
+- [ ] Valid HTML; no duplicate IDs
+- [ ] ARIA only where native semantics are insufficient (first rule of ARIA: don't)
+- [ ] ARIA roles/states/properties correctly used; custom widgets expose name/role/value
+- [ ] Dynamic content uses `aria-live` (polite/assertive) / `role="status"|"alert"`
+
+## Semantic HTML
+
+Prefer `<header> <nav> <main> <article> <section> <aside> <footer>`; sequential
+heading hierarchy (`h1 -> h2 -> h3`, no skips); `<button>` for actions and `<a>`
+for navigation; `<form> <label> <fieldset> <legend>` for forms. Never `<div onclick>`.
+
+## Keyboard testing
+
+`Tab` / `Shift+Tab` (move), `Enter` (activate link/button), `Space` (button /
+checkbox), `Escape` (close dialog/menu), arrow keys (within tabs/menus/radios).
+Verify: reach all interactive elements, focus order = visual order, focus visible,
+no traps, skip link works, modals trap focus, arrows navigate menus/tabs.
+
+## Common violations to flag
+
+Missing alt text; insufficient contrast; inputs without labels; missing focus
+indicators; keyboard traps; skipped heading levels; buttons with no accessible
+name; non-semantic div/span buttons; autoplaying media without controls; timeout
+without warning; duplicate IDs; empty links/buttons; tables without headers;
+missing `lang`; incorrect ARIA.
+
+## Quick mode
+
+With `--quick`: return only Critical issues; skip the full checklist.
+
+## Output
+
+```markdown
+## Accessibility Audit: {target}
+
+**WCAG Level Achieved**: {Partial A | A | Partial AA | AA | AAA}
+**Score**: {1-5}   **Critical Issues**: {count}
+
+### Compliance by Principle
+| Principle | Status | Issues |
+|-----------|--------|--------|
+| Perceivable | ✓/⚠/✗ | {n} |
+| Operable | ✓/⚠/✗ | {n} |
+| Understandable | ✓/⚠/✗ | {n} |
+| Robust | ✓/⚠/✗ | {n} |
+
+### Issues
+#### Critical (blocks access)
+- **WCAG {criterion}**: {issue} — Location: {file:line} — Impact: {who is blocked} — Fix: {specific change}
+#### Major
+- {issue with recommendation}
+#### Minor
+- {enhancement}
+
+### Passed Checks
+- {what is accessible}
+
+### Priority Actions
+1. {must fix}  2. {should fix}
+```
+
+## Tooling
+
+Color contrast: compute the WCAG ratio against the AA thresholds (4.5:1 body,
+3:1 large text). For automated scanning, prefer axe DevTools / Lighthouse /
+WAVE / pa11y when available.
+
+## Resources
+
+WCAG 2.1 quickref (w3.org/WAI/WCAG21/quickref), ARIA Authoring Practices
+(w3.org/WAI/ARIA/apg), WebAIM, Inclusive Components. Legal: ADA, Section 508, EAA.