speckit-taskstoissues

To convert spec-kit tasks into GitHub issues, this Skill reads the .specify/ directory and generates one issue per task while preserving intended ordering and dependencies. It automatically targets the correct repository by reading the remote URL and validates repo ownership before creation.

The best way to maintain task dependencies when exporting to GitHub is to map each task to a separate issue with explicit ordering and references. This approach ensures downstream work retains the original design artifact relationships from the .specify directory.

This task-to-issue conversion only works with spec-kit style repositories containing a .specify/ directory. It avoids cross-repo creation by validating repository ownership and reading the remote URL to target the correct GitHub project.

When generating GitHub issues, the workflow ensures each issue references the original design artifacts and specifies relationships to facilitate downstream work. This preserves the dependency-ordered structure defined in the .specify directory.

Issue generation requires a .specify directory because it serves as the source for mapping existing design artifacts and tasks into actionable, dependency-ordered GitHub issues, ensuring the workflow applies only to properly structured spec-kit repositories.