af-define-requirements

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.

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.

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.

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.

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.