speckit-taskstoissues

Convert project tasks into dependency-ordered GitHub issues.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/estaciolima/idle-improvement-game --skill speckit-taskstoissues-estaciolima
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/estaciolima/idle-improvement-game/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/estaciolima/idle-improvement-game --skill speckit-taskstoissues-estaciolima

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the friction of manually translating project tasks into tracked GitHub issues, ensuring that development work remains synchronized with design artifacts and project governance.

Core Features & Use Cases

  • Automated Issue Creation: Automatically generates GitHub issues from task lists defined in your project structure.
  • Dependency Ordering: Ensures issues are created in a logical, dependency-aware sequence.
  • Governance Integration: Respects project-specific principles and constraints defined in your constitution.
  • Use Case: When a feature design is finalized, use this skill to instantly turn your task list into a set of actionable, tracked GitHub issues linked to your repository.

Quick Start

Use the speckit-taskstoissues skill to convert all pending tasks in the current project into 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 project tasks into GitHub issues automatically?

To convert project tasks into GitHub issues automatically, this Skill reads task lists from your project structure and generates tracked issues. It bridges task planning and issue tracking by creating actionable GitHub entries based on finalized design artifacts.

How does dependency ordering work when generating GitHub issues from tasks?

Dependency ordering ensures GitHub issues are generated in a logical, dependency-aware sequence. The Skill evaluates task relationships within your project structure before creating the issues, maintaining correct execution order for development work.

Do I need a specific project structure to automate GitHub issue tracking?

Yes, automating GitHub issue tracking requires a valid spec-kit project structure. The Skill operates within this framework, reading design artifacts and adhering to project-specific constitution guidelines to properly generate the issues.

Can I use project governance rules to control issue creation?

Yes, you can use project governance to control issue creation. The Skill respects project-specific principles and constraints defined in your constitution, ensuring generated GitHub issues align with your established governance framework.

What is the best way to sync design artifacts with GitHub issue tracking?

The best way to sync design artifacts with issue tracking is using an automated conversion tool. This Skill translates finalized feature designs into tracked GitHub issues, keeping development work synchronized with project planning automatically.

Why does converting tasks to GitHub issues require a valid GitHub remote configuration?

Converting tasks to GitHub issues requires valid remote configuration to authenticate and write data to your repository. Without proper GitHub remote setup, the Skill cannot push the generated issues to the target project tracking system.