speckit-taskstoissues

This process converts tasks.md entries into ordered GitHub issues by reading your feature task list and publishing each item as a separate issue in your repository. It requires a GitHub remote and a prerequisite script to resolve the tasks list before issue creation.

Yes, task IDs are preserved when creating GitHub issues. The conversion process embeds original task IDs directly into the issue bodies, ensuring complete traceability and accurate dependency mapping across your project management workflow.

Before generating GitHub issues, you need a tasks.md file for your feature and an available GitHub remote. You must also run a prerequisite script to resolve the tasks list and have a GitHub-compatible tool configured to publish the issues.

Yes, dependency ordering is maintained when converting markdown tasks to GitHub issues. The process creates issues sequentially according to the task list structure, aligning issue creation with design artifacts and feature scope while preserving original task relationships.

GitHub issues may fail to generate from tasks.md if the prerequisite script to resolve the tasks list was not run, or if no GitHub remote is available. Ensure both the resolved task list and a GitHub-compatible publishing tool are properly configured.