speckit.taskstoissues

To convert design document tasks into GitHub issues automatically, this Skill parses actionable tasks and constraints from design artifacts, verifies the Git remote is a GitHub URL, and creates dependency-aware issues via GitHub MCP in the target repository.

Yes, you can create dependency-ordered GitHub issues from a feature development workflow by reading tracked tasks from design artifacts, parsing their prerequisites, and sequencing the generated issues to reflect task order and dependencies.

Yes, this tool prevents cross-repo issue creation by applying safety checks and scope validation that verify the Git remote URL before generating issues, ensuring all tasks map exclusively to the single target GitHub repository.

To map design artifacts to trackable GitHub issues, you need available design documents enumerating actionable tasks, a verified GitHub Git remote, and the speckit taskstoissues workflow to parse prerequisites and generate the issues.

Dependency-aware issue creation handles task prerequisites by parsing constraints from design artifacts and translating them into trackable GitHub issues that reflect the correct sequencing and task dependencies for developers.

Limitations when generating GitHub issues from tasks include requiring the Git remote to be a verified GitHub URL and enforcing scope validation that strictly prevents any cross-repo issue creation outside the target repository.