speckit-taskstoissues

To automate GitHub issue creation from project tasks, this Skill converts task descriptions into structured issues with dependency ordering. It requires the spec-kit project structure and GitHub access to map tasks while checking for existing issues to prevent duplicates.

Task-to-issue mapping handles dependencies by organizing tasks based on their relationships to maintain project order. This ensures that GitHub issues are created in a structured sequence, respecting the dependency chain defined within your project tasks.

Yes, you need a spec-kit project structure containing the `.specify/` directory to convert tasks into GitHub issues. The Skill specifically relies on this structure to accurately map and automate your task-to-issue workflow.

Yes, you can sync existing tasks to GitHub issues without creating duplicates because the Skill performs conditional checks for existing issues. It verifies whether an issue already exists before creating a new one during the task conversion process.

The best way to structure GitHub issues for dependency-ordered workflows is to automate task conversion using a spec-kit structure. This approach organizes issues based on their task dependencies, ensuring your project maintains a logical and actionable execution order.