Skip to content
Development
Command

/speckit.taskstoissues

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

From plugin
sudocode
29012 skills12 commands
Install
> /plugin marketplace add sudocode-ai/sudocode
> /plugin install sudocode@sudocode-marketplace

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/speckit.taskstoissues

Context preview

What this command does when you run it.

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Command definition

speckit.taskstoissues.md
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

$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:

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

Ships withsudocode

Lightweight agent orchestration dev tool that lives in your repo

Get the whole plugin