pm-write-spec

Generate structured product requirements documents from informal feature ideas.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill pm-write-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-write-spec
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/pm-write-spec
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill pm-write-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams and stakeholders often have vague ideas, scattered feedback, or feature requests that lack structure, measurable goals, and clear acceptance criteria. This Skill converts informal inputs into a scannable, implementation-ready product requirements document so teams can align quickly and reduce rework.

Core Features & Use Cases

  • Structured PRD generation: Produces a complete PRD with problem statement, goals, non-goals, user stories, categorized requirements (P0/P1/P2), success metrics, open questions, and timeline considerations.
  • Context-aware sourcing: Prompts for essential context and integrates available research, tickets, or designs when connected, falling back to user-provided details when not available.
  • Scoped delivery & iteration: Breaks large asks into phased specs, clarifies acceptance criteria in Given/When/Then or checklist format, and supports follow-up artifacts like design briefs or ticket breakdowns.
  • Use case: Turn a support ticket or stakeholder request into a prioritized, testable spec with measurable success metrics and a recommended phase 1 scope.

Quick Start

Write a product specification for "SSO support" that defines the problem, three measurable goals, P0 requirements with acceptance criteria, and a suggested rollout timeline.

Frequently Asked Questions about pm-write-spec

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

FAQPage Schema
How do I convert informal feature ideas into structured product requirements documents?

To convert feature ideas into structured product requirements documents, input your informal problem statements or user feedback to generate a scannable PRD with goals, user stories, acceptance criteria, and success metrics.

What is the best way to write user stories with acceptance criteria from vague stakeholder requests?

Writing user stories with acceptance criteria from vague requests involves transforming scattered feedback into categorized requirements using Given/When/Then or checklist formats, ensuring cross-functional teams align quickly on testable specs.

Can I use a PRD generator to break down large feature requests into phased specs?

Yes, you can use a PRD generator to break down large feature requests by producing phased specs that define scope, clarify non-goals, and recommend an initial rollout timeline to reduce development rework.

How do you define success metrics and measurable goals in a product spec?

Defining success metrics and measurable goals in a product spec requires translating stakeholder asks into quantifiable targets within the document, ensuring the resulting requirements have clear validation criteria for tracking progress.

Does generating a PRD from support tickets require pre-existing research or design files?

Generating a PRD from support tickets does not strictly require pre-existing research or design files. The process prompts for essential context and falls back to user-provided details when connected artifacts are unavailable.