# speckit-taskstoissues

> Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature. Use when users invoke `/speckit.taskstoissues`, want to create GitHub issues from tasks, need to sync task list with issue tracker, or want to enable team collaboration on implementation. Requires a GitHub repository with proper remote configured.

- Author: Arty
- Repository: CluelessCatDevs/SpecKit-Skills
- Version: 20260120081718
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/CluelessCatDevs/SpecKit-Skills
- Web: https://mule.run/skillshub/@@CluelessCatDevs/SpecKit-Skills~speckit-taskstoissues:20260120081718

---

---
name: speckit-taskstoissues
description: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature. Use when users invoke `/speckit.taskstoissues`, want to create GitHub issues from tasks, need to sync task list with issue tracker, or want to enable team collaboration on implementation. Requires a GitHub repository with proper remote configured.
---

# SpecKit Tasks to Issues

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

## User Input

```text
$ARGUMENTS
```

Consider the user input before proceeding (if not empty).

## Workflow

### Step 1: Load Feature Context

Run the prerequisites script from repo root:

**Bash:**
```bash
.claude/skills/speckit-taskstoissues/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks
```

**PowerShell:**
```powershell
.claude/skills/speckit-taskstoissues/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
```

Parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute.

### Step 2: Extract Tasks Path

From the executed script output, extract the path to **tasks.md**.

### Step 3: Verify GitHub Remote

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.

If the remote is not a GitHub URL, stop and inform the user that this command only works with GitHub repositories.

### Step 4: Create GitHub Issues

For each task in tasks.md:
- Use the GitHub MCP server (if available) or `gh` CLI to create a new issue
- The issue should be in the repository that matches the Git remote

**CRITICAL SAFETY RULES**:
- **UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL**
- Verify the repository matches before each issue creation
- If MCP server is not available, use `gh issue create` command

### Issue Format

For each task, create an issue with:
- **Title**: Task description (from tasks.md)
- **Body**: Include task ID, phase, dependencies, and file paths
- **Labels**: Consider adding labels based on task type (setup, feature, test, etc.)

## Behavior Rules

- Only works with GitHub repositories
- Always verify remote URL before creating issues
- Never create issues in wrong repositories
- Report progress as issues are created
- Handle rate limiting gracefully