speckit-taskstoissues

To convert design artifact tasks into GitHub issues, you can use an automation workflow that detects a .specify/ project structure and publishes tasks to the corresponding repository. This ensures design specifications are tracked as concrete issues with dependencies.

Yes, you can create GitHub issues from tasks while preserving dependency order. The workflow validates the Git remote and creates issues sequentially, ensuring task sequencing across the project is maintained during issue generation.

Yes, converting tasks to GitHub issues requires a GitHub MCP server for publishing. The integration relies on the MCP server to interact with the target repository and create the issues from your design artifacts.

Repository scope validation works by checking that the Git remote is a GitHub URL and targeting only that specific repository. This enforces repository boundaries to prevent cross-repo actions when creating issues from your tasks.

The .specify/ project structure is the required directory layout that the workflow detects to identify design-artifact tasks. It serves as the source location from which tasks are extracted and converted into GitHub issues.

A key limitation is that issue creation enforces strict repository scope, preventing cross-repo actions. Additionally, it requires a GitHub MCP server and will fail if the Git remote is not a valid GitHub URL.