product-manager — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited product-manager (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Strategic product management expertise for building the right things, in the right order, with the right people.
Great product management isn't about features. It's about outcomes — solving real problems for real users in ways that drive business results.
The best product managers:
When invoked, apply the guidelines in rules/ organized by:
roadmap-* — Roadmap creation, maintenance, and communicationprioritization-* — RICE, ICE, MoSCoW, and prioritization frameworksstakeholder-* — Managing up, down, and across the organizationsprint-* — Sprint planning, backlog grooming, ceremoniesscoping-* — Feature scoping, trade-offs, MVP definitionrelease-* — Release planning, coordination, communicationmetrics-* — Product metrics, OKRs, success measurementdebt-* — Technical debt management and balancing ┌─────────────────┐
│ Product │
│ Manager │
└────────┬────────┘
│
┌─────────────┼─────────────┐
│ │ │
▼ ▼ ▼
┌────────┐ ┌──────────┐ ┌──────────┐
│ UX │ │Engineering│ │ Data │
│Designer│ │ Lead │ │ Analyst │
└────────┘ └──────────┘ └──────────┘| Framework | Best For | Scoring | Complexity |
|---|---|---|---|
| RICE | Feature prioritization | Reach × Impact × Confidence / Effort | Medium |
| ICE | Quick decisions | Impact × Confidence × Ease | Low |
| MoSCoW | Release scoping | Must/Should/Could/Won't | Low |
| Kano | Customer satisfaction | Delight/Performance/Basic | High |
| Value vs Effort | Quick 2x2 plotting | Qualitative quadrants | Low |
┌──────────────────────────────────────────────────┐
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Discover │───▶│ Define │───▶│ Develop │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ ▲ │ │
│ │ ┌──────────┐ │ │
│ └─────────│ Measure │◀─────────┘ │
│ └──────────┘ │
│ │
└──────────────────────────────────────────────────┘| Type | Audience | Time Horizon | Detail Level |
|---|---|---|---|
| Vision | Board, investors | 2-5 years | High-level themes |
| Strategic | Leadership | 1 year | Quarterly goals |
| Release | Stakeholders | Quarter | Features/epics |
| Sprint | Dev team | 2 weeks | Stories/tasks |
High Confidence
│
┌───────────────┼───────────────┐
│ VALIDATE │ SHIP │
│ (test more) │ (execute) │
Low │ │ │ High
Impact───┼───────────────┼───────────────┼───Impact
│ IGNORE │ INVESTIGATE │
│ (say no) │ (research) │
└───────────────┼───────────────┘
│
Low Confidence| Stakeholder | Primary Interest | Communication Style |
|---|---|---|
| Executives | Business outcomes, strategy | High-level, metrics-focused |
| Engineering | Technical feasibility, quality | Detailed, collaborative |
| Design | User experience, usability | Visual, user-centric |
| Sales | Revenue, competitive advantage | Customer stories, timelines |
| Marketing | Positioning, launch timing | Messaging, dates |
| Support | User satisfaction, volume | Pain points, frequency |
| Customers | Problems solved, value | Empathy, listening |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.