speckit-taskstoissues

To convert Spec-Kit tasks into GitHub issues, this skill reads existing task artifacts from the .specify directory and creates dependency-ordered issues in the matching GitHub repository. It verifies the Git remote before posting to ensure repository safety.

Dependency ordering preserves task relationships so GitHub issues are created in a sequence that supports incremental delivery. This allows teams to execute the backlog step-by-step, ensuring foundational tasks are completed before dependent work begins.

No, this conversion applies specifically to Spec-Kit repositories that already contain task artifacts in a .specify structure. It requires task discovery from project scripts and will not function without this existing planning format.

You can create an actionable GitHub backlog by asking this skill to transform your existing feature tasks into separate issues. It reads the task lists and reflects the implementation intent directly into the GitHub repository's issue tracker.

Verifying the Git remote is a repository safety check that confirms the project is connected to the matching GitHub repository. This reduces the risk of posting the generated task issues to the wrong repository.

Yes, the skill reads task lists and transforms each task into a separate issue while preserving dependency ordering. This provides a clean backlog ready for sprint planning and assignment, even with complex task relationships.