Product Manager
Run roadmap, prioritization, scoping, sprints, releases, OKRs, and stakeholder alignment like a one-person PM across the whole product lifecycle.
Install
npx skills add https://github.com/ncklrs/startup-os-skills --skill product-managerWhat is this skill?
- Eight structured PM domains: roadmap, prioritization, stakeholder management, sprint/backlog, scoping, release, metrics/
- Prioritization frameworks including RICE, ICE, and MoSCoW for what to build next
- Feature scoping and MVP trade-offs to control scope creep
- Sprint planning, estimation, and agile ceremony guidance for small teams
- Metrics and OKRs emphasis on outcomes over outputs plus cross-functional collaboration patterns
Adoption & trust: 1 installs on skills.sh; 27 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Grill Memattpocock/skills
Grill With Docsmattpocock/skills
Brainstormingobra/superpowers
Lark Tasklarksuite/cli
Lark Workflow Standup Reportlarksuite/cli
Cavemanjuliusbrussee/blueprint
Journey fit
Primary fit
Build/PM is the canonical shelf because the skill packages ongoing product operations—backlog, sprints, release coordination—that solo builders live in while shipping, even though the same frameworks apply earlier and later. The pm subphase captures sprint/backlog, feature scoping, release planning, and metrics that sit between pure engineering and business strategy.
Common Questions / FAQ
Is Product Manager safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Product Manager
## 1. Roadmap Strategy (roadmap) **Impact:** CRITICAL **Description:** Creating, maintaining, and communicating roadmaps at all levels. Foundation of product planning that aligns teams and stakeholders. ## 2. Prioritization Frameworks (prioritization) **Impact:** CRITICAL **Description:** RICE, ICE, MoSCoW, and other frameworks for making data-informed decisions about what to build next. ## 3. Stakeholder Management (stakeholder) **Impact:** HIGH **Description:** Managing expectations, communicating effectively, and building alignment across executives, engineering, sales, and customers. ## 4. Sprint & Backlog (sprint) **Impact:** HIGH **Description:** Sprint planning, backlog grooming, estimation, and agile ceremonies that keep teams productive. ## 5. Feature Scoping (scoping) **Impact:** HIGH **Description:** Defining MVP, making trade-offs, writing specs, and managing scope creep. ## 6. Release Planning (release) **Impact:** MEDIUM-HIGH **Description:** Coordinating releases, managing dependencies, and communicating timelines. ## 7. Metrics & OKRs (metrics) **Impact:** CRITICAL **Description:** Defining success metrics, setting OKRs, and measuring outcomes over outputs. ## 8. Technical Debt (debt) **Impact:** MEDIUM-HIGH **Description:** Balancing feature work with technical health, prioritizing debt reduction, and communicating value. --- title: Cross-Functional Collaboration impact: HIGH tags: collaboration, teamwork, design, engineering, communication --- ## Cross-Functional Collaboration **Impact: HIGH** PMs don't build products — teams do. Your job is to create the conditions for teams to do their best work together. ### The Product Trio Model ``` ┌─────────────────────────────────────────────────────────────────┐ │ │ │ ┌─────────────┐ │ │ │ PRODUCT │ │ │ │ MANAGER │ │ │ └──────┬──────┘ │ │ │ │ │ Discovery ─────┼───── Delivery │ │ │ │ │ ┌───────────────┴───────────────┐ │ │ │ │ │ │ ┌──────┴──────┐ ┌──────┴──────┐ │ │ │ PRODUCT │ │ ENGINEERING │ │ │ │ DESIGNER │◄───────────────▶│ LEAD │ │ │ └─────────────┘ └─────────────┘ │ │ │ │ Shared ownership of │ │ problems AND solutions │ │ │ └─────────────────────────────────────────────────────────────────┘ ``` ### RACI for Common Activities | Activity | PM | Design | Eng Lead | Engineering | |----------|:--:|:------:|:--------:|:-----------:| | Problem definition | A | C | C | I | | User research | C | A | I | I | | Solution exploration | C | A | C | I | | Technical feasibility | C | I | A | C | | Requirements | A | C | C | I | | Design specs | C | A | I | C | | Technical specs | I | I | A | C | | Implementation | I | C | A | R | | QA/Testing | C | C | A | R | | Launch decision | A | C | C | I | | Success measurement | A | C | C | I | **Legend:** R=Responsible, A=Accountable, C=Consulted, I=Informed ### Working with Engineering **What engineers need from PMs:** | Need | What It Looks Like | |------|-------------------| | **Context, not tickets** | "Here's the problem and why it matters" | | **Clear priorities** | "This is #1, that's #2, period" | | **Stable requirements** | Minimize mid-s