speckit-taskstoissues

Convert spec-kit task definitions into dependency-ordered GitHub issues.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/youssif-mohamed1/Smart-LMS-with-AI-Proctoring --skill speckit-taskstoissues-youssif-mohamed1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/youssif-mohamed1/Smart-LMS-with-AI-Proctoring/tree/main/source%20code/LMS-Project/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/youssif-mohamed1/Smart-LMS-with-AI-Proctoring --skill speckit-taskstoissues-youssif-mohamed1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of manually translating scattered task definitions and design artifacts into a clear backlog of GitHub issues with correct dependencies and execution order.

Core Features & Use Cases

  • Dependency-ordered issue creation: Converts existing tasks into actionable GitHub issues arranged to reflect prerequisite relationships.
  • Spec-kit project validation: Requires the presence of a spec-kit style project structure (including the .specify directory) to locate tasks and related artifacts.
  • Optional extensibility via hooks: Runs configurable pre- and post-conversion extension hooks from .specify/extensions.yml when present and enabled, allowing customization without changing the core logic.

Quick Start

Use the speckit-taskstoissues skill to convert the current spec-kit tasks in your project into GitHub issues for your 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 with dependency ordering?

To convert spec-kit tasks into GitHub issues with dependency ordering, use a task-to-issue conversion skill that reads .specify artifacts and creates issues arranged by prerequisite relationships. It validates the origin remote is a GitHub URL before creating issues.

What is needed to generate GitHub issues from a spec-kit project structure?

Generating GitHub issues from a spec-kit project structure requires a repository containing .specify artifacts and a valid GitHub origin remote URL. The conversion process locates tasks within the .specify directory to ground issue creation in available design inputs.

Can I run custom scripts before or after converting tasks to GitHub issues?

You can run custom scripts before or after converting tasks to GitHub issues by configuring pre- and post-conversion extension hooks within the .specify/extensions.yml file. These optional hooks execute automatically when present and enabled.

Does task-to-issue conversion work without a GitHub remote configured?

Task-to-issue conversion does not work without a GitHub remote configured. The process requires absolute path resolution and explicitly validates that the repository's origin remote points to a GitHub URL before it can create any issues.

How are task dependencies preserved when creating GitHub issues from design artifacts?

Task dependencies are preserved when creating GitHub issues by translating prerequisite relationships from the original task definitions into the newly created issues' actionable structure. This ensures the generated backlog reflects the correct execution order.