@wipal/agent-team 1.0.0

package/.claude/skills/domain/product/requirements-gathering/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: requirements-gathering
+description: |
+  User requirements collection and analysis techniques. Use when: starting a new
+  project, gathering stakeholder needs, defining scope, or when user mentions
+  "requirements", "gather", "collect", "stakeholder", "needs", "scope".
+version: 1.0.0
+category: product
+tags:
+  - requirements
+  - discovery
+  - stakeholder
+  - scope
+depends_on: []
+recommends:
+  - user-stories
+used_by:
+  - user-stories
+  - sprint-planning
+---
+
+# Skill: Requirements Gathering
+
+## Core Principle
+**Understand before building.** The cost of misunderstanding grows exponentially over time.
+
+## Hard Rules
+
+1. **NEVER assume** - Always verify with stakeholders
+2. **NEVER skip documentation** - If it's not written, it doesn't exist
+3. **ALWAYS prioritize** - Not everything is "must have"
+4. **ALWAYS validate understanding** - Repeat back to stakeholders
+
+## Requirements Types
+
+| Type | Description | Example |
+|------|-------------|---------|
+| **Functional** | What the system does | "User can reset password" |
+| **Non-Functional** | How the system performs | "Page loads in < 2s" |
+| **Business** | Business goals | "Increase conversion by 10%" |
+| **Technical** | Tech constraints | "Must use PostgreSQL" |
+
+## Gathering Techniques
+
+### 1. Interviews
+```
+Questions to ask:
+- What problem are you trying to solve?
+- Who will use this feature?
+- What happens if this doesn't exist?
+- What would success look like?
+- What are the risks?
+```
+
+### 2. Workshops
+```
+Agenda:
+1. Problem statement (15 min)
+2. Current state analysis (30 min)
+3. Future state vision (30 min)
+4. Requirements brainstorming (45 min)
+5. Prioritization (30 min)
+```
+
+### 3. Observation
+```
+Watch users:
+- How they currently work
+- Pain points they experience
+- Workarounds they've created
+```
+
+## MoSCoW Prioritization
+
+| Priority | Meaning | Action |
+|----------|---------|--------|
+| **Must** | Critical for launch | Do first |
+| **Should** | Important but not critical | Do if time |
+| **Could** | Nice to have | Do if extra time |
+| **Won't** | Not this release | Backlog |
+
+## Requirements Document
+
+```markdown
+# Feature: User Authentication
+
+## Background
+Users need to securely access their accounts.
+
+## Business Goal
+Reduce support tickets related to password issues by 50%.
+
+## User Stories
+1. As a user, I want to log in with email/password
+2. As a user, I want to reset my password
+3. As a user, I want to use social login
+
+## Acceptance Criteria
+- [ ] Login works with email/password
+- [ ] Password reset sends email within 1 minute
+- [ ] Google/Facebook login available
+- [ ] All auth actions logged
+
+## Non-Functional Requirements
+- Login response time < 500ms
+- Support 1000 concurrent logins
+- 99.9% availability
+
+## Out of Scope
+- Biometric authentication
+- Multi-factor auth (Phase 2)
+
+## Dependencies
+- Email service
+- OAuth providers
+```
+
+## Common Mistakes
+
+| ❌ Mistake | ✅ Fix |
+|------------|--------|
+| Vague requirements | Specific, measurable |
+| No prioritization | Use MoSCoW |
+| Missing edge cases | Ask "what if?" |
+| No acceptance criteria | Define done |
+| Scope creep | Strict change control |
+
+## Checklist
+
+- [ ] All stakeholders identified
+- [ ] Requirements documented
+- [ ] Priorities assigned
+- [ ] Acceptance criteria defined
+- [ ] Dependencies identified
+- [ ] Risks documented
+- [ ] Stakeholder sign-off

