speckit-taskstoissues

Convert tasks from a .specify/ directory into dependency-ordered GitHub issues.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/apply-the/canon --skill speckit-taskstoissues-apply-the
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/apply-the/canon --skill speckit-taskstoissues-apply-the

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Task extraction: reads tasks from a .specify/ directory and generates corresponding GitHub issues in the target repository.
  • Dependency ordering: organizes issues based on cross-task dependencies to maintain logical work flow.
  • Use Case: In a spec-kit project, convert all design-originated tasks into tracked GitHub issues to drive progress and traceability.

Quick Start

Create GitHub issues from the tasks defined in the .specify directory of the repository.

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?

To convert spec-kit tasks into GitHub issues, the Skill reads tasks from a .specify/ directory and generates corresponding issues in the repository. It requires a spec-kit project and uses the GitHub MCP server to create the issues.

Does generating GitHub issues from a .specify directory require a remote origin URL?

Yes, generating GitHub issues requires the repository to have a GitHub remote origin URL. The Skill matches this Git remote origin URL to identify the target repository before creating the issues.

How are dependency orders handled when creating GitHub issues from spec-kit projects?

Dependency orders are handled by organizing the generated GitHub issues based on cross-task dependencies. This maintains a logical work flow and ensures actionable issues are created in the correct sequence.

Can I use this to generate issues for project management without manual dependency sorting?

Yes, you can generate issues for project management without manual sorting. The Skill automatically extracts design-originated tasks and applies dependency ordering to create tracked, actionable GitHub issues.

What limitations exist when automating GitHub issue creation from design artifacts?

A key limitation is that automating GitHub issue creation strictly requires a .specify/ directory in a spec-kit project. Additionally, the current Git repository must have a valid GitHub origin URL configured to function.