speckit-taskstoissues

To convert tasks into dependency-ordered GitHub issues, run the workflow on a spec-kit repository. It validates the Git remote targets GitHub, reads the .specify directory, and automatically generates ordered issues enriched with design artifact context.

Automating task-to-issue conversion for a spec-kit project requires a .specify directory and a valid GitHub remote URL. The workflow reads existing tasks, orders them by dependency, and uses available design artifacts to populate actionable GitHub issues.

No, the task-to-issue workflow does not work outside GitHub. It explicitly validates that the Git remote URL points to a GitHub repository before creating dependency-ordered issues to ensure reproducible feature tracking.

A .specify directory is required to generate GitHub issues because it ensures the repository follows the spec-kit project structure. The workflow relies on this structure to accurately map tasks and design artifacts into dependency-ordered issues.

Dependency management works by analyzing relationships between existing tasks in your spec-kit project. The workflow converts the task list into GitHub issues that are explicitly ordered by their dependencies to guide sequential feature implementation.