package/.claude/skills/domain/product/roadmap-planning/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: roadmap-planning
+description: |
+  Product roadmap creation and strategic planning. Use when: creating roadmaps,
+  planning quarters, aligning stakeholders, or when user mentions "roadmap",
+  "strategy", "quarterly plan", "product direction".
+version: 1.0.0
+category: product
+tags:
+  - roadmap
+  - strategy
+  - planning
+  - quarterly
+depends_on:
+  - sprint-planning
+recommends: []
+used_by: []
+---
+
+# Skill: Roadmap Planning
+
+## Core Principle
+**Roadmaps are direction, not destination.** They guide decisions, not dictate them.
+
+## Roadmap Horizons
+
+| Horizon | Timeline | Focus |
+|---------|----------|-------|
+| **Now** | 0-3 months | Committed, detailed |
+| **Next** | 3-6 months | Planned, flexible |
+| **Later** | 6-12 months | Visionary, tentative |
+
+## Hard Rules
+
+1. **NEVER overpromise** - Roadmaps change
+2. **NEVER set dates for "Later"** - Use quarters/themes
+3. **ALWAYS tie to business goals** - Why are we doing this?
+4. **ALWAYS review regularly** - Monthly updates
+
+## Roadmap Template
+
+```markdown
+# Product Roadmap 2024
+
+## Vision
+Become the #1 platform for [domain] by [metric]
+
+## Strategic Themes
+1. **User Growth** - 3x registered users
+2. **Revenue** - $10M ARR
+3. **Retention** - 90% monthly retention
+
+## Q1 2024 (Jan-Mar)
+
+### Theme: Foundation
+| Initiative | Status | Owner |
+|------------|--------|-------|
+| User authentication | Committed | Team A |
+| Core feature X | Committed | Team B |
+| Infrastructure setup | Committed | DevOps |
+
+**Key Results:**
+- 1000 users onboarded
+- < 500ms response time
+- 99.9% uptime
+
+## Q2 2024 (Apr-Jun)
+
+### Theme: Growth
+| Initiative | Status | Owner |
+|------------|--------|-------|
+| Payment integration | Planned | Team A |
+| Mobile app MVP | Planned | Team B |
+| Analytics dashboard | Planned | Team C |
+
+## Q3-Q4 2024 (Jul-Dec)
+
+### Theme: Scale
+- International expansion
+- Enterprise features
+- AI/ML capabilities
+```
+
+## Prioritization Framework
+
+### RICE Score
+```
+RICE = (Reach × Impact × Confidence) / Effort
+
+Reach: How many users affected? (per quarter)
+Impact: How much will it move the metric? (0.25-3)
+Confidence: How sure are we? (0.5-1.0)
+Effort: Person-months required
+
+Example:
+Reach: 10,000 users
+Impact: 1 (medium)
+Confidence: 0.8 (high)
+Effort: 2 person-months
+
+RICE = (10000 × 1 × 0.8) / 2 = 4000
+```
+
+### Value vs Effort Matrix
+```
+        High Value
+            │
+   Quick    │   Big Bets
+   Wins     │
+────────────┼────────────
+   Fill-ins │   Money Pits
+            │
+        Low Value
+
+   Low Effort    High Effort
+```
+
+## Common Mistakes
+
+| ❌ Mistake | ✅ Fix |
+|------------|--------|
+| Date-driven | Outcome-driven |
+| Too detailed far out | Themes for later |
+| No business alignment | Tie to OKRs |
+| Set in stone | Review monthly |
+| Missing dependencies | Cross-team planning |
+
+## OKR Alignment
+
+```markdown
+## Objective: Grow user base significantly
+
+### Key Results:
+1. KR1: 10,000 new users by Q2
+2. KR2: 40% activation rate
+3. KR3: NPS score > 50
+
+### Initiatives:
+- Referral program (KR1)
+- Onboarding optimization (KR2)
+- Customer support improvements (KR3)
+```
+
+## Communication
+
+### Executive Summary
+```
+1. What we're building (1 sentence)
+2. Why it matters (business value)
+3. When it's coming (quarter)
+4. What we need (resources)
+```
+
+### Stakeholder Update
+```
+Since last update:
+- Shipped: [features]
+- Progress: [initiatives]
+- Blocked: [blockers]
+- Next: [upcoming]
+```
+
+## Checklist
+
+- [ ] Tied to business goals
+- [ ] Prioritized with framework
+- [ ] reviewed monthly
+- [ ] Communicated to stakeholders
+- [ ] Flexible to change

