updated the product-management skills

product-management/README.md

@@ -13,11 +13,18 @@ claude plugins add knowledge-work-plugins/product-management
 This plugin gives you an AI-powered product management partner that can help with:
 
 - **Feature Specs & PRDs** — Generate structured product requirements documents from a problem statement or feature idea. Includes user stories, requirements prioritization, success metrics, and scope management.
-- **Roadmap Planning** — Create, update, and reprioritize your product roadmap. Supports Now/Next/Later, quarterly themes, and OKR-aligned formats with dependency mapping.
+- **Roadmap Planning** — Create, update, and reprioritize your product roadmap. Supports Now/Next/Later, quarterly themes, and OKR-aligned formats with dependency mapping and decision memos.
 - **Stakeholder Updates** — Generate status updates tailored to your audience (executives, engineering, customers). Pulls context from connected tools to save you the weekly update grind.
 - **User Research Synthesis** — Turn interview notes, survey data, and support tickets into structured insights. Identifies themes, builds personas, and surfaces opportunity areas with supporting evidence.
 - **Competitive Analysis** — Research competitors and generate briefs with feature comparisons, positioning analysis, and strategic implications.
 - **Metrics Review** — Analyze product metrics, identify trends, compare against targets, and surface actionable insights.
+- **Sprint Reviews** — Summarize sprint accomplishments with velocity metrics, demo highlights, and retrospective themes. Connects the dots between delivered work and product goals.
+- **Meeting Preparation** — Prepare for customer meetings, QBRs, and stakeholder calls with account context, talking points, risk assessment, and follow-up actions.
+- **Daily Briefs** — Start each day with a synthesis of overnight activity across Slack, project trackers, support tickets, and community channels.
+- **Prototyping** — Generate standalone interactive HTML prototypes from PRDs or feature descriptions. No dependencies, no build tools — just open in a browser.
+- **Release Notes** — Turn completed Jira tickets and PRD excerpts into polished, customer-facing release notes with proper categorization and tone.
+- **Feature Ideation** — Structure raw ideas from Slack threads, customer feedback, and brainstorms into validated feature concepts ready for a PRD.
+- **Executive Summaries** — Distill complex information into one-pagers (under 500 words) and TL;DRs (3-5 bullets) optimized for busy stakeholders.
 
 ## Commands
 
@@ -29,17 +36,30 @@ This plugin gives you an AI-powered product management partner that can help wit
 | `/synthesize-research` | Synthesize user research from interviews, surveys, and tickets |
 | `/competitive-brief` | Create a competitive analysis brief |
 | `/metrics-review` | Review and analyze product metrics |
+| `/daily-brief` | Synthesize overnight activity into a morning brief |
+| `/meeting-prep` | Prepare for customer meetings with context and talking points |
+| `/sprint-review` | Generate a sprint review summary with metrics and demos |
+| `/prototype` | Generate an interactive HTML prototype from a PRD or feature description |
+| `/release-notes` | Create customer-facing release notes from completed work |
+| `/feature-ideation` | Structure raw ideas into validated feature concepts |
+| `/one-pager` | Synthesize complex information into a one-page executive summary |
+| `/tldr` | Create a quick 3-5 bullet summary for Slack or email |
 
 ## Skills
 
 | Skill | What It Covers |
 |---|---|
-| `feature-spec` | PRD structure, user stories, requirements categorization, acceptance criteria |
-| `roadmap-management` | Prioritization frameworks (RICE, MoSCoW), roadmap formats, dependency mapping |
+| `feature-spec` | PRD structure, user stories, requirements categorization, acceptance criteria, idea structuring |
+| `roadmap-management` | Prioritization frameworks (RICE, MoSCoW), roadmap formats, dependency mapping, decision memos |
 | `stakeholder-comms` | Update templates by audience, risk communication, decision documentation |
 | `user-research-synthesis` | Thematic analysis, affinity mapping, persona development, opportunity sizing |
 | `competitive-analysis` | Feature comparison matrices, positioning analysis, win/loss analysis |
 | `metrics-tracking` | Product metrics hierarchy, goal setting (OKRs), dashboard design, review cadences |
