sp-taskstoissues

Converts tasks.md task plans into dependency-aware GitHub issues.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-taskstoissues-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-taskstoissues
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-taskstoissues
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-taskstoissues-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It eliminates the manual work of transcribing a spec-kit task plan into GitHub issues while preserving execution ordering and dependency intent. ## Core Features & Use Cases - Task-to-Issue Projection: Reads the active feature's tasks.md and creates one GitHub issue per task via the GitHub MCP server. - Remote Safety Guardrails: Verifies the git remote is a GitHub URL and aborts before creating issues in any repository that does not match the configured remote. - Workflow Integration: Fits into the spec-kit planning pipeline with prerequisite checks, blocked-exit contracts, and subagent-based execution. - Use Case: After finalizing tasks.md for a new feature, run this skill to generate a tracked GitHub issue set that implementation work can follow without losing the original task structure. ## Quick Start Ask the agent to convert the current feature's tasks.md into GitHub issues for this repository.

Frequently Asked Questions about sp-taskstoissues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a tasks.md file into GitHub issues?▼

Run this skill after your tasks.md is stable. It resolves the active feature's task artifacts, confirms the git remote is a GitHub URL, and creates one issue per task through the GitHub MCP server.

How to generate GitHub issues from a spec-kit task plan?▼

Invoke the skill from a spec-kit project with a .specify directory. It runs the prerequisite check script to locate tasks.md, then mirrors the task graph as GitHub issues in the repository matching your remote.

Does this work with non-GitHub remotes like GitLab?▼

No. The skill explicitly aborts if the repository remote is not a GitHub URL, and it never creates issues in repositories that do not match the configured remote.

What prerequisites are needed before creating issues from tasks?▼

You need a spec-kit project structure with a .specify directory, a completed tasks.md for the active feature, a GitHub remote origin, and access to the GitHub MCP server for issue creation.

What happens if issue creation fails or is blocked?▼

The skill follows a blocked-exit contract defined in .specify/templates/workflow-blocker-template.md, preserving workflow state and recording structured recovery steps instead of returning a bare error.