feature-spec

Generate structured product requirements documents with user stories and acceptance criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SMOrchestra-ai/smorch-brain --skill feature-spec-smorchestra-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/SMOrchestra-ai/smorch-brain/tree/main/plugins/product-management/skills/feature-spec
Command: npx skills add https://github.com/SMOrchestra-ai/smorch-brain --skill feature-spec-smorchestra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates ambiguity in product planning by turning ideas and stakeholder inputs into structured, testable product requirements documents that teams can act on. It reduces rework, aligns cross-functional teams, and clarifies acceptance criteria and success metrics before implementation.

Core Features & Use Cases

  • Structured PRDs: Problem statement, goals, non-goals, user stories, requirements (P0/P1/P2), acceptance criteria, open questions, and timeline guidance.
  • User story & acceptance criteria guidance: Produces prioritized, testable user stories and Given/When/Then acceptance criteria to support development and QA.
  • Success metrics & scope management: Defines leading and lagging indicators, target thresholds, and techniques to prevent scope creep during delivery.
  • Use Case: Product managers scoping a new feature can generate a complete PRD for stakeholder review, handoff to engineering, and launch measurement.

Quick Start

Use the feature-spec skill to generate a concise PRD for a new single sign-on feature targeting enterprise admins, including a problem statement, 3 goals, prioritized user stories, P0 requirements, acceptance criteria, and measurable 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 generate a product requirements document from a feature idea?

To generate a product requirements document, input your feature idea to produce a structured PRD containing problem statements, prioritized user stories, acceptance criteria, and success metrics.

How do I write acceptance criteria and user stories for sprint planning?

Writing acceptance criteria involves generating prioritized user stories and Given/When/Then test conditions to align cross-functional teams and support development and QA during sprint planning.

How do I define success metrics and non-goals to prevent scope creep?

Defining success metrics requires setting measurable leading and lagging indicators with target thresholds, alongside explicit non-goals, to manage scope and prevent scope creep during delivery.

Can I create a PRD for enterprise features like single sign-on?

Yes, you can create a PRD for enterprise features like single sign-on by generating tailored problem statements, goals, P0 requirements, and acceptance criteria for specific user personas such as enterprise admins.

What is the best way to structure stakeholder inputs into actionable requirements?

The best way to structure stakeholder inputs is to transform them into testable requirements with P0/P1/P2 prioritization, clear acceptance criteria, and timeline guidance for engineering handoff.