How does it help with user story writing?

The skill enforces the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) and provides clear templates for writing effective acceptance criteria.

Can I define success metrics with this skill?

Absolutely. It helps you define both leading indicators (like adoption rates) and lagging indicators (like revenue impact) to measure the outcome of your features.

Does this skill help manage project scope?

Yes, it includes a dedicated section for Non-Goals and requirement categorization (MoSCoW) to explicitly define boundaries and prevent feature creep during implementation.

What is the primary benefit of the Feature Spec skill?

It provides a standardized, professional framework for documenting product decisions, ensuring that technical teams and stakeholders are aligned on the 'what', 'why', and 'how' of a feature.

Product Management Feature Spec

Name: Product Management Feature Spec
Author: lilbom32

bylilbom32

0•

コラボレーションツール

Generates structured product requirements documents (PRDs) and user stories to define clear feature specifications and success metrics.

The Product Management Feature Spec skill provides a comprehensive framework for defining, documenting, and prioritizing product features. It guides users through the creation of high-quality Product Requirements Documents (PRDs) that include evidence-based problem statements, measurable goals, and explicit non-goals to prevent scope creep. By standardizing the way user stories and acceptance criteria are written, it ensures that developers, designers, and stakeholders have a shared understanding of what needs to be built and how success will be measured.

主な機能

01Structured PRD generation including problem statements and success metrics

02MoSCoW and P0/P1/P2 requirement prioritization frameworks

03Detailed acceptance criteria using Given/When/Then or checklist formats

040 GitHub stars

05Standardized user story creation using the INVEST framework

06Scope management tools to define explicit non-goals and architectural considerations

ユースケース

01Translating high-level business goals into actionable developer user stories and acceptance criteria

02Drafting a comprehensive PRD for a new product feature or major initiative

03Facilitating stakeholder alignment by documenting project scope, risks, and open questions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lilbom32/ketnoitrithuc feature-spec

For use in Claude.ai and ChatGPT

主な機能

01Structured PRD generation including problem statements and success metrics

02MoSCoW and P0/P1/P2 requirement prioritization frameworks

03Detailed acceptance criteria using Given/When/Then or checklist formats

040 GitHub stars

05Standardized user story creation using the INVEST framework

06Scope management tools to define explicit non-goals and architectural considerations

ユースケース

01Translating high-level business goals into actionable developer user stories and acceptance criteria

02Drafting a comprehensive PRD for a new product feature or major initiative

03Facilitating stakeholder alignment by documenting project scope, risks, and open questions