speckit-taskstoissues

Convert design-derived tasks into dependency-ordered GitHub issues aligned to feature milestones.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/tellbom/process --skill speckit-taskstoissues-tellbom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/tellbom/process/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/tellbom/process --skill speckit-taskstoissues-tellbom

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

  • Automatically translate design artifacts into GitHub issues with clear dependencies.
  • Produce a prioritized issue list aligned with feature milestones.
  • Integrates with .specify/extensions.yml to manage pre/post execution hooks.

Quick Start

Run speckit-taskstoissues on your project to convert existing tasks into a dependency-ordered set of 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 design artifacts into GitHub issues with dependencies?

You can convert design artifacts into GitHub issues by running a conversion tool that reads existing tasks and produces a linked, dependency-aware issue set aligned to feature milestones for your repository.

What is dependency-aware issue tracking for feature milestones?

Dependency-aware issue tracking organizes GitHub issues so that prerequisite tasks are linked and ordered before downstream work. This ensures each issue within a feature milestone is actionable and sequenced based on its relationships to other tasks.

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

Yes, generating GitHub issues from tasks requires a spec-kit style project structure with a .specify/ directory. Optional extension hooks can be configured within .specify/extensions.yml for pre and post execution.

Can I automate issue tracking across multiple repositories during feature development?

Automating issue tracking across repositories is supported by converting design-derived tasks into a linked set of GitHub issues aligned to feature milestones. This is useful for software teams managing feature development spanning multiple repositories.

What's the best way to manage pre and post execution hooks when creating GitHub issues?

Managing pre and post execution hooks is handled through the .specify/extensions.yml configuration file. This integrates with the issue generation process to manage hooks before and after converting design tasks into GitHub issues.

Why are my design tasks not converting into dependency-ordered GitHub issues?

Design tasks may not convert if the project lacks the required .specify/ directory structure or if GitHub is not properly configured as the target repository. The conversion relies on a spec-kit style project structure and valid design artifacts.