epic-story-planning

To create GitHub issues for epic and story planning, you use predefined templates like epic.yml and story.yml to generate structured issues, apply relevant labels, and map tasks to a planning hierarchy.

Writing gherkin acceptance criteria for user stories involves using structured patterns to define clear pass/fail conditions. This skill provides curated reference materials to guide accurate gherkin pattern usage for story planning.

Yes, you can use DEEP estimation for forecasting work in GitHub epics. This approach integrates with the planning hierarchy to improve estimation accuracy and label forecasting for generated issues.

Mapping tasks to a planning hierarchy requires breaking epics into smaller user stories with clear scope. This skill enforces frontmatter usage and template structures to maintain a repeatable hierarchy.

Yes, frontmatter is required in your GitHub issue templates for story planning. Enforcing frontmatter ensures structured metadata capture when generating epic and story issues from templates.

Using fixed templates for epic and story creation limits flexibility to the predefined epic.yml and story.yml structures. Planning scope and gherkin acceptance criteria must conform to these enforced frontmatter templates.