speckit.taskstoissues

You can convert tasks into dependency-ordered GitHub issues by extracting existing tasks from repository design artifacts and generating prioritized issues via the MCP server. The automation reads available artifacts and writes issues directly to the matching target repository.

Yes, you can generate GitHub issues automatically from design artifacts by running the conversion tool from the repository root. It reads the available design artifacts for the current feature and creates corresponding issues in the repository.

Remote URL verification checks that the target repository's remote URL matches the intended destination before writing any issues. This repository-scoped validation prevents unauthorized actions and blocks misdirected changes if the remote URL is mismatched.

If the remote URL is mismatched, the conversion process rejects the action and stops to prevent misdirected changes. The tool enforces this repository-scoped validation to ensure issues are only created in the correct target repository.

Yes, design artifacts and tasks must be present before conversion can proceed. The tool validates inputs and guards against unauthorized actions by only continuing when it successfully reads the necessary tasks and artifacts from the repository.

The best way to automate dependency-aware issue creation is to run the conversion tool from the repository root. It extracts tasks from existing artifacts, orders them by dependencies, and uses the MCP-based GitHub integration to write the prioritized issues automatically.