speckit-taskstoissues.agent

To convert design tasks into ordered GitHub issues, this Skill reads design artifacts from a .specify/ directory, extracts actionable tasks with dependencies, and posts them to the repository defined by your git remote while preserving task order.

Yes, converting tasks into GitHub issues requires a repository containing design artifacts and a .specify/ directory, along with a prerequisites check, remote validation, and the GitHub MCP endpoint to post issues.

Dependency-aware issue generation works by reading existing design tasks from spec-kit artifacts, evaluating their dependencies, and creating GitHub issues in the target repository that preserve the required execution order.

You can automatically create GitHub issues from design artifacts by running this Skill in your current repository, which validates your git remote and uses the GitHub MCP endpoint to post the extracted tasks as actionable issues.

The best way to surface scattered design tasks for triage is converting them into a structured set of GitHub issues, which enables teams to track work from design artifacts through to implementation with dependency awareness.

Tasks may not convert into GitHub issues if the prerequisites check fails, the .specify/ directory or design artifacts are missing, the git remote is invalid, or the GitHub MCP endpoint cannot access the target repository.