skills.rest
Clos01
Clos01COMMUNITY
Explore all skills by this author →
GitHub

pm-spec

Create structured product requirement documents with goals, metrics, and delivery plans.

3|2|Updated May 28, 2026
Search Tags:#requirements#roadmap#user stories#prd#product spec#feature brief
One-click install
npx skills add https://github.com/Clos01/Kenbun-Agent --skill pm-spec-clos01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/Clos01/Kenbun-Agent/tree/main/core/tools/skills/pm-spec
Command: npx skills add https://github.com/Clos01/Kenbun-Agent --skill pm-spec-clos01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams turn feature ideas into clear, structured product requirement documents by organizing goals, scope, metrics, and decisions in a single-page format.

Core Features & Use Cases

  • PRD Structure Generation: Creates product specs with problem statements, goals, non-goals, success metrics, user stories, milestones, and open questions.
  • Product Planning Workflow: Guides teams through defining feature requirements, audiences, rollout phases, and design considerations.
  • Use Case: Product managers can use this Skill to transform a feature brief such as adding two-factor authentication into a review-ready PRD.

Quick Start

Ask the pm-spec skill to write a PRD for a new feature including the problem, scope, milestones, and open questions.

Frequently Asked Questions about pm-spec

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

FAQPage Schema
How do I create a product requirement document from a feature brief?▼

To create a product requirement document from a feature brief, the Skill structures your feature idea into a review-ready PRD with problem statements, goals, scope, metrics, and rollout planning.

What sections should be included in a product spec or PRD?▼

A product spec or PRD should include organized sections for problem statements, goals, non-goals, success metrics, user stories, scope, design notes, rollout phases, and unresolved decisions.

Can I use this to plan feature rollout phases and milestones?▼

Yes, you can use this to plan feature rollout phases and milestones. The generated product requirement documents include specific sections for rollout planning and delivery milestones.

What is the best way to document user stories and open questions for a new feature?▼

The best way to document user stories and open questions for a new feature is to structure them within a single-page product spec that explicitly separates defined scope from unresolved decisions and milestones.

Does this approach work for single-page product requirement documents?▼

Yes, this approach works for single-page product requirement documents by organizing goals, scope, metrics, and decisions into a single-page format for review-ready product planning.

Related Skills

Explore More Product & Management Skills→
jtsang4jtsang4
2

shape

Guide structured conversations to define product ideas and create SPEC files.

Community
Intermediate
Buntyarora97Buntyarora97

product-manager

Create PRDs and roadmaps with customizable templates and prioritization frameworks.

Community
Advanced
pipixia-labspipixia-labs
38

pm-spec

Convert a design brief into a structured one-page product spec.

Official
Advanced
42team-ru42team-ru

shape

Plan UX/UI by interviewing stakeholders and generating a structured design brief.

Official
Advanced