speckit-taskstoissues

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

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill speckit-taskstoissues-ldilov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/ldilov/harness-forge --skill speckit-taskstoissues-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing tasks into a structured backlog by turning design artifacts into dependency-ordered GitHub issues that can be tracked and implemented efficiently.

Core Features & Use Cases

  • Dependency-ordered issue generation: Creates GitHub issues in the order dictated by task dependencies.
  • Artifact-driven planning: Leverages design artifacts stored in .specify/ to drive task creation.
  • Use Case: For a feature with multiple linked tasks, automatically generate issues and link them to a feature epic.

Quick Start

Run the speckit taskstoissues workflow to generate GitHub issues from your design artifacts, ordered by dependencies.

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 ordered by dependencies?

Dependency-ordered issue generation reads design artifacts stored in your .specify/ directory and automatically creates GitHub issues structured by their task dependencies. This organizes feature development backlogs directly from your design specs.

Do I need a specific project structure to generate GitHub issues from spec-kit artifacts?

Yes, generating GitHub issues from spec-kit artifacts requires a spec-kit project structure with a .specify/ directory. You also need access to the repository remote to ensure issues are created in the correct GitHub repository.

Can I link multiple generated GitHub issues to a feature epic automatically?

Yes, for a feature with multiple linked tasks, the workflow automatically generates issues from your backlog and links them to a feature epic. This enables efficient tracking and implementation of artifact-driven planning.

What's the best way to automate backlog creation from design artifacts in GitHub?

The best way to automate backlog creation from design artifacts in GitHub is using artifact-driven planning. This workflow converts existing design specs into structured, dependency-ordered GitHub issues that can be tracked and implemented efficiently.

Why does issue generation require access to the repository remote?

Issue generation requires repository remote access to ensure issues are created in the correct GitHub repository. This validates the target destination before automatically converting your backlog of tasks into tracked issues.