speckit-taskstoissues

Convert project tasks into dependency-ordered GitHub issues.

Updated May 31, 2026
One-click install
npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-taskstoissues-piklar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Piklar/Rizza-60/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-taskstoissues-piklar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the transition from project planning to execution by converting task lists into dependency-ordered GitHub issues, ensuring that project requirements are tracked directly in the development environment.

Core Features & Use Cases

  • Automated Issue Creation: Transforms task lists into actionable GitHub issues while maintaining project context.
  • Extension Hooks: Supports pre- and post-conversion hooks to integrate custom workflows or validation steps.
  • Use Case: After finalizing a feature specification, use this tool to automatically generate a series of linked GitHub issues based on the defined tasks, ensuring the development team has a clear, tracked roadmap.

Quick Start

Run the speckit-taskstoissues skill to convert all identified 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?

Yes, you can customize task conversion using pre- and post-conversion extension hooks. These hooks support integrating custom workflows or validation steps before and after issue creation.

Do I need a GitHub MCP server to create issues from spec-kit tasks?

Yes, you need GitHub MCP server integration and valid repository remote configuration to execute issue creation. The Skill relies on these to synchronize tasks directly with your repository's issue tracking.

How does dependency ordering work when generating GitHub issues from task lists?

Dependency ordering works by parsing task lists within feature directories and sequencing the resulting GitHub issues based on their defined relationships. This ensures the development team receives a tracked, logically ordered roadmap.

What's the best way to synchronize spec-kit design artifacts with GitHub issue tracking?

The best way to synchronize spec-kit artifacts is running this Skill to transform finalized feature specifications into linked GitHub issues. It maintains project context and automates the transition from planning to execution.