013-agile-feature

Agile feature documentation should include scope, acceptance criteria, user stories, dependencies, integration guidance, and success metrics to provide comprehensive planning context for both stakeholders and engineering teams.

The best way to split epics during backlog refinement is to convert each epic into individual Markdown feature documents, ensuring each feature has clearly defined scope and success metrics for software development planning.

Yes, you can generate user stories and acceptance criteria from an existing epic file by providing the file path or pasting its content directly into the agent to automate the feature planning documentation.

Agile feature documentation planning works without external project management dependencies because the process operates standalone using internal scripts and references to parse epics and output Markdown files.

A limitation of automating epic to feature splitting is that the Skill generates structured Markdown templates for stakeholders, meaning complex narrative context or highly dynamic project management states may require manual adjustment.