package/.claude/skills/domain/product/sprint-planning/SKILL.md

@@ -0,0 +1,151 @@
+---
+name: sprint-planning
+description: |
+  Sprint planning and estimation techniques for agile teams. Use when: planning
+  sprints, estimating stories, setting sprint goals, or when user mentions
+  "sprint", "planning", "estimate", "velocity", "story points".
+version: 1.0.0
+category: product
+tags:
+  - sprint
+  - planning
+  - estimation
+  - velocity
+depends_on:
+  - user-stories
+recommends: []
+used_by: []
+---
+
+# Skill: Sprint Planning
+
+## Core Principle
+**Plan with confidence, adapt with humility.** Sprints are predictions, not promises.
+
+## Sprint Planning Steps
+
+```
+1. Review backlog (before meeting)
+2. Set sprint goal
+3. Select stories
+4. Break down stories
+5. Estimate tasks
+6. Confirm commitment
+```
+
+## Hard Rules
+
+1. **NEVER overcommit** - Leave buffer for unknowns
+2. **NEVER add stories mid-sprint** - Protect scope
+3. **ALWAYS have a sprint goal** - Unifying purpose
+4. **ALWAYS involve the whole team** - Collective commitment
+
+## Estimation Techniques
+
+### Story Points (Fibonacci)
+```
+1  - Trivial, < 1 hour
+2  - Simple, 1-2 hours
+3  - Straightforward, half day
+5  - Moderate, 1-2 days
+8  - Complex, 2-4 days
+13 - Very complex, consider splitting
+21 - Epic, must split
+```
+
+### Planning Poker
+```
+1. Read story aloud
+2. Team discusses briefly
+3. Everyone reveals card simultaneously
+4. Discuss outliers
+5. Reach consensus
+```
+
+### T-Shirt Sizing
+```
+XS - < 2 hours
+S  - Half day
+M  - 1-2 days
+L  - 3-5 days
+XL - > 1 week (split it!)
+```
+
+## Velocity Calculation
+
+```
+Sprint 1: 32 points completed
+Sprint 2: 28 points completed
+Sprint 3: 35 points completed
+Sprint 4: 30 points completed
+
+Average Velocity = (32 + 28 + 35 + 30) / 4 = 31.25 points
+
+Recommended commitment: 28-30 points (85-95% of velocity)
+```
+
+## Sprint Goal Template
+
+```markdown
+# Sprint [Number] Goal
+
+## Theme
+Enable users to securely access their accounts
+
+## Key Deliverables
+1. User authentication (login/logout)
+2. Password reset flow
+3. Session management
+
+## Success Metrics
+- All stories completed
+- Zero critical bugs
+- Demo-ready by sprint end
+
+## Risks
+- Email service integration might be delayed
+- OAuth provider approval pending
+```
+
+## Sprint Backlog Template
+
+```markdown
+# Sprint [Number] Backlog
+
+| Story | Points | Owner | Status |
+|-------|--------|-------|--------|
+| AUTH-101 User login | 5 | @alice | In Progress |
+| AUTH-102 Password reset | 8 | @bob | Todo |
+| AUTH-103 Session timeout | 3 | @charlie | Done |
+
+**Total Points:** 16
+**Velocity Target:** 30
+**Remaining Capacity:** 14
+```
+
+## Common Mistakes
+
+| ❌ Mistake | ✅ Fix |
+|------------|--------|
+| Overcommitting | Leave 15% buffer |
+| No sprint goal | Define unifying theme |
+| Ignoring velocity | Use historical data |
+| Adding scope mid-sprint | Move to next sprint |
+| No task breakdown | Break into subtasks |
+
+## Daily Standup Format
+
+```
+1. What I completed yesterday
+2. What I'm working on today
+3. Any blockers
+```
+
+## Checklist
+
+- [ ] Sprint goal defined
+- [ ] Stories selected
+- [ ] Stories estimated
+- [ ] Team committed
+- [ ] Capacity considered
+- [ ] Risks identified

package/.claude/skills/domain/product/stakeholder-communication/SKILL.md

