Skip to main content
prompt CX Codex GP ChatGPT

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

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 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 .specify using 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.md

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

Similar prompts

All prompts for Agent setup: memory, context, orchestration →

From the same set83

The whole set →
speckit-companion The speckit-companion GitHub Copilot plugin displays Spec Kit progress for each project spec. Open its documents or start the next stage from the board beside the chat. ★ 110repo stars tasks Generates dependency-ordered tasks with estimates from a feature spec. Outputs a structured tasks.md file. CX Codex GP ChatGPT ★ 110repo stars specify The specify prompt turns a feature description and project context into a Markdown spec. Use it to define requirements before implementation. CX Codex GP ChatGPT ★ 110repo stars speckit.git.remote 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 cleanup-reviewer cleanup-reviewer reviews a specified slice of a repository cleanup diff and reports findings only. Use it when the review should stay within named files. CX Codex ★ 110repo stars speckit.git.initialize The speckit.git.initialize command sets up a Git repository in your project and creates an initial commit if one doesn't exist. Use it when starting a new project or preparing a template. CX Codex +1 ★ 110repo stars speckit-git-remote 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 speckit-git-initialize speckit-git-initialize creates a Git repository in the current project and makes its first commit. It fits spec-kit projects that need Git initialized. CX Codex +1 ★ 110repo stars

Project sponsors

Companies that keep this analytics open