Skip to main content
command CX Codex

speckit.taskstoissues — Claude Code command: turn tasks into issues

speckit.taskstoissues converts a list of tasks into dependency-ordered GitHub issues using design artifacts and project context. Works only with GitHub repositories.

no license ★ 117 updated 2026-10-29

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/speckit.taskstoissues.md
Open on GitHub

What speckit.taskstoissues does

The command reads tasks from your project, validates the remote repository, and creates GitHub issues via the GitHub MCP server. It runs prerequisite checks beforehand: verifies task files exist, documentation is accessible, and the remote URL matches GitHub.

It uses GitHub MCP for issue creation. Critical constraint: issues can only be created in repositories whose remote URL matches your current Git configuration. If the remote does not point to GitHub, the command will not proceed.

What it helps with

  • Convert task lists into structured GitHub issues
  • Organize issues by dependencies between work items
  • Link issues to design artifacts and project context
  • Automate issue creation from specifications without manual UI entry

Example prompts for the agent

  • Convert tasks from .specify/scripts/bash/check-prerequisites.sh into GitHub issues for the current feature
  • Create dependency-ordered issues from a task list based on project documentation
  • Turn tasks into issues after verifying the remote repository is on GitHub

How to install speckit.taskstoissues

Manually: put the files in place

.claude/commands/speckit.taskstoissues.md

Call it with /speckit.taskstoissues. For all projects use ~/.claude/commands/

Questions about speckit.taskstoissues

How do I install speckit.taskstoissues in Claude Code?

Place .claude/commands/speckit.taskstoissues.md in the .claude/commands/ directory at your project root. The command will be available as /speckit.taskstoissues.

What does speckit.taskstoissues do?

It reads tasks from your project, analyzes their dependencies based on design artifacts, and creates ordered GitHub issues. It only works if your remote repository is on GitHub.

Why won't the command create issues?

Check three things: task files must exist in the project, the remote URL (git remote -v) must point to GitHub, and you must have permission to create issues in that repository.

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →
speckit-taskstoissues github-spec-kit speckit-taskstoissues turns tasks from tasks.md into dependency-ordered GitHub issues. The skill is marked deprecated and points to a replacement extension. CX Codex +1 1,600installs issue-triage decebals Automate GitHub issue triage: sort incoming tasks by type (bugs, features, questions), assign priority labels, and flag duplicates. Use during backlog cleanup, weekly reviews, or after returning from time off. CX Codex +1 254installs label-context-mapping hiromaily The label-context-mapping skill maps GitHub labels to context documents and development skills automatically. Use it when creating tasks or working on them—the right contexts and verification commands load on their own. CX Codex +1 1installs speckit.git.remote alfredoperez speckit.git.remote detects the Git remote origin URL, parses repository ownership, and validates github.com hosts for downstream workflows. CX Codex +1 ★ 110repo stars speckit-git-remote spec-kit-core speckit-git-remote detects the Git remote URL and verifies GitHub connectivity for tasks like issue creation in spec-kit workflows. Designed for repositories structured with a .specify/ directory. CX Codex +1 ★ 110repo stars feature-dev official Anthropic feature-dev guides new feature work by exploring the codebase, asking for missing details, shaping the architecture, and waiting for approval before implementation. CX Codex +1 179installs security-hardening Seth Hobson security-hardening — a Claude Code command that runs a defense-in-depth security audit across application layers. It scans for vulnerabilities, builds a threat model, and waits for approval before fixing anything. CX Codex +1 437installs status Seth Hobson Shows Conductor project status, active tracks, and next actions. Use it to inspect task progress and spot blockers. CX Codex +1 348installs

From the same set9

speckit.plan speckit.plan executes implementation planning workflow to produce architectural artifacts and API contracts. CX Codex +1 ★ 117repo stars speckit.constitution The speckit.constitution command edits a project’s constitution and checks related templates and guidance for alignment. Use it when development principles or governance rules change. CX Codex +1 ★ 117repo stars speckit.tasks speckit.tasks builds a tasks.md file for a feature from plan.md and spec.md, splitting work into phases by user story priority. CX Codex +1 ★ 117repo stars speckit.analyze speckit.analyze inspects spec.md, plan.md, and tasks.md for conflicts, gaps, and constitution violations before code generation. Runs in read-only mode. CX Codex +1 ★ 117repo stars speckit.implement The speckit.implement command works through the tasks in tasks.md using the project plan and related documents. Use it to carry out an implementation plan in a defined order. CX Codex +1 ★ 117repo stars speckit.clarify speckit.clarify — a command that scans a feature spec for underspecified areas and asks up to 5 targeted questions to fill gaps before planning begins. CX Codex +1 ★ 117repo stars speckit.specify speckit.specify builds or updates a feature specification straight from a natural language prompt. Handy for structuring requirements and acceptance criteria before writing code. CX Codex +1 ★ 117repo stars speckit.checklist speckit.checklist builds a checklist for reviewing feature requirements, including unclear statements and missing scenarios. Use it before implementing a feature or reviewing its spec. CX Codex +1 ★ 117repo stars

Project sponsors

Companies that keep this analytics open