@codihaus/claude-skills 1.6.21 → 1.6.22

package/skills/debrief/references/codes.md

@@ -0,0 +1,135 @@
+# Reference Codes
+
+Quick reference for use case naming and codebase discovery.
+
+---
+
+## Use Case Group Codes
+
+Standard codes for `UC-{GROUP}-{NNN}-{slug}.md` naming.
+
+| Code | Domain | Examples |
+|------|--------|----------|
+| **AUTH** | Authentication | Login, logout, password reset, SSO |
+| **USER** | User Management | Registration, profile, settings |
+| **PAY** | Payments | Checkout, refunds, payment methods |
+| **SUB** | Subscriptions | Plans, upgrades, cancellation |
+| **BILL** | Billing | Invoices, receipts, statements |
+| **NOTIF** | Notifications | Email, push, in-app alerts |
+| **ADMIN** | Administration | Dashboard, settings, config |
+| **RPT** | Reporting | Analytics, exports, dashboards |
+| **INTG** | Integrations | API, webhooks, third-party |
+| **SRCH** | Search | Search, filters, browse |
+| **INV** | Inventory | Stock, catalog, products |
+| **ORD** | Orders | Cart, checkout, order history |
+| **SHIP** | Shipping | Delivery, tracking, returns |
+| **MSG** | Messaging | Chat, comments, threads |
+| **FILE** | Files | Upload, storage, sharing |
+| **TEAM** | Teams | Organizations, roles, permissions |
+| **ONBD** | Onboarding | Setup, tutorials, first-run |
+| **SUPP** | Support | Help, tickets, FAQ |
+
+**Custom codes**: Define project-specific codes in BRD README (3-5 chars, obvious meaning).
+
+**Principle**: Group by user intent, not implementation (PAY not STRIPE, USER not DATABASE).
+
+---
+
+## Codebase Discovery Patterns
+
+For existing codebase scanning (detect features and tech stack).
+
+### Frontend File Patterns
+
+**Include**:
+```
+**/*.vue              # Vue.js
+**/*.tsx, **/*.jsx    # React / Next.js
+**/pages/**/*         # Routes
+**/app/**/page.tsx    # Next.js App Router
+**/*.svelte           # Svelte
+**/*.component.ts     # Angular
+```
+
+**Exclude**:
+```
+node_modules/**, dist/**, build/**, .next/**, .nuxt/**
+*.min.js, *.bundle.js, *.chunk.js
+**/*.test.*, **/*.spec.*, __tests__/**
+```
+
+---
+
+### Feature Inference from Files
+
+Map file/folder names to features:
+
+| Pattern | Feature |
+|---------|---------|
+| `auth/`, `login.*`, `signin.*` | Authentication |
+| `user/`, `profile.*`, `account.*` | User Management |
+| `dashboard.*` | Dashboard |
+| `payment/`, `checkout.*`, `billing.*` | Payments |
+| `subscription/`, `plans.*` | Subscriptions |
+| `admin/` | Admin Panel |
+| `notification/`, `alerts/` | Notifications |
+| `search.*` | Search |
+| `cart.*`, `basket.*` | Shopping Cart |
+| `order/`, `orders/` | Orders |
+| `product/`, `catalog/` | Products |
+| `message/`, `chat/`, `inbox/` | Messaging |
+| `report/`, `analytics/` | Reporting |
+| `upload/`, `files/`, `media/` | File Management |
+| `team/`, `organization/` | Team Management |
+| `onboarding/`, `wizard/`, `setup/` | Onboarding |
+| `help/`, `support/`, `faq/` | Help/Support |
+
+---
+
+### Tech Stack Detection
+
+**Package files**:
+```
+package.json      → Node.js / JavaScript
+requirements.txt  → Python
+Gemfile           → Ruby
+go.mod            → Go
+Cargo.toml        → Rust
+composer.json     → PHP
+```
+
+**Framework detection** (from package.json dependencies):
+- `next` → Next.js
+- `nuxt` → Nuxt.js
+- `vue` → Vue.js
+- `react` → React
+- `@angular/core` → Angular
+- `svelte` → Svelte
+- `express` → Express.js
+- `nestjs` → NestJS
+
+---
+
+### Documentation Patterns
+
+Look for existing docs:
+```
+README.md, CLAUDE.md, CONTRIBUTING.md
+docs/**/*.md
+plans/**/*.md
+specifications/**/*.md
+.github/**/*.md
+```
+
+---
+
+## Discovery Strategy
+
+**For existing codebase**:
+1. Find package.json → Detect framework
+2. Glob frontend files → List pages/components
+3. Match patterns → Infer features
+4. Read docs (README, CLAUDE.md)
+5. Summarize in context.md
+
+**Output**: Features table with status (exists/missing), tech stack summary

