feature-spec

Name: feature-spec
Availability: InStock
Author: lilbom32

Generate structured PRDs with problem statements, goals, user stories, and success metrics.

Updated Mar 15, 2026

Search Tags:#requirements #prioritization #prd #product-management #user-stories #acceptance-criteria

Ready to run

npx skills add https://github.com/lilbom32/ketnoitrithuc --skill feature-spec-lilbom32

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/lilbom32/ketnoitrithuc/tree/main/.claude/skills/product-management/1.1.0/skills/feature-spec
Command: npx skills add https://github.com/lilbom32/ketnoitrithuc --skill feature-spec-lilbom32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write structured product requirements documents (PRDs) with problem statements, goals, non-goals, user stories, requirements, acceptance criteria, and success metrics to align cross-functional teams and reduce scope drift.

Core Features & Use Cases

Structured PRD templates for problem statements, goals, non-goals, user stories, requirements, acceptance criteria, and success metrics
Guidance on MoSCoW prioritization, scope boundaries, decision logging, and artifact reuse
Clear workflows for drafting, reviewing, and approving product decisions across teams

Quick Start

Create a PRD for a feature by outlining the problem, goals, user stories, requirements, acceptance criteria, and success metrics.

Frequently Asked Questions about feature-spec

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

FAQPage Schema

How do I write a product requirements document that aligns cross-functional teams?▼

To write a PRD, outline the problem, goals, user stories, requirements, acceptance criteria, and success metrics. A template-driven approach enforces sections for non-goals, open questions, and timeline, reducing scope drift across product teams.

What should be included in a PRD to prevent scope drift?▼

A PRD prevents scope drift by explicitly defining non-goals alongside goals, user stories, and requirements. Documenting scope boundaries and using MoSCoW prioritization ensures cross-functional teams understand what is excluded from the feature spec.

How do I prioritize requirements and user stories for a new feature spec?▼

Prioritize requirements and user stories by applying MoSCoW prioritization within your PRD. This method categorizes product decisions into must-have, should-have, could-have, and won't-have items to manage scope and timeline effectively.

When do I need to document non-goals and open questions in a PRD?▼

Document non-goals and open questions in a PRD whenever speccing a new feature to establish clear scope boundaries. Logging these product decisions prevents scope creep and highlights unresolved issues for cross-functional team review.

Does this PRD template approach work for documenting product decisions and approval workflows?▼

Yes, the PRD template supports drafting, reviewing, and approving product decisions across teams. It structures problem statements, success metrics, and timelines to guide the review process and ensure cross-functional alignment.