claude-skills-for-pms

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Process meeting notes or transcripts into structured documents. Use when: summarize meeting, extract action items, meeting minutes, synthesize notes, process notes, create meeting summary, what were the decisions, extract action items from meeting.

Create concise one-page briefs for quick alignment and stakeholder decisions. Use when: one pager, feature brief, quick spec, feature proposal.

Use this skill when the user wants to plan and create engineering-ready stories directly in Jira. Trigger on: 'create jira stories', 'push stories to jira', 'write stories for this epic', 'create stories under [epic key]', 'make jira tickets for this feature', or any combination of story/ticket creation intent with a Jira destination. Also trigger when the user shares a feature brief, PRD, or Jira epic and asks to 'break it down into tickets', 'generate stories', or 'create the backlog'. Do NOT trigger for story generation to documents — use user-story-writer for .docx or .md output.

Generate release notes from Jira tickets, Confluence pages, or feature descriptions. Use when: release notes, changelog, what's new, feature announcement, release communication.

Generate a release readiness checklist from stories, acceptance criteria, NFRs, and risks

Use when the user wants to update the Customer Team Change Log Confluence page with recently shipped DLRUSER items. Trigger on: '/update-customer', 'update customer changelog', 'update customer change log', 'log what shipped for customer', 'what went to prod this week for customer'. Queries the DLRUSER Jira board for Done items and appends them to https://carsales.atlassian.net/wiki/spaces/DEAL/pages/3230072918/Customer+Team+-+Change+Log

Use when the user wants to update the Inventory changelog Confluence page with recently shipped DLRINV items. Trigger on: '/update-inventory', 'update inventory changelog', 'log what shipped', 'update the changelog', 'what went to prod this week'. Queries the DLRINV Jira board for Done items and appends them to https://carsales.atlassian.net/wiki/spaces/DEAL/pages/3928391694/Inventory+changelog

Use when reviewing, critiquing, or improving OKRs for a product or delivery team. Triggers on requests to review OKRs, check if key results are measurable, improve KR quality, or validate an OKR set before a planning cycle.

Critically examine an idea, plan, or decision by stress-testing assumptions, surfacing blind spots, and presenting steelman counterarguments

Generate a full Product Requirements Document (PRD) from a feature description, idea, or Jira ticket. Use when: create PRD, write PRD, product spec, requirements document, product requirements, define feature, I need a PRD for, help me write a product spec.

Run structured market research and competitor analysis for a product, feature, or market segment. Use when: market research, competitive analysis, competitor comparison, market sizing, industry analysis, trend analysis, competitive landscape, SWOT analysis, TAM SAM SOM, who are the competitors for, what's the market size.

Use when the user wants to log an architectural, product, or technical decision to Confluence. Trigger on: '/log-decision', 'log a decision', 'document a decision', 'create a decision log', 'record this decision', 'ADR'. Asks structured questions then creates a new child Confluence page with a two-column ADF decision log table.

Design product experiments beyond web A/B tests — pricing, features, operations, and more. Use when: product experiment, pricing experiment, feature experiment, pilot program.

Generate a release readiness checklist from stories, acceptance criteria, NFRs, and risks