PM Mean
Purpose
Write PRDs (Product Requirements Documents) for MEAN stack web applications and validate deliverables against acceptance criteria. This skill bridges user requests and developer execution.
Key Patterns
PRD Structure
Every PRD must include:
- Overview — What the app does, who it's for, core value proposition
- Features — Numbered list (F1, F2...), each with: description, user story, acceptance criteria
- Data Model Summary — Key entities and relationships (high-level, not full schema)
- API Summary — Key endpoints grouped by resource (high-level, not full contracts)
- UI Summary — Key pages/views and user flows (high-level, not full component tree)
- Technical Constraints — Auth method (JWT for MEAN), deployment target, performance requirements
- Priorities — MoSCoW (Must/Should/Could/Won't) for features
User Story Format
As a [role], I want to [action] so that [benefit].
Acceptance Criteria:
- Given [context], when [action], then [result]
Acceptance Review Pattern
When reviewing deliverables (final pipeline phase):
- Read the original PRD
- For each feature: check if acceptance criteria are met
- Produce a pass/fail verdict per feature
- Flag missing features, partial implementations, and deviations
Conventions
- Write for developers, not stakeholders — be specific, not vague
- Every feature MUST have testable acceptance criteria (Given/When/Then)
- Use REST resource naming: plural nouns, lowercase (/api/users, /api/posts)
- Specify auth requirements per feature (public, authenticated, admin)
- Include error scenarios in acceptance criteria
- Number features for easy reference (F1, F2, F3...)
Knowledge Strategy
- Patterns to capture: Successful PRD structures, common MEAN features (auth, CRUD, real-time), good acceptance criteria examples
- Examples to collect: Completed PRDs that led to successful implementations
- Update permission: Agents may freely add/update files in
references/. Changes to SKILL.md or scripts/ require user approval.
1---2name: pm-mean3description: Product management for MEAN stack apps. Use when writing PRDs, defining features, acceptance criteria, or reviewing deliverables for MongoDB + Express + React + Node.js projects.4---56# PM Mean78## Purpose910Write PRDs (Product Requirements Documents) for MEAN stack web applications and validate deliverables against acceptance criteria. This skill bridges user requests and developer execution.1112## Key Patterns1314### PRD Structure15Every PRD must include:161. **Overview** — What the app does, who it's for, core value proposition172. **Features** — Numbered list (F1, F2...), each with: description, user story, acceptance criteria183. **Data Model Summary** — Key entities and relationships (high-level, not full schema)194. **API Summary** — Key endpoints grouped by resource (high-level, not full contracts)205. **UI Summary** — Key pages/views and user flows (high-level, not full component tree)216. **Technical Constraints** — Auth method (JWT for MEAN), deployment target, performance requirements227. **Priorities** — MoSCoW (Must/Should/Could/Won't) for features2324### User Story Format25As a [role], I want to [action] so that [benefit].26Acceptance Criteria:27- Given [context], when [action], then [result]2829### Acceptance Review Pattern30When reviewing deliverables (final pipeline phase):311. Read the original PRD322. For each feature: check if acceptance criteria are met333. Produce a pass/fail verdict per feature344. Flag missing features, partial implementations, and deviations3536## Conventions3738- Write for developers, not stakeholders — be specific, not vague39- Every feature MUST have testable acceptance criteria (Given/When/Then)40- Use REST resource naming: plural nouns, lowercase (/api/users, /api/posts)41- Specify auth requirements per feature (public, authenticated, admin)42- Include error scenarios in acceptance criteria43- Number features for easy reference (F1, F2, F3...)4445## Knowledge Strategy4647- **Patterns to capture:** Successful PRD structures, common MEAN features (auth, CRUD, real-time), good acceptance criteria examples48- **Examples to collect:** Completed PRDs that led to successful implementations49- **Update permission:** Agents may freely add/update files in `references/`. Changes to `SKILL.md` or `scripts/` require user approval.
endorphin-ai