+| `sprint-execution` | Sprint metrics, velocity analysis, demo preparation, burndown interpretation, retrospectives |
+| `meeting-preparation` | Account review methodology, talking point frameworks, risk identification, QBR planning |
+| `release-communication` | Customer-facing writing, changelog categorization, version conventions, deprecation lifecycle |
+| `executive-synthesis` | Pyramid principle, one-pager framework, TL;DR writing, audience adaptation |
+| `html-prototyping` | Design defaults, responsive layout patterns, interactive components, accessibility basics |
 
 ## Example Workflows
 
@@ -83,6 +103,36 @@ Claude: [Researches competitor onboarding approaches]
 Claude: [Generates brief with feature comparison, strengths/weaknesses, and strategic implications]
 ```
 
+### Sprint Review
+
+```
+You: /sprint-review
+Claude: What sprint are we reviewing? I'll also need the dates and team name.
+You: Sprint 42, Jan 6-17, Search Pod
+Claude: [Pulls completed tickets from project tracker, team discussion from Slack]
+Claude: [Generates sprint summary with velocity metrics, demo highlights, blockers, and customer feedback]
+```
+
+### Morning Brief
+
+```
+You: /daily-brief
+Claude: Good morning! What's your name and company? I'll synthesize what happened overnight.
+You: Jane, Acme Corp
+Claude: [Scans Slack channels, project tracker updates, support tickets]
+Claude: [Generates prioritized brief: what needs attention today, what's blocked, what shipped overnight]
+```
+
+### Interactive Prototype
+
+```
+You: /prototype
+Claude: What feature or flow should I prototype?
+You: A search results page with filters for content type, date range, and author
+Claude: [Generates a complete standalone HTML file with interactive filters, realistic data, and responsive layout]
+Claude: [Save as .html and open in your browser — no build tools needed]
+```
+
 ## Data Sources
 
 > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](CONNECTORS.md).

product-management/commands/daily-brief.md

@@ -0,0 +1,79 @@
+---
+description: Synthesize overnight activity into a morning brief with urgent items, progress, and recommended actions
+argument-hint: "<date or 'today'>"
+---
+
+# Daily Brief
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md).
+
+Synthesize overnight activity into a prioritized morning brief.
+
+## Workflow
+
+### 1. Understand the Context
+
+Ask the user:
+- What date is this brief for? (Default to today)
+- What team or product area to focus on?
+- Any specific concerns or priorities to watch for?
+
+### 2. Pull Context from Connected Tools
+
+If **~~chat** is connected:
+- Pull overnight messages from key product and engineering channels
+- Identify threads with unresolved questions or escalations
+- Surface decisions made asynchronously
+- Note any direct messages or mentions requiring the user's attention
+
+If **~~project tracker** is connected:
+- Pull sprint status and recent ticket updates
+- Identify items that changed status overnight (moved to blocked, completed, or at risk)
+- Surface blockers or items flagged as urgent
+- Check sprint burndown progress
+
+If **~~user feedback** is connected:
+- Pull recent support tickets and their severity
+- Identify trending issues or spikes in ticket volume
+- Surface any critical or P0 tickets opened overnight
+
+If **~~meeting transcription** is connected:
+- Pull notes from recent meetings
+- Identify action items assigned to the user
+- Surface any decisions that affect the user's priorities
+
+If no tools are connected, ask the user to paste:
+- Recent Slack messages or team chat activity
+- Sprint or project updates from Jira, Linear, or similar
+- Support tickets or customer feedback
+- Community posts or feature requests
+
+### 3. Generate the Brief
+
+Produce a structured morning brief. See the **sprint-execution** skill for sprint health indicators and the **meeting-preparation** skill for upcoming meeting context.
+
+- **TL;DR**: 2-3 sentence summary of the most important things from overnight
+- **Urgent Items**: Blockers, escalations, critical bugs — anything requiring action today
+- **Sprint Progress**: Current sprint status, notable completions, items at risk
+- **Customer Signals**: Key feedback from support and community channels
+- **Recommended Actions**: Top 3 things to focus on today, ordered by priority
+
+### 4. Follow Up
+
+After generating the brief:
+- Offer to draft responses to urgent items
+- Offer to create a standup update from the brief
+- Offer to investigate any concerning signals in more depth
+- Offer to prep for any meetings happening today
+
+## Output Format
+
+Use markdown with clear headers. Keep the brief scannable — the reader should get the essential picture in 60 seconds.
+
+## Tips
+
+- Prioritize ruthlessly. A brief that highlights everything highlights nothing.
+- Blockers and escalations always come first, before progress updates.
+- Customer signals are often the most strategically important part — do not bury them.
+- Recommended actions should be specific and time-bound, not vague suggestions.
+- If there is nothing urgent, say so. "No fires" is valuable information.

product-management/commands/feature-ideation.md

@@ -0,0 +1,86 @@
+---
+description: Structure raw ideas, feedback, and problems into concrete feature concepts with action plans
+argument-hint: "<idea or problem statement>"
+---
+
+# Feature Ideation
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md).
+
+Transform raw ideas into structured feature concepts. This is the upstream step before `/write-spec` — use it when an idea needs shaping before it is ready for a full PRD.
+
+## Workflow
+
+### 1. Understand the Raw Idea
+
+Ask the user what they are working with. Accept any of:
+- A raw idea ("We should add AI search")
+- A customer problem ("Users cannot find content quickly")
+- A feature request ("Customer X wants bulk export")
+- A Slack thread or brainstorm output ("Here is what the team discussed...")
+- A competitive observation ("Competitor Y just launched Z")
+
+### 2. Gather Signal
+
+Ask the user about the evidence behind this idea. Be conversational — do not dump all questions at once:
+
+- **Customer signal**: Who is asking for this? How many customers or users? How often does it come up?
+- **Problem severity**: How painful is the current state? What workaround do people use today?
+- **Strategic alignment**: Does this connect to a company or team goal?
+- **Competitive context**: Are competitors doing this? Is it table stakes or a differentiator?
+- **Constraints**: Any known technical, timeline, or resource constraints?
+
+### 3. Pull Context from Connected Tools
+
+If **~~chat** is connected:
+- Search for related Slack discussions about this idea
+- Pull threads where customers or teammates have mentioned the problem
+- Identify any prior decisions or discussions about this area
+
+If **~~user feedback** is connected:
+- Search for related support tickets or feature requests
+- Count how many customers have asked for something similar
+- Pull representative quotes from customer feedback
+
+If **~~product analytics** is connected:
+- Pull usage data related to the problem area
+- Search for behavioral signals (drop-offs, workarounds, low adoption)
+- Find data that quantifies the impact of the problem
+
+If these tools are not connected, work from what the user provides. Explicitly note where more data would strengthen the concept.
+
+### 4. Generate the Feature Concept
+
+Produce a structured feature concept document. See the **feature-spec** skill (especially the Idea Structuring section) for guidance on moving from raw idea to PRD-ready concept.
+
+- **Problem Definition**: What user problem does this solve? Who experiences it? How severe is it? (2-3 sentences, grounded in evidence)
+- **Customer Signal Summary**: What evidence supports this idea? Number of requests, support tickets, community votes, competitive pressure.
+- **Solution Options**: 2-3 approaches to solving the problem:
+  - **Option A**: Simplest version that addresses the core problem
+  - **Option B**: More comprehensive approach with broader impact
+  - **Option C**: Different angle or creative alternative
+  - For each: brief description, estimated effort, expected impact, key risk
+- **Assumptions to Validate**: What must be true for this to work? List 3-5 assumptions that should be tested before committing.
+- **Open Questions**: What do we not know yet? Tag each with who should answer.
+- **Recommended Next Step**: Is this ready for a PRD? Should we prototype first? Run customer interviews? Analyze data?
+- **2-Week Action Plan**: Specific steps to move this forward, with owners and dates.
+
+### 5. Follow Up
+
+After generating the concept:
+- Offer to turn it into a full PRD using `/write-spec`
+- Offer to create a prototype of the most promising option using `/prototype`
+- Offer to draft customer interview questions to validate assumptions
+- Offer to create a one-pager summary for stakeholder alignment
+
+## Output Format
+
+Use markdown with clear headers. Keep the document to 1-2 pages — this is a concept document, not a full spec. The goal is to structure thinking enough to make a go/no-go decision on further investment.
+
+## Tips
+
+- Do not fall in love with the first solution. Generate at least 2-3 options before recommending one.
+- The "Assumptions to Validate" section is the most important part. Every idea has hidden assumptions that can make or break it.
+- Be direct about signal strength. "2 customers mentioned this once" is different from "47 support tickets in 3 months."
+- The recommended next step should match the signal strength. Strong signal → write the PRD. Weak signal → validate first.
+- Keep the action plan to 2 weeks. If it takes longer to validate an idea, the idea may be too big or too vague.

product-management/commands/meeting-prep.md

@@ -0,0 +1,85 @@
+---
+description: Prepare for a customer meeting with account context, talking points, risks, and questions to ask
+argument-hint: "<account name and meeting type>"
+---
+
+# Meeting Prep
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md).
+
+Generate a meeting preparation pack with account context, talking points, and risk assessment.
+
+## Workflow
+
+### 1. Understand the Meeting
+
+Ask the user:
+- What account or customer is this meeting with?
+- What type of meeting? (QBR, check-in, escalation, executive briefing, sales call)
+- When is the meeting?
+- Who is attending from the customer side? What are their roles and priorities?
+- Any specific topics or concerns to address?
+
+### 2. Pull Context from Connected Tools
+
+If **~~user feedback** is connected:
+- Pull open support tickets for this account and their severity
+- Search for recent feature requests or feedback from this customer
+- Check support ticket volume and resolution time trends
+
+If **~~meeting transcription** is connected:
+- Pull notes from previous meetings with this account
+- Identify open action items from the last meeting
+- Surface recurring themes or concerns raised in past calls
+
+If **~~chat** is connected:
+- Search for recent internal conversations about this account
+- Pull any customer-facing thread activity
+- Identify any escalations or urgent issues discussed
+
+If **~~knowledge base** is connected:
+- Search for account plans, success plans, or internal notes
+- Pull any relevant case studies or reference materials
+- Find related feature specs or roadmap items
+
+If **~~project tracker** is connected:
+- Search for tickets tagged with this account or customer
+- Pull status on any committed deliverables for this customer
+
+If these tools are not connected, ask the user to paste:
+- Account health score, NPS, and contract details
+- Recent support tickets for this account
+- Previous meeting notes or Gong call summaries
+- Any relevant internal context
+
+### 3. Generate the Prep Pack
+
+Produce a structured meeting preparation document. See the **meeting-preparation** skill for detailed guidance on account review methodology, talking point frameworks, and risk identification.
+
+- **Account Snapshot**: Key facts — contract details, health score, tenure, usage summary
+- **Meeting Context**: Type, attendees with roles, and agenda
+- **Talking Points**: Proactive points (what you want to communicate), reactive points (what they will likely ask), and discovery questions (what you want to learn)
+- **Open Items**: Status of their feature requests, support tickets, and previous action items
+- **Risks**: Issues that could come up — escalations, delays, competitor mentions, renewal concerns
+- **Opportunities**: Expansion potential, case study opportunity, new stakeholder introduction
+- **Recommended Approach**: How to structure the conversation and what outcome to aim for
+
+### 4. Follow Up
+
+After generating the prep pack:
+- Offer to draft the meeting agenda to send in advance
+- Offer to prepare specific talking point scripts for sensitive topics
+- Offer to create a post-meeting summary template
+- Offer to prep a QBR deck if this is a quarterly review
+
+## Output Format
+
+Use markdown with clear headers. Keep the document actionable — the reader should be able to walk into the meeting confidently after a 5-minute read.
+
+## Tips
+
+- Know who is in the room. Different stakeholders care about different things — a CTO cares about technical roadmap, a VP of Ops cares about support and reliability.
+- Review previous meeting action items before the call. Nothing erodes trust faster than forgotten commitments.
+- Prepare at least 3 discovery questions. Meetings where you only present and never learn are wasted opportunities.
+- If there are known issues or risks, address them proactively rather than waiting for the customer to bring them up.
+- Have a clear outcome in mind for every meeting. What do you want to be true after the meeting that is not true before it?