af-define-requirements

Define atomic feature requirements and generate mini-PRDs for structured delivery.

Updated Feb 8, 2026

Search Tags:#requirements #product management #feature definition #scrum #mini-prd #atomic features

Ready to run

npx skills add https://github.com/GainInsightDev/websites --skill af-define-requirements

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: af-define-requirements
Source: https://github.com/GainInsightDev/websites/tree/main/.claude/skills/af-define-requirements
Command: npx skills add https://github.com/GainInsightDev/websites --skill af-define-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of defining granular feature requirements and creating concise Product Requirement Documents (PRDs) to ensure structured and atomic work breakdown.

Core Features & Use Cases

Atomic Feature Definition: Helps in breaking down large epics into smaller, manageable features.
Mini-PRD Generation: Facilitates the creation of structured mini-PRDs for each feature.
Structured Delivery: Supports a clear hierarchy from Epic to Feature to Scenario, aiding in implementation planning.
Use Case: When starting a new feature development, use this Skill to define its core requirements, user stories, and acceptance criteria in a standardized format.

Quick Start

Use the af-define-requirements skill to define the requirements for the user authentication epic.

Frequently Asked Questions about af-define-requirements

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

FAQPage Schema

How do I break down large epics into manageable features for scrum delivery?▼

To break down large epics for scrum delivery, you define atomic feature requirements and generate mini-PRDs. This structures the hierarchy from Epic to Feature to Scenario, ensuring work is broken into atomic units for implementation planning.

What is the best way to create a mini-PRD for a new product feature?▼

The best way to create a mini-PRD is by defining atomic feature requirements in a standardized format. This process generates concise Product Requirement Documents that include core requirements, user stories, and acceptance criteria for structured delivery.

How does generating atomic feature requirements improve product management workflows?▼

Generating atomic feature requirements improves product management workflows by streamlining the definition of granular requirements. It ensures a structured work breakdown, supporting a clear hierarchy from Epic to Feature to Scenario for concise PRD generation.

Do I need established documentation standards to define atomic requirements?▼

Yes, defining atomic requirements requires adherence to established documentation standards for feature definition and PRD structure. This ensures the generated mini-PRDs and structured delivery formats remain consistent across the product development workflow.

Can I use this approach to structure user stories and acceptance criteria for a feature?▼

Yes, you can use this approach to structure user stories and acceptance criteria for a feature. The process defines atomic requirements and generates mini-PRDs, capturing the core requirements in a standardized format for implementation planning.