skills.rest
ilandahan
ilandahanCOMMUNITY
Explore all skills by this author →
GitHub

Product Manager Role Skill

Capture requirements, user stories, and acceptance criteria across product phases.

9|2|Updated Dec 10, 2025
Search Tags:#requirements#product-management#user-stories#acceptance-criteria#memory-system#phase-gates
One-click install
npx skills add https://github.com/ilandahan/AID --skill product-manager-role-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Product Manager Role Skill
Source: https://github.com/ilandahan/AID/tree/main/.claude/skills/memory-system/references/roles/product-manager
Command: npx skills add https://github.com/ilandahan/AID --skill product-manager-role-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill clarifies and enforces structured product management by capturing requirements, user stories, acceptance criteria, and defined scope across Discovery, PRD, Tech Spec, Development, and QA & Ship phases. It reduces ambiguity, improves alignment, and accelerates decision-making.

Core Features & Use Cases

  • Requirements definition: capture stakeholder needs, translate into PRD, and create traceable user stories.
  • Acceptance criteria & scope management: define clear success criteria and maintain scope alignment across teams.
  • Phase-driven collaboration: guides PM, Dev, and QA through all project phases with a memory of previous learnings.
  • Use Case: For a new feature, draft a PRD, map stakeholders, and generate acceptance tests that align with the phase gates.

Quick Start

Use the Product Manager Role Skill to draft a PRD outline for a new feature, including stakeholder map and acceptance criteria.

Frequently Asked Questions about Product Manager Role Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a PRD with traceable user stories and acceptance criteria?▼

To write a PRD with traceable user stories, you capture stakeholder needs and translate them into structured product requirements documentation. This enforces clear acceptance criteria and scope alignment across development and QA teams.

What is the best way to manage product scope across discovery and QA phases?▼

Managing product scope across phases requires enforcing structured documentation and defined phase gates from discovery through QA. This approach maintains scope alignment and improves cross-functional team collaboration.

Can I use this skill to map stakeholders and define feature scope?▼

Yes, you can use this skill to map stakeholders and define feature scope. It captures requirements and stakeholder needs, translating them into a structured PRD outline with clear success criteria.

Does product management scope alignment work without a memory system?▼

Product management scope alignment works better with a memory system that retains learnings across sessions. Without it, you risk losing traceability of acceptance criteria and previous phase decisions between project stages.

Related Skills

Explore More Product & Management Skills→
magnus919magnus919
40

product-discovery

Map stakeholders, conduct interviews, and distill requirements into formal specifications.

Community
Advanced
sunrain520sunrain520
72

spec-first:spec

Define functional requirements and acceptance criteria through a structured multi-phase workflow.

Community
Advanced
thepriceisrightthepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community
Advanced
HunterMcGrewHunterMcGrew

prism-user-stories

Generate structured user stories and requirements with acceptance criteria.

Community
Advanced