pm-feature-spec

Create structured PRDs and feature specs with user stories and acceptance criteria.

Updated Aug 23, 2026

Search Tags:#requirements #prd #pm #user-stories #acceptance-criteria #feature-spec #moscow

Ready to run

npx skills add https://github.com/kirillshilin/instructions --skill pm-feature-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-feature-spec
Source: https://github.com/kirillshilin/instructions/tree/main/obsolete/dotgithub/skills/pm-feature-spec
Command: npx skills add https://github.com/kirillshilin/instructions --skill pm-feature-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing comprehensive feature specifications helps product teams align on goals, scope, and success criteria without ambiguity.

Core Features & Use Cases

Define problem statements, goals, and non-goals to anchor decisions.
Create user stories with clear acceptance criteria and MoSCoW prioritisation.
Capture success metrics, timelines, and open questions to guide delivery.

Quick Start

Draft a complete PRD from a raw idea by outlining the problem, goals, user stories, and acceptance criteria.

Frequently Asked Questions about pm-feature-spec

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

FAQPage Schema

What is a PRD and how does it structure feature requirements?▼

A PRD is a product requirements document that structures feature specs by defining problem statements, goals, non-goals, user stories, and acceptance criteria to align product teams. It captures success metrics, timelines, and open questions to guide delivery.

How do I write user stories with acceptance criteria for a new feature?▼

To write user stories with acceptance criteria, start from your raw feature idea and define the problem statement and goals. Then, generate specific user stories paired with clear acceptance criteria and apply MoSCoW prioritization to categorize requirements.

What's the best way to prioritize requirements using the MoSCoW method?▼

The best way to prioritize requirements using the MoSCoW method is to categorize your user stories and feature specs into Must-have, Should-have, Could-have, and Won't-have buckets during PRD creation, ensuring clear scope alignment for product teams.

Can I draft a complete feature spec from a raw idea without prior documentation?▼

Yes, you can draft a complete feature spec from a raw idea. The process transforms your initial concept directly into a structured PRD by outlining the problem, goals, user stories, acceptance criteria, and success metrics without needing prior documentation.

Does a feature spec need to include non-goals and success metrics?▼

Yes, a feature spec needs to include non-goals and success metrics. Documenting non-goals anchors decisions by defining out-of-scope items, while success metrics capture the criteria required to measure and guide the delivery of the feature.