speckit-phasestoissues

You can create GitHub issues from specification files by using a tool to parse phase definitions and task lists, automatically generating parent issues and linked sub-issues with contextual labels based on your Git repository context.

Yes, you can automatically break down project phases into GitHub sub-issues by extracting tasks from your specification files. Each task is converted into a linked sub-issue under a parent phase issue, streamlining development workflow management.

To add acceptance criteria and implementation plans to GitHub issues automatically, use an automation tool that reads your specification files and embeds the phase descriptions and contextual details directly into the generated issue bodies.

Yes, generating GitHub issues from specification files requires Git repository access. The automation relies on your current Git context and project structure to correctly extract phases, apply relevant labels, and link the generated issues.

The best way to automate task management issue labeling from project specifications is to use a script that reads your workflow type and priority directly from the spec files, automatically applying the relevant labels during GitHub issue creation.

You should avoid automating GitHub issue creation from development phases if your project lacks structured specification files with defined phases and tasks, or if your repository does not have the Git context necessary for proper issue linking and labeling.