create-release-epic

You need the gh CLI installed and configured for GitHub API interactions, along with bash scripting support. These prerequisites allow the Skill to execute API calls, manipulate files locally, and automate the creation and linking of new epics in your specified repository.

During the disposition management phase, you interactively decide whether to transfer, supersede, or route each observation. This ensures that only the most critical and relevant themes are included in the structured body of the newly generated release epic issue.

The disposition management feature allows you to interactively decide whether to transfer, supersede, or route each observation. This ensures that only relevant themes are included in the structured body of the newly generated release epic issue.

Without the gh CLI, the Skill cannot interact with the GitHub API to aggregate comments from existing issues or execute the creation and linking of the new release epic issue in your repository.

By clustering observations into logical themes and allowing interactive disposition decisions, the Skill ensures that the generated release epic issue accurately reflects the most critical themes identified during the agile release planning process.

Creating release epics requires bash scripting for local file manipulation and executing gh CLI commands. The Skill uses bash scripts to process aggregated GitHub issue comments, manage the thematic clustering locally, and orchestrate the API calls needed to create and link the new release epic.