speckit-taskstoissues

Converting spec-kit tasks to GitHub issues requires a tool that reads your `.specify/` directory and creates issues via the GitHub API. This automation performs deduplication and creates issues based on task dependencies.

Task conversion handles dependencies by ensuring issues are created in the correct order based on task dependencies. This ordering maintains the logical flow of your project structure during the GitHub issue creation process.

Yes, you need GitHub API access to convert tasks to issues in a spec-kit project. The conversion process directly interacts with GitHub repositories to perform issue creation and deduplication, requiring both API access and a spec-kit project directory.

Yes, you can filter which tasks are converted to GitHub issues by running the conversion command with an optional filter or label. This allows you to target specific tasks within your spec-kit project structure for issue creation.

Yes, the task conversion process prevents duplicate GitHub issues by performing deduplication during creation. It checks your existing GitHub repository to ensure that tasks from the `.specify/` directory are not converted into issues that already exist.

Yes, you can add custom logic before or after converting tasks to GitHub issues using extension hooks. The conversion process supports optional or mandatory hooks that allow you to inject custom pre- and post-conversion logic into the workflow.