Stats
Actions
Tags
Turn meetings into decisions, owners, open questions, and follow-ups.
How this skill is triggered — by the user, by Claude, or both
Slash command
/project-product-skills:decision-meeting-notesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this workflow to structure meeting notes to maximize value and ensure follow-through.
Use this workflow to structure meeting notes to maximize value and ensure follow-through.
Meeting: [Meeting Title]
Date: [Date]
Attendees: [Names/Roles]
Note Taker: [Name]
Duration: [Actual duration]
(Check off items as discussed)
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.
All action items should be:
Format:
Key points discussed organized by topic:
Topic 1: [Name]
Topic 2: [Name]
Questions that couldn't be answered:
Clear summary of what happens next:
During the meeting:
After the meeting:
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
Focus on:
Template additions:
Focus on:
Template additions:
Focus on:
Template additions:
Focus on:
Template additions:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub danielpradilla/project-product-skills --plugin project-product-skills