speckit-taskstoissues

Convert spec-kit feature task lists into dependency-ordered GitHub issues.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/basmawebinfo-hub/lover-diet-center --skill speckit-taskstoissues-basmawebinfo-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/basmawebinfo-hub/lover-diet-center/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/basmawebinfo-hub/lover-diet-center --skill speckit-taskstoissues-basmawebinfo-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts an existing feature task list into actionable GitHub issues so teams can move from specification artifacts to trackable execution without manually rewriting work items.

Core Features & Use Cases

  • Task-to-Issue Conversion: Reads feature task definitions from a spec-kit project and turns each task into a corresponding GitHub issue.
  • Dependency-Aware Workflow: Preserves task ordering so issues reflect the intended implementation sequence for a feature.
  • Safety and Governance Checks: Verifies prerequisites, loads project constitution guidance when available, and only proceeds when the repository remote matches a GitHub URL.
  • Extension Hook Support: Detects optional and mandatory pre- and post-execution hooks from the spec-kit extensions configuration.
  • Use Case: After generating implementation tasks for a new product feature in a spec-kit repository, use this Skill to publish the backlog directly into the correct GitHub repository for engineering execution.

Quick Start

Ask the AI to convert the current spec-kit feature tasks into dependency-ordered GitHub issues for the repository remote.

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 feature tasks into GitHub issues in dependency order?

Spec-kit feature tasks are converted into GitHub issues by reading the .specify project structure, validating prerequisites, and creating issues sequentially in the matching GitHub repository to preserve dependency ordering.

What prerequisites are needed to create GitHub issues from a spec-kit repository?

Creating GitHub issues from spec-kit requires a .specify project structure, generated task files, an optional constitution configuration, and a verified GitHub-backed remote URL on the repository to ensure correct issue delivery.

Does spec-kit issue creation support extension hooks for pre and post-execution workflows?

Spec-kit issue creation detects optional and mandatory pre- and post-execution hooks from the spec-kit extensions configuration, allowing custom workflow integration before or after converting feature tasks into GitHub issues.

Can I publish a feature backlog directly to GitHub from spec-kit task definitions?

Publishing a feature backlog directly to GitHub is supported by converting existing spec-kit task definitions into trackable GitHub issues, moving teams from specification artifacts to execution without manual rewriting.

Why does spec-kit issue creation require a GitHub remote URL verification?

Remote URL verification restricts issue creation to the matching GitHub repository, ensuring safety and governance by preventing tasks from being published to incorrect or unauthorized remote destinations.

What is the best way to automate feature planning from spec-kit to GitHub issue tracking?

Automating feature planning from spec-kit to GitHub is achieved by converting dependency-ordered task lists into actionable issues, applying prerequisite validation and hook handling to maintain implementation sequence.