speckit-taskstoissues

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

130|14|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill speckit-taskstoissues-dmae97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/speckit-taskstoissues
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill speckit-taskstoissues-dmae97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit projects often have tasks defined in a way that is not directly actionable for tracking and collaboration, so this Skill converts existing tasks into ready-to-work GitHub issues with dependency-ordered execution.

Core Features & Use Cases

  • Dependency-ordered issue creation: Converts tasks into GitHub issues in the correct order based on their dependencies so downstream work is unblocked.
  • Spec-artifact driven mapping: Uses the available design artifacts from the .specify/ structure to determine what to create and how to represent it.
  • Guardrails via repo/remote validation: Ensures issues are created only when the detected GitHub remote matches the expected GitHub URL constraints.
  • Extension hooks support (optional and mandatory): Executes before/after hooks from .specify/extensions.yml when present, without attempting to interpret hook conditions itself.

Quick Start

Run speckit-taskstoissues in your spec-kit project root to convert the discovered tasks into GitHub issues for the configured remote.

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 for project tracking?

Converting spec-kit tasks into GitHub issues requires running the Skill in your project root to map .specify/ artifacts into dependency-ordered issues. It validates the GitHub remote origin and creates issues in the correct execution order for team tracking.

How does dependency ordering work when creating GitHub issues from spec-kit tasks?

Dependency ordering works by analyzing task relationships in .specify/ artifacts to sequence GitHub issues correctly. Downstream work is unblocked because prerequisite tasks are established as issues before dependent ones are generated for the team.

Do I need a GitHub remote origin configured to use spec-kit task conversion?

Yes, a valid GitHub remote origin is required. The Skill validates the detected GitHub remote against expected URL constraints to ensure issues are created in the correct repository before proceeding with task conversion.

Can I execute custom hooks when generating GitHub issues from spec-kit tasks?

Yes, custom hooks can be executed by defining them in .specify/extensions.yml. The Skill runs optional and mandatory before/after hooks during issue creation without interpreting hook conditions itself, enabling custom workflow orchestration.

What are the limitations of using spec-kit artifacts for GitHub issue creation?

The main limitation is that issue creation is restricted to workflows where tasks are derived from .specify/ artifacts. The Skill requires a GitHub MCP server and prerequisite checks via .specify/scripts/bash/check-prerequisites.sh to function correctly.