speckit-taskstoissues

To convert design tasks into GitHub issues, this Skill validates task lists from your project and creates issues via the GitHub MCP server. It automatically maps design artifacts stored in a .specify/ directory into a structured, dependency-ordered backlog.

Dependency-ordered issue generation works by reading existing design tasks from the .specify/ structure and sequencing the output GitHub issues based on their relationships. This ensures that linked issues are created in the correct order for implementation planning.

Yes, you need the GitHub MCP server configured to generate issues from .specify/ artifacts. The Skill relies on this server connection to validate your task lists and automatically publish the dependency-ordered issues directly to your repository.

The best way to create a linked backlog from design artifacts is using a project automation Skill that maps tasks to issues with metadata and labels. It processes multiple tasks from your .specify/ directory and generates ready-to-assign items with dependency ordering.

Yes, you can add custom hooks when generating GitHub issues from spec-kit tasks. The Skill includes pre- and post-execution extension hooks, allowing you to inject custom logic before the task validation begins and after the issues are successfully created.

If your spec-kit design tasks are not converting into GitHub issues, ensure your project uses the required .specify/ structure and that the GitHub MCP server is properly configured. The Skill validates task lists from this specific directory before creating issues.