speckit.taskstoissues — Claude Code prompt: tasks to GitHub Issues
speckit.taskstoissues — a prompt that converts a task list into structured GitHub Issues with dependency ordering. Works with design artifacts and requires GitHub MCP server access.
MIT ★ 110 updated 2026-10-19
.claude/commands/speckit.taskstoissues.mdWhat speckit.taskstoissues does
The prompt reads tasks from project configuration (via check-prerequisites.sh), verifies the repository is on GitHub, and creates Issues through the github/github-mcp-server/issue_write MCP server. Each task becomes a separate Issue ordered by execution dependencies and enriched with available documentation.
It uses a bash script to check prerequisites and extract task and artifact lists. The prompt requires a GitHub URL in Git remote—it will not proceed on GitLab, Gitea, or other hosts. You need GitHub MCP server access and a repository configured with .specify/scripts/bash/check-prerequisites.sh.
What it helps with
- convert a task list into GitHub Issues
- create Issues that respect task dependencies
- populate Issues with data from design artifacts
- verify the target repository matches the Git remote before creation
Example prompts for the agent
- Convert my tasks to GitHub Issues, respecting their dependencies
- Create Issues for each task in
.specifyusing available design artifacts - Transform my task list into structured Issues with descriptions and execution order
How to install speckit.taskstoissues
Manually: put the files in place
.claude/commands/speckit.taskstoissues.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about speckit.taskstoissues
How do I install speckit.taskstoissues in Claude Code?
Place the contents of .claude/commands/speckit.taskstoissues.md into your project's .claude/commands directory. The prompt will be available as a custom command in Claude Code.
What does speckit.taskstoissues do?
It converts project tasks (from .specify config) into ready-to-use GitHub Issues with dependency ordering and available documentation. Uses the GitHub MCP server to create Issues.
Why does the prompt require GitHub?
Issue creation happens through the GitHub MCP server. On other platforms (GitLab, Gitea), the prompt stops and refuses to proceed to prevent creating Issues in the wrong repository.
Source text
speckit.taskstoissues.md · MIT
--- description: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts. tools: ['github/github-mcp-server/issue_write'] --- ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## Outline 1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot"). 1. From the executed script, extract the path to **tasks**. 1. Get the Git remote by running: ```bash git config --get remote.origin.url ``` > [!CAUTION] > ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL 1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote. > [!CAUTION] > UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL
© alfredoperez · MIT · alfredoperez/speckit-companion