@@ -0,0 +1,162 @@
+---
+name: stakeholder-communication
+description: |
+  Stakeholder management and communication strategies. Use when: managing
+  expectations, reporting progress, handling conflicts, or when user mentions
+  "stakeholder", "communication", "status report", "expectations".
+version: 1.0.0
+category: product
+tags:
+  - stakeholder
+  - communication
+  - management
+  - reporting
+depends_on: []
+recommends: []
+used_by: []
+---
+
+# Skill: Stakeholder Communication
+
+## Core Principle
+**No surprises.** Stakeholders should hear news from you first, whether good or bad.
+
+## Stakeholder Types
+
+| Type | Interest | Influence | Strategy |
+|------|----------|-----------|----------|
+| **Sponsor** | High | High | Engage closely |
+| **Champion** | High | Low | Keep informed |
+| **Blocker** | Low | High | Manage carefully |
+| **Observer** | Low | Low | Keep aware |
+
+## Hard Rules
+
+1. **NEVER surprise stakeholders** - Communicate early
+2. **NEVER overpromise** - Under-promise, over-deliver
+3. **ALWAYS be transparent** - Especially about problems
+4. **ALWAYS tailor the message** - Technical vs business
+
+## Communication Plan
+
+```markdown
+# Stakeholder Communication Plan
+
+## Weekly
+- Team standup summary
+- Blockers and risks
+- Key metrics
+
+## Bi-weekly
+- Sprint review outcomes
+- Demo of completed work
+- Next sprint preview
+
+## Monthly
+- Roadmap progress
+- Budget status
+- Risk assessment
+
+## As Needed
+- Critical issues
+- Scope changes
+- Major milestones
+```
+
+## Status Report Template
+
+```markdown
+# [Project Name] Status - Week of [Date]
+
+## Executive Summary
+🟢 On Track / 🟡 At Risk / 🔴 Off Track
+
+## This Week
+- ✅ Completed: [items]
+- 🔄 In Progress: [items]
+- ⏳ Blocked: [items + blockers]
+
+## Next Week
+- [ ] [Planned items]
+
+## Key Metrics
+| Metric | Target | Actual | Trend |
+|--------|--------|--------|-------|
+| Velocity | 30 | 28 | ↓ |
+| Bugs | <5 | 3 | ✅ |
+| Coverage | >80% | 85% | ✅ |
+
+## Risks & Mitigations
+| Risk | Likelihood | Impact | Mitigation |
+|------|------------|--------|------------|
+| API delay | Medium | High | Started mock service |
+
+## Decisions Needed
+- [Decision 1] - Need approval by [date]
+
+## Ask
+- [Any resources or support needed]
+```
+
+## Handling Bad News
+
+### Framework: SBI
+```
+1. Situation: What happened (facts only)
+2. Behavior: What was done / not done
+3. Impact: What this means for the project
+```
+
+### Example
+```
+"I need to share some concerning news.
+
+Situation: The payment provider integration is delayed by 2 weeks.
+Behavior: They're waiting for compliance approval.
+Impact: We won't be able to accept payments until [date].
+
+Here's what we're doing about it:
+- Exploring alternative providers
+- Adjusting the launch timeline
+- Adding a manual payment option
+
+I wanted you to know now so we can plan accordingly."
+```
+
+## Common Mistakes
+
+| ❌ Mistake | ✅ Fix |
+|------------|--------|
+| Only reporting good news | Be transparent |
+| Too technical | Tailor audience |
+| Infrequent updates | Regular cadence |
+| No clear ask | Be specific |
+| Ignoring concerns | Address head-on |
+
+## Meeting Types
+
+### Sprint Review
+```
+1. Sprint goal review (5 min)
+2. Demo completed work (20 min)
+3. Metrics review (10 min)
+4. Q&A and feedback (15 min)
+5. Next sprint preview (10 min)
+```
+
+### Executive Update
+```
+1. Headline status (1 min)
+2. Key achievements (2 min)
+3. Risks and mitigations (3 min)
+4. Decisions needed (2 min)
+5. Q&A (7 min)
+```
+
+## Checklist
+
+- [ ] Stakeholders identified
+- [ ] Communication plan created
+- [ ] Regular cadence established
+- [ ] Bad news delivered early
+- [ ] Feedback incorporated