role-pm

Generate size-calibrated requirements artifacts with scope and success criteria.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/tomwangowa/agent-skills --skill role-pm-tomwangowa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-pm
Source: https://github.com/tomwangowa/agent-skills/tree/main/role-pm
Command: npx skills add https://github.com/tomwangowa/agent-skills --skill role-pm-tomwangowa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill translates user goals into clear, actionable requirements artifacts, ensuring alignment and reducing ambiguity in project development.

Core Features & Use Cases

  • Size-Calibrated Requirements: Generates tailored artifacts (bullet lists, user stories, PRDs) based on project size (small, medium, large).
  • Risk Identification: Proactively identifies potential product risks.
  • Use Case: A startup founder has a high-level idea for a new app. They use this Skill to generate a structured set of requirements, scope, and success criteria, which are then handed off to the development team.

Quick Start

Use the role-pm skill to define requirements for a small project with the goal of building a basic user authentication system.

Frequently Asked Questions about role-pm

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

FAQPage Schema
How do I generate structured product requirements from high-level project goals?

To generate structured product requirements, you translate user goals into actionable scope, prioritization, and success criteria. This process ensures alignment and reduces ambiguity by producing tailored artifacts like user stories or PRDs for development teams.

Can I use user stories and PRDs for small project scope definition?

User stories and PRDs can be used for small project scope definition, but the format is calibrated by project size. Small projects use bullet lists, medium projects use user stories, and large projects require comprehensive PRDs with detailed risk analysis.

What is the best way to document project scope and identify risks early?

The best way to document project scope and identify risks is through size-calibrated requirements gathering. By defining actionable requirements and success criteria proactively, you surface potential product risks early, ensuring development teams understand boundaries and constraints.

Does this requirements gathering process support large scale projects with risk assessment?

This requirements gathering process supports large scale projects by generating comprehensive PRDs and performing detailed risk assessment. It calibrates the documentation format to match the project size, ensuring complex initiatives receive appropriate scope and risk analysis.

How to write actionable requirements for a development team?

To write actionable requirements for a development team, you define user goals into structured artifacts with clear scope and prioritization. This establishes unambiguous success criteria, reducing development friction and ensuring the final product matches expectations.