@codihaus/claude-skills 1.6.8 → 1.6.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codihaus/claude-skills",
-  "version": "1.6.8",
+  "version": "1.6.9",
   "description": "Claude Code skills for software development workflow",
   "main": "src/index.js",
   "bin": {

package/skills/debrief/SKILL.md

@@ -68,6 +68,7 @@ Depending on mode:
 **New Project:**
 - BRD with use cases grouped by feature
 - Context document (stakeholders, constraints, users)
+- Market research (MVP/Standard/Advanced feature tiers)
 - Feature folders created
 - Architecture feasibility validated
 - Questionnaire for customer gaps
@@ -110,22 +111,72 @@ Detect automatically on start:
 
 ## Context Gathering
 
-Use `AskUserQuestion` to understand project context.
+Use `AskUserQuestion` to understand project context and scope preferences.
+
+### For New Project
+
+Ask 5 key questions using `AskUserQuestion`:
+
+**Q1: Project Type & Source Code**
+Options:
+- New project (no existing code)
+- Existing codebase (current folder)
+- Existing codebase (different folder)
+
+**Q2: Industry/Niche**
+Options:
+- SaaS B2B
+- SaaS B2C
+- E-commerce
+- Marketplace
+- Enterprise
+- Other
+
+**Q3: Target Users**
+Options:
+- Business users (B2B)
+- Consumers (B2C)
+- Internal users
+- Mixed
+
+**Q4: Known Constraints** (multi-select)
+Options:
+- Timeline constraint
+- Budget constraint
+- Compliance requirements
+- Integration requirements
+- None
+
+**Q5: Scope Tier Preference**
+Options:
+- **Core (3-5 use cases)** - MVP, essential features only
+- **Standard (8-12 use cases)** - Competitive parity, market standard
+- **Full (15+ use cases)** - Advanced features, differentiation
+
+This helps align on MVP vs market standard vs advanced features upfront.
+
+### For Add Feature
+
+Ask 2 questions:
+
+**Q1: Feature Name**
+What to call this feature (e.g., "billing", "notifications", "analytics")
 
-**For New Project, ask about:**
-- Project type (new vs existing codebase)
-- Industry/niche
-- Target users
-- Known constraints
-- Scope tier (Core/Standard/Full)
+**Q2: Scope for This Feature**
+Options:
+- **Core** - MVP/essential only
+- **Standard** - Competitive parity
+- **Full** - Advanced/differentiation features
 
-**For Add Feature, ask about:**
-- Feature name
-- Scope for this feature
+### For Existing Codebase
 
-**For Existing Codebase:**
-- Scan for docs, existing features, patterns
-- Reference `references/file-patterns.md` for scan patterns
+**If user indicates existing codebase:**
+- Scan for docs (CLAUDE.md, README, CONTRIBUTING)
+- Scan frontend files (.vue, .tsx, .jsx) to infer existing features
+- Use `references/file-patterns.md` for scan patterns
+- Summarize findings in `context.md`
+
+This codebase discovery informs which features already exist and what gaps remain.
 
 ## Duplicate Prevention
 
@@ -150,12 +201,62 @@ Use `AskUserQuestion` to understand project context.
 - Open questions
 - References from market research
 
-**Market research:**
-- Industry patterns
-- User flows
-- Compliance requirements
-- Documentation links
-- Output to `references.md`
+## Market Research
+
+**Why research:** Understand feature tiers and competitive landscape to inform scope decisions.
+
+**Combines with user's scope preference:**
+- User chose "Core" → Focus research on MVP features
+- User chose "Standard" → Research MVP + market standard features
+- User chose "Full" → Research all tiers including advanced/differentiation
+
+**What to research:**
+- Industry patterns (what similar products do)
+- User flows (standard UX patterns in this domain)
+- Compliance requirements (regulations, standards, must-haves)
+- Documentation links (references for engineers)
+
+**Expected insights organized by tier:**
+- **MVP Features (Must-Have):** Minimum to be viable product
+  - Example: Login, basic CRUD, core workflows
+- **Market Standard (Competitive Parity):** What competitors offer
+  - Example: SSO, notifications, exports
+- **Advanced Features (Differentiation):** What sets apart top products
+  - Example: AI suggestions, real-time collaboration, advanced analytics
+
+**Output:**
+- `references.md` - Organized by feature tier with links and notes
+- Use insights to:
+  - Validate user's scope choice (Core/Standard/Full)
+  - Prioritize use cases (Must/Should/Could)
+  - Guide customer conversations ("This is standard" vs "This is premium")
+
+**Format for references.md:**
+```markdown
+## {Feature} - Market Research
+
+### MVP (Must-Have)
+- Login/Signup - Industry standard: email + password + OAuth
+  - Reference: [Auth0 best practices](link)
+- Profile management - Every product has this
+
+### Market Standard (Competitive Parity)
+- SSO integration - 80% of competitors offer this
+  - Reference: [SAML guide](link)
+- Email notifications - User expectation
+
+### Advanced (Differentiation)
+- AI-powered recommendations - Only Competitor X has this
+  - Reference: [ML recommendation patterns](link)
+- Real-time collaboration - Top-tier feature
+```
+
+**How it guides use case creation:**
+- User chose "Core" → Create use cases for MVP tier only
+- User chose "Standard" → Create use cases for MVP + Market Standard tiers
+- User chose "Full" → Create use cases for all tiers
+
+This alignment ensures use cases match the agreed scope.
 
 ## BRD Structure