package/skills/debrief/references/research.md

@@ -0,0 +1,227 @@
+# Market Research Guide
+
+**Mindset**: Evidence-based validation. Features classified by market standards, not personal judgment.
+
+**Methodology**: Comparison-first → Deep validation → Tier classification
+
+**Expected Outcome**: Features with tier (MVP/Standard/Advanced) backed by evidence (competitor presence, user demand, ecosystem signals).
+
+---
+
+## Quick Start (20%)
+
+### Comparison-First Approach
+
+**Start here** - one comparison page = 10 competitors analyzed:
+
+```
+"{category} comparison 2026"
+"best {category} alternatives 2026"
+"{product A} vs {product B} vs {product C}"
+```
+
+**Extract**:
+- Feature matrix (what features competitors have)
+- "Must-have" vs "nice-to-have" language
+- Deal-breaker features
+- Tier hints (free/pro/enterprise)
+
+**Result**: Feature list with initial tier hypothesis in 5 minutes.
+
+---
+
+### Tier Classification
+
+**MVP** (80%+ competitors, high demand):
+- Present in 8+ out of 10 competitors
+- Free tier placement
+- User complaints when missing
+- "Must-have" in comparisons
+
+**Standard** (60-80% competitors, expected):
+- Present in 6-8 out of 10 competitors
+- Pro tier placement
+- Expected by users, not differentiating
+- Competitive parity
+
+**Advanced** (<60% competitors, differentiator):
+- Present in <6 out of 10 competitors
+- Enterprise tier exclusive
+- "Wow factor" in reviews
+- Sets top products apart
+
+---
+
+### Evidence Format
+
+Per feature, collect:
+- **Competitor presence**: X/10 have it (%)
+- **Tier placement**: Free/Pro/Enterprise
+- **User demand**: Quote or stat
+- **Ecosystem signal**: Extensions, plugins, GitHub reactions
+
+**Confidence levels**:
+- High: 5+ sources, clear consensus
+- Medium: 2-4 sources, mostly aligned
+- Low: 1 source or conflicting → questionnaire
+
+---
+
+## Validation Sources (20%)
+
+### Comparison & Alternatives (Primary)
+
+**Why primary**: One page covers 5-10 competitors with feature matrices.
+
+**Where**:
+- Generic: Google "{category} comparison"
+- Curated: AlternativeTo, G2 Alternatives, SaaSHub, Slant
+
+**Look for**:
+- Feature comparison tables
+- "Why users switch" sections
+- Deal-breaker features
+
+---
+
+### Ecosystems (Gap Analysis)
+
+**Chrome Extensions**: `"{category} chrome extension"` → what users add
+**WordPress Plugins**: `site:wordpress.org/plugins "{feature}"` → active installs
+**Shopify Apps**: `site:apps.shopify.com "{category}"` → store count
+**GitHub Issues**: `"{category} open source" site:github.com` → feature requests with reactions
+
+**Signal**: Popular extensions/plugins = feature gap in core products
+
+---
+
+### User Signals (Validation)
+
+**Reddit**: `"{feature}" site:reddit.com/r/{subreddit}` → what users request
+**Reviews**: `"{product}" site:g2.com` → feature mentions in pros/cons
+**Forums**: Indie Hackers, Hacker News, Product Hunt → discussions
+
+**Signal**: User complaints, requests, praise patterns
+
+---
+
+### Competitor Direct (Context)
+
+**Product pages**: Feature lists, value props
+**Pricing pages**: Tier placement (free/pro/enterprise)
+**Google Business**: User reviews mentioning features
+
+**Signal**: Market positioning, feature bundling
+
+---
+
+## Research by Domain (80% - optional)
+
+### SaaS B2B
+**Focus**: G2, Capterra, GitHub, Chrome extensions
+**Key features**: SSO, team management, integrations, analytics
+
+### E-commerce
+**Focus**: Shopify Apps, WooCommerce plugins, Trustpilot
+**Key features**: Payment gateways, shipping, inventory, mobile
+
+### Marketplace
+**Focus**: Product Hunt, Reddit startups, app marketplaces
+**Key features**: Buyer/seller features, trust & safety, payments
+
+### Developer Tools
+**Focus**: GitHub (primary), Hacker News, Stack Overflow
+**Key features**: API design, CLI, integrations, documentation
+
+---
+
+## Methodology
+
+### Phase 1: Comparison Scan (5 min)
+
+**Goal**: Extract feature matrix from comparison pages.
+
+**Approach**:
+- Find 2-3 comparison/alternative pages
+- Extract features mentioned
+- Note universal vs premium features
+- List competitor names
+
+**Output**: Feature candidates with tier hints
+
+---
+
+### Phase 2: Deep Validation (5-10 min per feature)
+
+**Goal**: Validate tier with evidence from multiple source types.
+
+**Approach**: Cross-validate across source categories:
+- Comparison pages (initial)
+- Ecosystem (Chrome, WordPress, GitHub)
+- User signals (Reddit, reviews)
+- Competitor direct (pricing, features)
+
+**Output**: Tier classification with evidence and sources
+
+---
+
+## Questionnaire Strategy
+
+**Always generate questionnaire** with:
+
+**Validation questions** (customer confirms research):
+- "We found 9/10 competitors offer {feature}. Confirm you need this?"
+- "Market shows {feature} is {tier}. Agree with priority?"
+
+**Open questions** (genuine unknowns):
+- Business rules needing clarification
+- Integration requirements
+- Constraints and limits
+
+**Purpose**: Customer validates assumptions + fills gaps
+
+---
+
+## Common Patterns
+
+**Feature presence** → Tier hypothesis:
+- 100% presence → likely MVP
+- 80%+ presence → MVP or Standard
+- 60-80% presence → Standard
+- <60% presence → Advanced
+
+**Pricing placement** → Tier signal:
+- Free tier → likely MVP
+- Pro tier → likely Standard
+- Enterprise only → likely Advanced
+
+**User language** → Demand signal:
+- "Can't use without" → MVP
+- "Expected feature" → Standard
+- "Wow, amazing" → Advanced
+
+---
+
+## Expected Output
+
+Per feature:
+```
+Feature: SSO Login
+Tier: MVP
+Why: 90% competitor presence (9/10), enterprise requirement
+
+Evidence:
+- Competitors: 9/10 have it (Competitor A, B, C...)
+- Tier: Pro in 6/9, Free in 3/9
+- User demand: "SSO is why we chose this tool" - G2 reviews
+- GitHub: Issue #127 with 143 👍 reactions
+
+Sources:
+- [Comparison page](url)
+- [G2 reviews](url)
+- [GitHub issue](url)
+
+Confidence: High
+```
+
+Write to `features/{feature}/references.md` (feature-specific) or `brd/references.md` (project-wide).

