skills.rest
aimentor606
aimentor606COMMUNITY
Explore all skills by this author →
GitHub

feature-spec

Generate structured product requirements documents with prioritized acceptance criteria.

Updated Apr 8, 2026
Search Tags:#prd#user-stories#acceptance-criteria#feature-spec#product-requirements#success-metrics
One-click install
npx skills add https://github.com/aimentor606/aether --skill feature-spec-aimentor606
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/aimentor606/aether/tree/main/core/kortix-master/opencode/skills/GENERAL-KNOWLEDGE-WORKER/feature-spec
Command: npx skills add https://github.com/aimentor606/aether --skill feature-spec-aimentor606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many product teams struggle to translate ideas into clear, actionable specifications that align stakeholders, define scope, and measure success. This Skill provides a repeatable PRD structure to reduce ambiguity, prevent scope creep, and accelerate delivery by making decisions explicit and testable.

Core Features & Use Cases

  • Structured PRD template: Problem statement, goals, non-goals, user stories, requirements (P0/P1/P2), acceptance criteria, success metrics, open questions, and timeline considerations.
  • User story and acceptance criteria guidance: Helps write independent, testable stories with Given/When/Then criteria and common mistake avoidance.
  • Scope and prioritization: MoSCoW categorization and tips to prevent scope creep during implementation.
  • Use Case: A product manager preparing a launch spec for an onboarding flow can produce a prioritized PRD with measurable targets and a testable acceptance checklist to hand off to engineering.

Quick Start

Draft a complete PRD for a new onboarding flow including a concise problem statement, three measurable goals, three non-goals, prioritized user stories with 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 with measurable goals?▼

A structured PRD template prevents scope creep by making decisions explicit and testable, categorizing requirements using MoSCoW prioritization, and providing independent user stories with Given/When/Then acceptance criteria to remove ambiguity for engineering teams.

What is the best way to structure a PRD for stakeholder alignment?▼

The best way to structure a PRD for stakeholder alignment is to include problem statements, measurable goals, non-goals, MoSCoW prioritized requirements, and success metrics, making decisions explicit and testable to prevent scope creep.

Can I use MoSCoW prioritization to prevent scope creep in feature specs?▼

Write independent, testable user stories by pairing each with Given/When/Then acceptance criteria, ensuring clear validation steps while avoiding common specification mistakes that create ambiguity for engineering teams.

Can I use MoSCoW prioritization to prevent scope creep in feature specs?▼

Yes, applying MoSCoW categorization to your feature specs helps prevent scope creep by explicitly separating must-have, should-have, and could-have requirements, ensuring engineering teams focus only on prioritized items during implementation.

What should I include in a feature spec for an onboarding flow?▼

A feature spec for an onboarding flow should include a problem statement, three measurable goals, three non-goals, prioritized user stories with acceptance criteria, and success metrics suitable for implementation planning and handoff.

Related Skills

Explore More Product & Management Skills→
AAbdulghanyAAbdulghany

write-spec

Generate a structured PRD template from a problem statement or feature idea.

Community
Advanced
busboom-software-studiobusboom-software-studio
1

create-tickets

Convert architecture-update.md and usecases.md into sequenced tickets with dependencies.

Official
Advanced
hajrasarwar11hajrasarwar11

product-manager

Generate PRDs, user stories, and roadmaps with acceptance criteria.

Community
Intermediate
MaxKlat29MaxKlat29

user-story-splitting

Break down large user stories into smaller, independent stories using systematic splitting patterns.

Community
Intermediate