aigroup-workflow 1.0.1 → 1.1.1

package/skills/max/meeting-notes/SKILL.md

@@ -0,0 +1,266 @@
+---
+name: meeting-notes
+description: Structure and format meeting notes following PM best practices. Use when the user needs to create, format, or organize meeting notes, capture action items from meetings, or document discussions and decisions.
+metadata:
+  author: https://github.com/mohitagw15856/pm-claude-skills
+  domain: product-management
+  triggers: meeting notes, action items, meeting summary, discussion notes
+  role: project-manager
+  scope: documentation
+---
+
+# Meeting Notes Skill
+
+This skill structures meeting notes to maximize value and ensure follow-through.
+
+## Standard Meeting Notes Template
+
+### Meeting Header
+**Meeting**: [Meeting Title]  
+**Date**: [Date]  
+**Attendees**: [Names/Roles]  
+**Note Taker**: [Name]  
+**Duration**: [Actual duration]
+
+### Agenda
+- [ ] Topic 1
+- [ ] Topic 2
+- [ ] Topic 3
+
+*(Check off items as discussed)*
+
+### Decisions Made
+Clear documentation of decisions:
+
+**Decision**: [What was decided]  
+**Context**: [Why this decision]  
+**Owner**: [Who's responsible for executing]  
+**Deadline**: [When if applicable]  
+
+Use this format for each decision made.
+
+### Action Items
+All action items should be:
+- [ ] **[Action item]** - @Owner - Due: [Date]
+- [ ] **[Action item]** - @Owner - Due: [Date]
+
+Format:
+- Clear, specific action
+- Single owner (no "team" ownership)
+- Concrete deadline
+- Checkbox for tracking
+
+### Discussion Notes
+Key points discussed organized by topic:
+
+**Topic 1: [Name]**
+- Key point or discussion highlight
+- Important context or concern raised
+- Any data or information shared
+
+**Topic 2: [Name]**
+- Key discussion points
+- Decisions or conclusions reached
+
+### Open Questions / Follow-Up
+Questions that couldn't be answered:
+- **Question**: [What we need to know]
+- **Owner**: [Who will find out]
+- **By When**: [Deadline]
+
+### Next Steps
+Clear summary of what happens next:
+1. [Immediate next action]
+2. [Follow-up meeting if needed]
+3. [Any broader process to start]
+
+## Best Practices
+
+**During the meeting:**
+- Focus on decisions and action items over dialogue
+- Capture specific commitments, not general discussion
+- Note dissenting opinions on important decisions
+- Ask for clarity on vague commitments ("I'll look into it" → "I'll analyze the data and share findings by Friday")
+
+**After the meeting:**
+- Send notes within 2 hours while fresh
+- Tag action item owners (@mention them)
+- Include links to relevant documents
+- Follow up on overdue action items
+
+**What to capture:**
+✅ Decisions made
+✅ Action items with owners and deadlines
+✅ Key points of discussion
+✅ Open questions
+✅ Next steps
+
+**What to skip:**
+❌ Verbatim transcripts
+❌ Off-topic tangents
+❌ Preliminary discussion before decisions
+❌ Redundant information
+
+## Meeting Types & Adaptations
+
+### 1:1 Meetings
+Focus on:
+- Career development discussions
+- Feedback (both directions)
+- Current challenges
+- Action items for both parties
+
+Template additions:
+- **Recent Wins**: What's going well
+- **Challenges**: What's not going well
+- **Career Discussion**: Development topics
+- **Feedback**: For both parties
+
+### Sprint Planning
+Focus on:
+- Story acceptance criteria
+- Sizing/estimation decisions
+- Dependency identification
+- Sprint commitment
+
+Template additions:
+- **Sprint Goal**: What we're committing to
+- **Story Points**: Capacity and estimates
+- **Dependencies**: External blockers
+- **Definition of Done**: Acceptance criteria
+
+### Product Reviews
+Focus on:
+- Design decisions
+- User feedback discussed
+- Changes requested
+- Launch readiness assessment
+
+Template additions:
+- **Design Decisions**: What was approved/rejected
+- **User Feedback**: Key insights discussed
+- **Open Design Questions**: What needs iteration
+- **Launch Criteria**: Remaining requirements
+
+### Stakeholder Sync
+Focus on:
+- Status updates delivered
+- Concerns raised
+- Approvals given
+- Escalation needs
+
+Template additions:
+- **Status Overview**: High-level progress
+- **Approvals Obtained**: Sign-offs received
+- **Escalations**: Issues raised to stakeholders
+- **Next Sync**: When and what to cover
+
+## Example Meeting Notes
+
+```
+# Product Roadmap Review - Q1 2026
+**Date**: January 20, 2026  
+**Attendees**: Sarah (CPO), Mike (Eng Lead), Jennifer (Design), Tom (PM)  
+**Note Taker**: Tom  
+**Duration**: 45 minutes
+
+## Agenda
+- [x] Review Q1 planned features
+- [x] Discuss resource constraints
+- [x] Prioritization discussion
+- [x] Timeline alignment
+
+## Decisions Made
+
+**Decision**: Move multi-channel dashboard to Q2, prioritize mobile app improvements for Q1  
+**Context**: Customer feedback shows mobile experience is significantly impacting retention (65% of users primarily mobile). Engineering team can only tackle one major initiative this quarter.  
+**Owner**: Tom (PM) to communicate to stakeholders  
+**Deadline**: January 22
+
+**Decision**: Allocate 20% of engineering time to technical debt  
+**Context**: Accumulated tech debt is slowing feature development. Team velocity dropped 30% last quarter.  
+**Owner**: Mike (Eng Lead) to create tech debt backlog  
+**Deadline**: January 27
+
+**Decision**: Run mobile beta with 100 users before full launch
+**Context**: Need to validate improvements on diverse devices
+**Owner**: Jennifer (Design) to coordinate with QA
+**Deadline**: February 10
+
+## Action Items
+- [ ] **Update Q1 roadmap deck with new prioritization** - @Tom - Due: Jan 22
+- [ ] **Schedule alignment meeting with support team about dashboard delay** - @Tom - Due: Jan 24
+- [ ] **Create tech debt prioritization rubric** - @Mike - Due: Jan 27
+- [ ] **Run user testing on mobile designs** - @Jennifer - Due: Feb 3
+- [ ] **Document decision rationale for executives** - @Sarah - Due: Jan 23
+- [ ] **Identify 100 beta users for mobile** - @Tom - Due: Feb 1
+
+## Discussion Notes
+
+**Q1 Feature Prioritization**
+- Customer retention is #1 company priority this quarter
+- Mobile app NPS score is 6.2 (vs 8.1 for web)
+- Mobile accounts for 65% of daily active users
+- Multi-channel dashboard would take 8 engineering weeks
+- Mobile improvements estimated at 6 engineering weeks with higher ROI
+- Sales has 3 enterprise deals waiting on dashboard feature
+
+**Resource Constraints**
+- Currently 4 engineers available (down from 6 last quarter due to attrition)
+- Design team can support both initiatives but at reduced capacity
+- QA team needs 2 weeks for thorough testing on mobile
+- One engineer on loan to security team through February
+
+**Risk Discussion**
+- Delaying dashboard may impact enterprise sales (3 deals waiting)
+- Sarah noted: "We can position mobile improvements as foundation for enterprise features"
+- Mike raised concern about mobile tech stack stability - addressed through tech debt allocation
+- Need to communicate clearly with Sales about timeline change
+
+**Mobile Implementation Plan**
+- Week 1-2: Design refinements based on user feedback
+- Week 3-4: Engineering implementation
+- Week 5: Internal testing
+- Week 6: Beta with 100 users
+- Week 7: Full rollout
+
+## Open Questions
+- **Question**: What's the impact on enterprise pipeline if we delay dashboard?  
+  **Owner**: Sarah will check with Sales leadership  
+  **By When**: January 23
+
+- **Question**: Can we do a limited beta of dashboard for enterprise customers?  
+  **Owner**: Tom will explore MVP scope with Mike  
+  **By When**: January 25
+
+- **Question**: What's our plan if mobile improvements don't hit target metrics?
+  **Owner**: Tom will create contingency plan
+  **By When**: January 27
+
+## Next Steps
+1. Tom to send updated roadmap to leadership by EOD Wednesday (Jan 22)
+2. Team to begin sprint planning for mobile improvements next Monday (Jan 27)
+3. Follow-up meeting on Feb 1 to review progress and validate prioritization
+4. Sarah to present decision rationale to executive team on Jan 24
+
+---
+
+**Next Meeting**: February 1, 2026 - Progress Check-in
+**Notes Sent**: January 20, 2026 5:30 PM
+```
+
+## Notes Distribution
+
+**Subject Line Format**: "[Meeting Type] Notes - [Date] - [Key Topic]"
+
+Example: "Product Roadmap Review Notes - Jan 20 - Q1 Prioritization"
+
+**Recipients**:
+- All attendees
+- Anyone mentioned in action items
+- Anyone who requested notes
+
+**Follow-Up**:
+- Send reminder 3 days before action item due dates
+- Weekly summary of all open action items
+- Mark action items as complete and share updates

package/skills/max/prd-template/SKILL.md

@@ -0,0 +1,150 @@
+---
+name: prd-template
+description: Product Requirements Document creation following proven PM template structure. Use when the user asks to create, write, draft, or help with a PRD, product requirements document, product spec, feature specification, or product documentation for a new feature or product.
+metadata:
+  author: https://github.com/mohitagw15856/pm-claude-skills
+  domain: product-management
+  triggers: PRD, product requirements, feature spec, product documentation
+  role: project-manager
+  scope: documentation
+---
+
+# PRD Template Skill
+
+This skill helps create professional Product Requirements Documents following industry best practices.
+
+## Template Structure
+
+Every PRD should include these sections in order:
+
+### 1. Overview
+- **Problem Statement**: What problem are we solving? (2-3 sentences)
+- **Proposed Solution**: High-level description of what we're building (2-3 sentences)
+- **Success Metrics**: How we'll measure success (3-5 key metrics)
+
+### 2. Context & Background
+- **Why Now**: Why is this the right time?
+- **Strategic Alignment**: How does this align with company objectives?
+- **User Research Summary**: Key insights from research (if applicable)
+
+### 3. User Stories & Use Cases
+Format: "As a [user type], I want to [action] so that [benefit]"
+- Include 3-7 primary user stories
+- Add acceptance criteria for each
+
+### 4. Requirements
+**Functional Requirements:**
+- Must-have features (P0)
+- Should-have features (P1)
+- Nice-to-have features (P2)
+
+**Non-Functional Requirements:**
+- Performance expectations
+- Security considerations
+- Accessibility requirements
+
+### 5. Design & User Experience
+- Link to design mocks or wireframes
+- Key user flows
+- Edge cases and error states
+
+### 6. Technical Considerations
+- Architecture implications
+- Dependencies on other systems
+- Technical risks and mitigations
+
+### 7. Implementation Plan
+- **Phase 1 (MVP)**: What goes in first version
+- **Phase 2**: What comes next
+- **Phase 3**: Future enhancements
+
+### 8. Open Questions
+- Decisions that still need to be made
+- Stakeholders to consult
+- Research needed
+
+### 9. Appendix
+- Research links
+- Related documents
+- Competitive analysis
+
+## Writing Guidelines
+
+**Tone**: Clear, concise, actionable
+**Audience**: Engineers, designers, stakeholders
+**Length**: Aim for 3-6 pages for features, 8-12 for products
+
+**Best Practices:**
+- Use concrete examples over abstractions
+- Include "why" not just "what"
+- Make requirements testable
+- Link to supporting materials
+- Update as decisions are made
+
+## What Makes a Good PRD
+
+✅ **Do:**
+- Write from the user's perspective
+- Include specific success metrics
+- Address edge cases
+- Link to research and data
+- Make trade-offs explicit
+
+❌ **Don't:**
+- Write implementation details (that's tech spec)
+- Assume everyone has context
+- Leave requirements ambiguous
+- Skip the "why"
+- Forget about accessibility
+
+## Example PRD Opening
+
+```
+# PRD: Multi-Channel Customer Support Dashboard
+
+## Overview
+
+**Problem Statement**: Support teams are currently managing customer inquiries across email, chat, and social media using three separate tools, leading to delayed responses, duplicated work, and inconsistent customer experiences. On average, support agents waste 2.3 hours per day switching between tools and manually tracking conversation history.
+
+**Proposed Solution**: Build a unified dashboard that aggregates customer inquiries from all channels into a single interface, maintains conversation history across channels, and provides intelligent routing based on agent expertise and availability.
+
+**Success Metrics**:
+- Reduce average response time from 4 hours to 1 hour
+- Decrease tool-switching time by 80% (from 2.3 to <0.5 hours)
+- Improve customer satisfaction score from 3.8 to 4.5 (out of 5)
+- Increase support agent productivity by 35%
+
+## Context & Background
+
+**Why Now**: Customer satisfaction has declined 15% over the past 6 months, primarily due to slow response times. Our top competitor launched a unified support dashboard last quarter, and we're hearing about it in sales calls. Support team turnover is at 45% annually, with "tool complexity" cited as a top frustration.
+
+**Strategic Alignment**: This aligns with our Q1 company objective to "Improve customer retention by 10%" and our support team's OKR to "Reduce average handle time by 25%."
+
+**User Research Summary**: We conducted interviews with 12 support agents and observed 20 hours of support sessions. Key findings:
+- Agents spend 35% of their time finding context from previous interactions
+- 65% of escalations are due to lack of conversation history
+- Agents rated tool-switching as their #1 daily frustration (9.2/10 pain)
+- Current NPS for support experience is -12
+
+## User Stories & Use Cases
+
+**US1: Unified Inbox**
+As a support agent, I want to see all customer inquiries in one place so that I don't miss urgent requests and can prioritize effectively.
+
+Acceptance Criteria:
+- Inbox shows inquiries from email, chat, and social media
+- Inquiries are sorted by priority (urgent, high, normal, low)
+- Agent can filter by channel, customer, or status
+- Real-time updates when new inquiries arrive
+
+**US2: Cross-Channel Context**
+As a support agent, I want to see the full conversation history regardless of channel so that I can provide consistent, informed responses without asking customers to repeat themselves.
+
+Acceptance Criteria:
+- Timeline view shows all interactions chronologically
+- Each interaction displays channel, timestamp, and content
+- Customer profile shows demographics and account information
+- Previous issues and resolutions are accessible
+
+[Continue with 5-7 total user stories...]
+```

package/skills/max/stakeholder-update/SKILL.md

@@ -0,0 +1,225 @@
+---
+name: stakeholder-update
+description: Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives.
+metadata:
+  author: https://github.com/mohitagw15856/pm-claude-skills
+  domain: product-management
+  triggers: status update, progress report, stakeholder communication, executive summary
+  role: project-manager
+  scope: documentation
+---
+
+# Stakeholder Update Skill
+
+This skill creates effective status updates for executives and stakeholders following the BLUF (Bottom Line Up Front) principle.
+
+## Update Structure
+
+### 1. BLUF (Bottom Line Up Front)
+Start with the most important information:
+- **Status**: 🟢 On track / 🟡 At risk / 🔴 Blocked / ✅ Complete
+- **Key Takeaway**: One sentence summary of current state
+- **Action Needed**: What you need from stakeholders (if anything)
+
+### 2. Progress Summary
+Brief overview of accomplishments:
+- What shipped this period
+- Milestones achieved
+- Key metrics movement
+
+Keep to 3-5 bullet points maximum.
+
+### 3. Metrics Dashboard
+
+**Key Metrics**
+| Metric | Current | Target | Trend | Status |
+|--------|---------|--------|-------|--------|
+| [Metric name] | [Value] | [Target] | ↑/→/↓ | 🟢/🟡/🔴 |
+
+Include 3-5 most important metrics only.
+
+### 4. Risks & Blockers
+
+**High Priority Issues:**
+- **Issue**: Brief description
+- **Impact**: What's at stake
+- **Mitigation**: What you're doing about it
+- **Help Needed**: What stakeholders can do (if applicable)
+
+Only include issues that matter at executive level.
+
+### 5. Upcoming Milestones
+
+**Next 30 Days:**
+- Milestone (expected date)
+- Milestone (expected date)
+
+**Next 90 Days:**
+- Major milestone (month)
+- Major milestone (month)
+
+### 6. Decisions Needed (if applicable)
+- **Decision**: Clear description
+- **Options**: 2-3 options with pros/cons
+- **Recommendation**: What you recommend and why
+- **Timeline**: When decision is needed
+
+## Writing Guidelines
+
+**Tone**: Professional, concise, action-oriented
+**Length**: Keep under 1 page (or 2 minutes reading time)
+**Frequency**: Weekly for active projects, bi-weekly for maintenance
+
+**Executive Communication Principles:**
+
+1. **Lead with conclusions, not process**
+   - ❌ "We ran 5 experiments this week and analyzed the data..."
+   - ✅ "Conversion rate increased 15% from optimization work"
+
+2. **Focus on impact, not activities**
+   - ❌ "Held 12 customer interviews"
+   - ✅ "Identified #1 barrier to adoption (complexity of setup)"
+
+3. **Make problems visible early**
+   - Don't sugarcoat risks
+   - Propose solutions, not just problems
+   - Be specific about help needed
+
+4. **Use data to tell story**
+   - Quantify whenever possible
+   - Show trends, not just snapshots
+   - Connect metrics to business outcomes
+
+5. **Make it scannable**
+   - Use headers and bullet points
+   - Bold key information
+   - Use visual indicators (🟢🟡🔴, ↑→↓)
+
+## Status Guidelines
+
+**🟢 On Track**: Meeting all targets, no significant risks
+**🟡 At Risk**: Potential issues that could impact delivery
+**🔴 Blocked**: Critical issues preventing progress, needs intervention
+
+## Example Update
+
+```
+# Product Update: Customer Onboarding Redesign
+**Week of Jan 20, 2026**
+
+## BLUF
+**Status**: 🟡 At Risk  
+**Key Takeaway**: New onboarding flow is performing well in tests (+35% completion), but launch delayed one week due to integration issues with billing system.  
+**Action Needed**: Decision needed on whether to launch onboarding separately or wait for billing integration fix.
+
+## Progress Summary
+- Completed user testing with 24 participants (94% positive feedback)
+- Implemented first-time user experience improvements
+- Resolved 12 of 15 bugs identified in QA
+- Engineering allocated resources to billing integration fix
+
+## Key Metrics
+| Metric | Current | Target | Trend | Status |
+|--------|---------|--------|-------|--------|
+| Onboarding Completion | 45% | 60% | → | 🟡 |
+| Time to First Value | 4.2 min | 3.0 min | ↓ | 🟢 |
+| Setup Support Tickets | 45/week | <30/week | ↓ | 🟢 |
+| User Activation Rate | 52% | 65% | → | 🟡 |
+
+## Risks & Blockers
+
+**HIGH: Billing System Integration Delay**
+- **Impact**: Prevents users from completing onboarding flow; delays launch by 1-2 weeks
+- **Root Cause**: API deprecation by payment processor, requires code rewrite
+- **Mitigation**: Engineering team reallocated resources, fix ETA Feb 3
+- **Decision Needed**: Launch onboarding without payment integration or wait for fix? (See below)
+
+**MEDIUM: Mobile Testing Coverage**
+- **Impact**: Some edge cases on older Android devices not tested
+- **Mitigation**: Partnering with QA to expand test matrix; running beta with internal users on diverse devices
+
+## Upcoming Milestones
+
+**Next 30 Days:**
+- Resolve billing integration (Feb 3)
+- Launch onboarding redesign (Feb 5 or Feb 12 depending on decision)
+- Begin measuring impact on conversion (Feb 12)
+
+**Next 90 Days:**
+- Iterate based on production data (March)
+- Extend to mobile app (April)
+- Launch advanced features (May)
+
+## Decision Needed
+
+**Should we launch onboarding separately from billing integration?**
+
+**Option A: Launch Now (Recommended)**
+- Pros: Get 35% completion rate improvement to users immediately, gather production data, maintain momentum
+- Cons: Users need to complete payment in old flow, slightly disjointed experience
+- Timeline: Launch Feb 5
+
+**Option B: Wait for Billing Fix**
+- Pros: Fully integrated experience from day one, no technical debt
+- Cons: Delays benefits by 2 weeks, Q1 metric targets at risk, team momentum lost
+- Timeline: Launch Feb 12
+
+**Recommendation**: Option A. The onboarding improvements are valuable independently, and the old payment flow works fine. Waiting risks missing Q1 targets and delays validated improvements from reaching users.
+
+**Timeline**: Need decision by Jan 22 for Feb 5 launch.
+
+---
+
+**Questions?** Reply to this email or ping me on Slack.
+```
+
+## Frequency Guidance
+
+**Daily standups**: 
+- Ultra-brief (3 bullets)
+- What shipped yesterday
+- What's shipping today
+- Blockers
+
+**Weekly updates**:
+- Use full template above
+- Focus on progress and risks
+- Keep to 1 page
+
+**Monthly reviews**:
+- Deeper metrics analysis
+- Strategic reflections
+- Quarterly goal progress
+- Longer format (2-3 pages) acceptable
+
+**Quarterly business reviews**:
+- Comprehensive analysis
+- Trends over time
+- Strategic recommendations
+- Presentation format
+
+## Adaptation by Audience
+
+### For C-Suite
+- Lead with business impact
+- Connect to company OKRs
+- Focus on strategy and outcomes
+- Minimize technical details
+
+### For Product/Engineering Leadership
+- Include technical context
+- Show sprint/milestone progress
+- Discuss architecture implications
+- Reference technical debt
+
+### For Cross-Functional Teams
+- Balance technical and business context
+- Highlight dependencies
+- Call out collaboration needs
+- Make asks explicit
+
+### For Board/Investors
+- Focus on metrics and traction
+- Competitive positioning
+- Market opportunities
+- Financial implications