skills.rest
CLOCKWORK-TEMPTATION
CLOCKWORK-TEMPTATIONCOMMUNITY
Explore all skills by this author →
GitHub

speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues via MCP.

Updated Aug 23, 2026
Search Tags:#automation#github#issues#tasks#spec-kit#convert#dependency
One-click install
npx skills add https://github.com/CLOCKWORK-TEMPTATION/plugin_01UphfxAg16yZB4YodKYf1RZ --skill speckit-taskstoissues-clockwork-temptation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/CLOCKWORK-TEMPTATION/plugin_01UphfxAg16yZB4YodKYf1RZ/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/CLOCKWORK-TEMPTATION/plugin_01UphfxAg16yZB4YodKYf1RZ --skill speckit-taskstoissues-clockwork-temptation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Automatically map design artifacts to GitHub issues in dependency order.
  • Maintain traceability between specs, tasks, and issues across repositories.
  • Use-case: Given a feature spec in .specify, generate coordinated issues for implementation.

Quick Start

Run the speckit-taskstoissues workflow to convert existing tasks into dependency-ordered GitHub issues.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert spec-kit tasks into GitHub issues automatically?▼

You can convert spec-kit tasks into GitHub issues by running the workflow, which reads design artifacts from a .specify directory and creates dependency-ordered issues via the GitHub MCP server.

What are dependency-ordered GitHub issues and why do they matter?▼

Dependency-ordered GitHub issues are repository tasks generated from design artifacts in a sequence that respects task dependencies, ensuring traceability and coordinated implementation across repositories.

Do I need a .specify directory to generate GitHub issues from tasks?▼

Yes, a .specify directory is required. This workflow is applicable to spec-kit style projects, relying on that directory to locate design artifacts and translate them into actionable GitHub issues.

Can I create GitHub issues across multiple repositories from design artifacts?▼

Yes, you can create issues across repositories. The workflow validates repository tasks, verifies the Git remote URL is a GitHub URL, and creates issues on the matching repository via the GitHub MCP server.

How does the GitHub MCP server validate repository tasks before creating issues?▼

The workflow validates repository tasks by verifying that the Git remote URL is a valid GitHub URL. This ensures issues are created on the correct matching repository via the MCP server.

Related Skills

Explore More Software Engineering Skills→
chaimtchaimt

speckit-taskstoissues

Convert project task lists into dependency-ordered GitHub issues.

Community
Advanced
dalagerdalager
1

V3 Swarm Coordination

Orchestrate a 15-agent hierarchical mesh for parallel v3 implementation with dependency enforcement.

Community
Advanced
xige169xige169

speckit-taskstoissues

Convert .specify/ design artifacts into dependency-ordered GitHub issues.

Community
Intermediate
xyphyxxyphyx

speckit-taskstoissues

Convert task lists and design artifacts into dependency-ordered GitHub issues.

Official
Intermediate