speckit-taskstoissues

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

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/alansmello/Amani_ImportadosERP --skill speckit-taskstoissues-alansmello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/alansmello/Amani_ImportadosERP/tree/main/.cursor/skills/speckit-taskstoissues
Command: npx skills add https://github.com/alansmello/Amani_ImportadosERP --skill speckit-taskstoissues-alansmello

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Generate GitHub issues from a preexisting task list, preserving task order and dependencies.
  • Align issues with design artifacts located in a .specify/ directory to maintain traceability.
  • Use cases include turning feature backlog tasks into issues for planning, sprint scoping, and cross-team coordination.

Quick Start

Create GitHub issues for your feature by converting your current task catalog into a dependency-aware issue set.

Frequently Asked Questions about speckit-taskstoissues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert feature development tasks into ordered GitHub issues?

Convert feature development tasks into ordered GitHub issues by reading a preexisting task list and generating dependency-aware issues. This aligns your backlog with design artifacts stored in a .specify/ directory to maintain project traceability.

Do I need a spec-kit project structure to generate dependency-ordered GitHub issues?

Yes, a spec-kit project structure is required to generate dependency-ordered GitHub issues. The tool reads task definitions from the .specify/ directory to create issues with appropriate metadata and dependencies.

What is the best way to align GitHub issues with design artifacts for sprint planning?

Align GitHub issues with design artifacts by converting a task catalog into a dependency-aware issue set. This preserves task order and dependencies, making it ideal for sprint scoping and cross-team coordination.

Can I preserve task dependencies when generating GitHub issues from a backlog?

Yes, you can preserve task dependencies when generating GitHub issues. The conversion process reads existing task definitions and creates issues that reflect the original task order and dependencies.

Why does converting tasks to GitHub issues require a .specify/ directory?

Converting tasks to GitHub issues requires a .specify/ directory because it contains the design artifacts and task definitions needed to generate issues with accurate dependencies and metadata.

Does speckit-taskstoissues work with existing GitHub repositories for project management?

Yes, speckit-taskstoissues works with existing GitHub repositories for project management. It converts your current task catalog into a dependency-aware issue set directly within your GitHub project.