package/skills/debrief/references/templates/brd-references.md

@@ -0,0 +1,80 @@
+# Project References (Project-Wide)
+
+> **Scope**: Industry, compliance, competitor overview
+> **Updated**: {YYYY-MM-DD}
+
+---
+
+## Industry Landscape
+
+**Category**: {SaaS B2B / E-commerce / Marketplace / etc.}
+**Market Size**: {if relevant}
+**Key Players**: {Top 5 competitors}
+
+**Industry Trends**:
+- {Trend 1 impacting product features}
+- {Trend 2 impacting product features}
+
+---
+
+## Compliance & Regulations
+
+### Required Compliance
+| Requirement | Applies To | Reference |
+|-------------|------------|-----------|
+| GDPR | User data, EU users | [Guide](url) |
+| PCI DSS | Payment processing | [Docs](url) |
+| SOC 2 | Enterprise customers | [Info](url) |
+
+### Industry Standards
+- {Standard 1 - why it matters}
+- {Standard 2 - why it matters}
+
+---
+
+## Competitor Overview
+
+### Leading Competitors
+
+**{Competitor A}**:
+- Position: {Market leader / Mid-tier / Niche}
+- Key differentiators: {What they're known for}
+- Pricing model: {Freemium / Subscription / etc.}
+- Link: [Website](url)
+
+**{Competitor B}**:
+- Position: {Position}
+- Key differentiators: {Features}
+- Pricing model: {Model}
+- Link: [Website](url)
+
+{Repeat for 3-5 competitors}
+
+---
+
+## Implementation Resources
+
+> **For Engineers**: General documentation (feature-specific docs in feature folders)
+
+### Platform Documentation
+| Technology | Link | Purpose |
+|------------|------|---------|
+| {Platform/Service} | [Docs](url) | {General purpose} |
+
+### Industry Examples
+| Company | Link | What to Learn |
+|---------|------|---------------|
+| {Company} | [Example](url) | {General pattern} |
+
+---
+
+## Notes
+
+**Project Goals**:
+- {High-level goal 1}
+- {High-level goal 2}
+
+**Constraints**:
+- {Project-wide constraint}
+
+**See Feature Folders**: `plans/features/{name}/references.md` for feature-specific research

package/skills/debrief/references/templates/feature-references.md

@@ -0,0 +1,98 @@
+# {Feature Name} - Market Research
+
+> **Feature**: {auth / billing / notifications / etc.}
+> **Group Code**: {AUTH / PAY / NOTIF / etc.}
+> **Research Date**: {YYYY-MM-DD}
+> **Confidence**: High / Medium / Low
+
+---
+
+## Research Summary
+
+**Competitors Analyzed**: {count} ({list names})
+**Evidence Sources**: {count} sources
+- Competitors: {count}
+- Ecosystem: {count}
+- User signals: {count}
+
+**Tier Distribution**:
+- MVP: {count} features
+- Standard: {count} features
+- Advanced: {count} features
+
+---
+
+## Features (Sequenced)
+
+### MVP (Must-Have)
+
+#### 1. {Feature Name}
+
+**Why MVP**: {1 sentence - e.g., "100% competitor presence, user complaint when missing"}
+
+**Evidence**:
+- Competitors: {X/Y} have it ({percentage}%)
+- Tier: {Free/Pro/Enterprise} in {count} competitors
+- User demand: "{Quote or stat}"
+- Ecosystem: {Chrome extension data / GitHub reactions / etc.}
+
+**Sources**:
+- [Competitor A](url)
+- [G2 Reviews](url)
+- [Reddit Thread](url)
+
+**Related UCs**: [[uc-xxx-001]], [[uc-xxx-002]]
+
+---
+
+#### 2. {Feature Name}
+
+**Why MVP**: {1 sentence}
+
+**Evidence**:
+- Competitors: {X/Y} ({percentage}%)
+- Tier: {Placement}
+- User demand: "{Quote/stat}"
+- Ecosystem: {Data}
+
+**Sources**:
+- [Source 1](url)
+- [Source 2](url)
+
+**Depends On**: #1 (must create before validate)
+**Related UCs**: [[uc-xxx-003]]
+
+---
+
+### Standard (Competitive Parity)
+
+#### 3. {Feature Name}
+
+{Same format as above}
+
+---
+
+### Advanced (Differentiation)
+
+#### 4. {Feature Name}
+
+{Same format as above}
+
+---
+
+## Implementation Resources
+
+> **For Engineers**: Links specific to this feature
+
+| Topic | Link | Purpose |
+|-------|------|---------|
+| {Service} {Feature} API | [Docs](url) | {Implementation} |
+
+---
+
+## Open Questions
+
+- {Question requiring customer input}
+- {Uncertainty needing validation}
+
+**See**: `questionnaire-{date}.xlsx` for full questions

package/skills/debrief/references/templates/use-case.md

@@ -0,0 +1,31 @@
+# UC-{GROUP}-{NNN}: {Title}
+
+**Story**: As a {user type}, I want {goal}, so that {benefit}
+**Tier**: MVP / Standard / Advanced
+**Depends on**: [[uc-xxx-nnn]] (if applicable)
+
+---
+
+## Must Have
+
+**Acceptance Criteria**:
+- {Critical success condition 1}
+- {Critical success condition 2}
+- {Critical success condition 3}
+
+**Business Rules**:
+- {Key constraint or limit}
+- {Required validation}
+- {Business policy}
+
+---
+
+## Open Questions
+
+- {Question for customer - impacts acceptance criteria}
+- {Question for customer - impacts business rule}
+
+---
+
+**Market Context**: {Brief evidence - e.g., "100% competitor presence, free tier"}
+**Full details**: Run `/dev-specs {feature}` for implementation flows and technical details