Product Manager Prd

What it does

When your agent uses it

• Tasks that involve PRD writing
• Tasks that involve User stories

Example prompts

• “/product-manager-prd”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Analyze Context: Review the existing codebase only to understand Technical Constraints and Integration Points that might affect the PRD.
2. 2Clarification Protocol: Ask 3-5 questions to better understand the user's needs, focusing on the WHY and WHO before the WHAT.
3. 3Structure the Document: Organize the PRD strictly according to the Mandatory PRD Template below.
4. 4Write User Stories: Use the Agile format: "As a [type of user], I want to [goal], so that [reason]." Assign a unique ID (e.g., GH-001).
5. 5Define Acceptance Criteria: List specific SMART criteria with a checklist format (- [ ]).
6. 6File Creation: Save the file using the format prd-feature--.md (e.g., prd-feature-login-system-08062026.md).
7. 7Issue Creation: After presenting the PRD, proactively ask if the user would like to create GitHub issues for the user stories. If they…

What it can do on your machine

Read from SKILL.md and the folder at commit c8c9159. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Manager Prd loads about 898 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 218 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~44

When it runs · the whole SKILL.md, loaded when a task matches

~898

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from GulajavaMinistudio/Mayukai-Theme at commit c8c9159, republished under its MIT licence (© GulajavaMinistudio). 218 words, ~898 tokens.

name

product-manager-prd

description

Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.

license

MIT

<!-- markdownlint-disable -->

## PRD: {project_title}

## 1. Product overview
### 1.1 Document title and version
- PRD: {project_title}
- Version: {version_number}

### 1.2 Product summary
- Brief overview (2-3 short paragraphs).

## 2. Goals
### 2.1 Business goals
- Bullet list.
### 2.2 User goals
- Bullet list.
### 2.3 Non-goals (Out of Scope)
- Bullet list.

## 3. User personas
### 3.1 Key user types
- Bullet list.
### 3.2 Basic persona details
- **{persona_name}**: {description}
### 3.3 Role-based access
- **{role_name}**: {permissions/description}

## 4. Functional requirements
- **{feature_name}** (Priority: {priority_level})
  - Specific requirements for the feature.

## 5. User experience
### 5.1 Entry points & first-time user flow
- Bullet list.
### 5.2 Core experience
- **{step_name}**: {description}
### 5.3 UI/UX highlights & Edge cases
- Bullet list.

## 6. Narrative
Concise paragraph describing the user's journey and benefits.

## 7. Success metrics
### 7.1 User-centric metrics
- Bullet list.
### 7.2 Business metrics
- Bullet list.
### 7.3 Technical metrics
- Bullet list.

## 8. Technical considerations (Input for Engineering Team)
### 8.1 Integration points
- Bullet list.
### 8.2 Data storage & privacy
- Bullet list.
### 8.3 Scalability & potential technical challenges
- Bullet list.

## 9. Milestones & sequencing
### 9.1 Project estimate & Team composition
- {Size}: {time_estimate} | {Team}: {roles involved}
### 9.2 Suggested phases
- **{Phase number}**: {description} ({time_estimate})

## 10. User stories & Acceptance Criteria

### 10.1. {User story title}
- **ID**: {GH-001}
- **Story**: As a [type of user], I want to [goal], so that [reason].
- **Acceptance criteria**:
  - [ ] {SMART Criteria 1}
  - [ ] {SMART Criteria 2}

© GulajavaMinistudio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/product-manager-prd of GulajavaMinistudio/Mayukai-Theme.

Open the folder on GitHubat commit c8c9159