speckit-taskstoissues

To convert design tasks into GitHub issues, this Skill extracts artifacts from a .specify directory and generates a dependency-ordered list of linked issues. It ensures traceable task execution by mapping design templates directly to your repository's issue tracker.

Yes, you can automatically map feature spec dependencies to GitHub issues. The Skill reads task lists derived from design templates in the .specify directory, derives dependencies from those artifacts, and creates linked issues in the correct progressive implementation order.

Yes, you need a .specify directory containing design artifacts and a derived task list. The Skill strictly scopes its task extraction to this directory to ensure accurate dependency mapping and prevent cross-repo risks when generating GitHub issues.

The Skill prevents cross-repo risks by requiring strict adherence to repository remotes. It requires access to the Git remote and a functioning MCP-like server to create issues, ensuring that generated GitHub issues map only to the correct target repository.

The best way to drive progressive implementation from feature specs is to generate dependency-ordered GitHub issues. By converting design artifacts into linked issues surfaced in the correct order, the Skill enables traceable and sequential task execution for the feature.