product-manager

Converts product ideas into BRDs with user stories, acceptance criteria, and implementation verification.

176|49|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/nagisanzenin/production-grade --skill product-manager-nagisanzenin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/nagisanzenin/production-grade/tree/main/skills/product-manager
Command: npx skills add https://github.com/nagisanzenin/production-grade --skill product-manager-nagisanzenin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning vague product ideas and business goals into clear, testable engineering requirements is hard, and implementations often drift from what was actually requested. This Skill interviews stakeholders, researches the domain, writes a formal BRD, and verifies that shipped code matches the requirements. ## Core Features & Use Cases - Adaptive CEO Interview: Asks 2-12 questions depending on engagement mode (Express, Standard, Thorough, Meticulous) to capture the problem, users, constraints, and success metrics. - BRD Authoring: Produces a structured Business Requirements Document with user stories, testable acceptance criteria, business rules, and out-of-scope items, tracked in an INDEX.md. - Autonomous Verification: Spawns a verification agent that checks each acceptance criterion against the actual codebase and reports PASS/FAIL/PARTIAL per criterion. - Use Case: A founder says "I want to build an uptime monitoring tool." The Skill interviews them, researches competitors, writes the BRD, hands it to engineering, and later verifies the implementation matches every acceptance criterion. ## Quick Start Ask the product-manager skill to turn your new feature idea into a BRD with user stories and acceptance criteria.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I turn a product idea into a BRD with user stories?▼

Describe your feature idea and the Skill runs a structured interview covering the problem, users, constraints, and success metrics. It then writes a BRD with user stories in standard format, testable acceptance criteria, business rules, and out-of-scope items.

How to write testable acceptance criteria for a feature?▼

Acceptance criteria follow the Given/When/Then format and must be specific and measurable, such as "returns 200 with valid JSON within 500ms" rather than "should be fast." In Thorough and Meticulous modes, criteria are co-authored and validated with you before approval.

Can the interview depth be adjusted for quick feature requests?▼

Yes, engagement modes control interview depth. Express mode asks 2-3 questions and auto-fills gaps from web research, Standard asks 3-5, Thorough asks 5-8, and Meticulous runs 8-12 questions across multiple rounds with market and risk analysis.

Does it verify that code matches the requirements?▼

Yes, Phase 4 spawns a verification agent that reads each BRD acceptance criterion and checks it against the codebase, reporting PASS, FAIL, or PARTIAL per criterion with an overall compliance percentage. BRD status updates to Verified or Done accordingly.

When should I not use a product requirements workflow?▼

Skip it for pure technical tasks, bug fixes, and refactoring that do not change business logic. The Skill is designed for translating business context into engineering specs, not for writing code or handling implementation work directly.