What if the remote URL is not a GitHub URL?

The process should abort and not create any issues; only proceed when the remote is a GitHub URL as required.

How do I handle quotes in arguments like I'm Groot?

Escape with backslashes as shown (e.g., I\'m Groot) or use double quotes where possible.

Can I edit or delete created issues later?

Yes. Once created, issues can be edited, updated, or closed via GitHub like any other issue.

speckit-taskstoissues

npx machina-cli add skill h3y6e/speckit-skills/speckit-taskstoissues --openclaw

Files (1)

SKILL.md

974 B

Speckit Taskstoissues Skill

Outline

Run scripts/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").
From the executed script, extract the path to tasks.
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

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

Source

git clone https://github.com/h3y6e/speckit-skills/blob/main/skills/speckit-taskstoissues/SKILL.mdView on GitHub

Overview

Converts items listed in tasks.md into GitHub issues using the MCP server to track work items in your repository project management. It enforces prerequisites, ensures the remote URL points to a GitHub repository, and creates one issue per task from the list.

How This Skill Works

Run the prereqs script from the repo root to emit a JSON with FEATURE_DIR and AVAILABLE_DOCS as absolute paths. From the output, extract the path to tasks and retrieve the Git remote with git config --get remote.origin.url, proceeding only if the remote is GitHub. For each task, use the GitHub MCP server to create a new issue in the repository matching the remote URL.

When to Use It

You have a tasks.md file at repo root that describes work items to implement
You want to open GitHub issues automatically to track each task
Preparing project management items after a task breakdown
Onboard automation for new projects and want consistent issue creation from tasks.md
You need to run this from the repo root using absolute paths to ensure reproducibility

Quick Start

Step 1: Run scripts/check-prerequisites.sh --json --require-tasks --include-tasks from the repo root
Step 2: Use the output to locate the tasks path, then run git config --get remote.origin.url and verify it is a GitHub URL
Step 3: For each task, use the GitHub MCP server to create a new issue in the repository tied to the remote URL

Best Practices

Run the prereqs script from the repo root to ensure absolute paths are used
Validate that the Git remote is GitHub before creating issues
Only create issues for tasks that exist in the tasks list
Use the MCP server to tie issues to the repository represented by the remote
Escape single quotes in CLI arguments when tasks contain quotes (eg I\'m Groot) as shown

Example Use Cases

A sprint kickoff where tasks.md entries are converted into issues to start tracking work
After task breakdown, each item becomes an actionable GitHub issue in the project
Maintaining parity between tasks.md and issues for a single repository
Automating issue creation for a new project by converting tasks.md during setup
Auditing task-to-issue creation to ensure the remote URL matches GitHub

Frequently Asked Questions

Add this skill to your agents