product-manager

Create PRDs, user stories, and feature specs with standardized templates.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Kibbey/fyli --skill product-manager-kibbey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/Kibbey/fyli/tree/main/.claude/skills/product-manager
Command: npx skills add https://github.com/Kibbey/fyli --skill product-manager-kibbey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Busy teams often lack a consistent, structured approach to product documentation. This skill helps create PRDs, user stories, and feature specs that align stakeholders and guide product decisions.

Core Features & Use Cases

  • PRD creation and template-driven documentation
  • User story generation with acceptance criteria
  • Feature specification drafting and traceability
  • Stakeholder interview prompts and decision framing
  • Update of product vision and roadmap alignment

Quick Start

Provide a PRD draft for a new feature, including problem statement, goals, user stories, and acceptance criteria. If needed, ask clarifying questions to align with goals.

Frequently Asked Questions about product-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a PRD with measurable goals and testable acceptance criteria?

To create a PRD, define an explicit problem statement, set measurable goals, and write testable acceptance criteria. This ensures your product requirement documentation aligns stakeholders and guides scalable feature development.

What is the best way to write user stories for feature specs?

Writing user stories requires standardized templates that enforce testable acceptance criteria and explicit problem statements. This approach maintains traceability and ensures feature specifications align with the overarching product vision.

Can I use this approach to align stakeholders and update product vision?

Yes, you can align stakeholders and update product vision by using structured decision framing and interview prompts. This enforces consistent product documentation and translates stakeholder input into measurable goals.

Does this method require any specific product-management frameworks to function?

No specific external frameworks are required to define and document product decisions. The approach relies on standardized templates for creating PRDs, user stories, and feature specs to enforce consistent documentation.

Why do my feature specs lack traceability and consistent structure?

Feature specs lack traceability when teams skip standardized templates and explicit problem statements. Enforcing testable acceptance criteria and measurable goals within your PRDs resolves this inconsistency and aligns product decisions.

How do I refine requirements and analyze features for a new product?

Refine requirements by drafting feature specifications with explicit problem statements and measurable goals. Analyzing features through standardized templates ensures your user stories contain testable acceptance criteria for scalable collaboration.