skills.rest
felvieira
felvieiraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

po-feature-spec

Translate business needs into user stories, acceptance criteria, and handoff plans.

22|6|Updated Mar 10, 2026
Search Tags:#backlog#handoffs#product-management#user-stories#acceptance-criteria#feature-spec
One-click install
npx skills add https://github.com/felvieira/claude-skills-fv --skill po-feature-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: po-feature-spec
Source: https://github.com/felvieira/claude-skills-fv/tree/main/skills/01-po-feature-spec
Command: npx skills add https://github.com/felvieira/claude-skills-fv --skill po-feature-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates vague business needs into clear, actionable feature specifications.

Core Features & Use Cases

  • Translate business goals into explicit user stories and acceptance criteria.
  • Define feature scope, dependencies, and prioritization for aligned cross-functional teams.
  • Provide handoffs to UI/UX, engineering, and QA with a clear success metric plan.

Quick Start

Provide a concise feature brief for a new capability by stating the business objective, success criteria, and initial acceptance tests.

Frequently Asked Questions about po-feature-spec

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

FAQPage Schema
How do I translate vague business needs into actionable feature specifications?▼

To translate vague business needs into actionable feature specifications, define the problem statement, set feature scope boundaries, write user stories, and establish clear success metrics for cross-functional handoffs.

What should be included in a feature spec for engineering and QA handoffs?▼

A feature spec for engineering and QA handoffs should include a problem statement, scope in/out, business rules, user stories, acceptance criteria, success metrics, and a clear handoff plan to UI/UX and development teams.

How do I write user stories and acceptance criteria from a business objective?▼

Writing user stories and acceptance criteria from a business objective requires stating the goal, defining explicit success criteria, and translating them into initial acceptance tests and prioritized backlog items.

Can I use this to define feature scope and dependencies for cross-functional teams?▼

Yes, you can define feature scope, dependencies, and prioritization to align cross-functional teams by providing a concise feature brief that states the business objective and initial acceptance tests.

What is the best way to structure a minimal feature specification for product management?▼

The best way to structure a minimal feature specification for product management is to include a problem statement, scope in/out boundaries, business rules, prioritization, and a defined success metric plan.

Related Skills

Explore More Product & Management Skills→
SriRamkunamsettySriRamkunamsetty

one-three-one-rule

Generate a 1-3-1 decision brief with problem, options, and recommendation.

Community
Advanced
rakhnianskii9rakhnianskii9

team-ui

Coordinate cross-functional UI project pipelines across design, implementation, review, and polish phases.

Community
Advanced
StudentCristianStudentCristian

nw-user-story-mapping

Generates story-map.md and prioritization.md from user activities and outcomes.

Community
Intermediate
ZateZate
9

requirements-patterns

Generate user stories and acceptance criteria using Given-When-Then templates.

Community
Basic