product-manager_skill

This skill helps define product vision, prioritize roadmaps, and validate user needs using JTBD, RICE, and Kano methods.
  • Python

60

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill kienhaminh/anti-chaotic --skill product-manager

  • SKILL.md7.9 KB

Overview

This skill provides practical product management guidance for defining vision, building outcome-focused roadmaps, and running user-centric discovery. It codifies frameworks and workflows—visioning, prioritization (RICE/Kano), PRD creation, task decomposition, and sprint execution—so you can move from hypothesis to shippable work. Use it to keep teams aligned around customer value and fast, testable delivery.

How this skill works

The skill inspects goals, user problems, and business context to recommend a strategy (Now/Next/Later) using JTBD and prioritization frameworks like RICE and Kano. It generates structured artifacts: strategic PRDs, user stories with acceptance criteria, and a decomposed backlog (epics → stories → tasks) following a maximum-granularity rule. It enforces process rules: mandatory PRD template, vertical slices, explicit tests, and tasks sized for 2–8 hour work items.

When to use it

  • Defining product vision or aligning to OKRs
  • Planning a strategic roadmap (Now/Next/Later)
  • Creating or reviewing a PRD or user stories
  • Prioritizing feature candidates using RICE/Kano
  • Decomposing a document or feature into actionable tasks
  • Preparing for sprint planning or acceptance testing

Best practices

  • Focus on outcome over output—define success metrics before features
  • Validate problems with user interviews before writing requirements
  • Prioritize ruthlessly; say no to low-impact work
  • Decompose vertically into end-to-end slices, not horizontal layers
  • Make tests explicit: each feature includes separate testing tasks
  • Keep tasks 2–8 hours and independently testable

Example use cases

  • Draft a strategic PRD that ties a new feature to measurable OKRs
  • Score and rank a list of product ideas using RICE and Kano
  • Break a PRD into epics, stories, and 2–8 hour tasks with ACs
  • Review a BA spec and suggest simplifications and missing edge cases
  • Run discovery: JTBD interviews, hypothesis framing, and success metrics

FAQ

Yes. Use the strategic PRD template to ensure hypothesis, success metrics, and analytics are included before development.

How granular should tasks be?

Aim for 2–8 hour tasks. Break work into vertical slices with explicit testing and acceptance criteria so each task is independently verifiable.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational