speckit-taskstoissues

Convert task list items into dependency-ordered GitHub issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual overhead of tracking project tasks by automatically converting them into dependency-ordered GitHub issues, ensuring your development backlog stays perfectly aligned with your design artifacts.

Core Features & Use Cases

  • Automated Synchronization: Parses task lists and creates corresponding GitHub issues with standardized titles.
  • Deduplication Logic: Intelligently checks existing repository issues to prevent duplicate creation for the same task ID.
  • Extensible Workflow: Supports pre- and post-execution hooks to integrate custom project-specific logic or validation steps.

Quick Start

Invoke the speckit-taskstoissues skill to scan your project tasks and generate missing GitHub issues for all pending items.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I automatically convert project tasks into GitHub issues?

Automated task synchronization parses task lists and creates structured GitHub issues with standardized titles. This process maintains dependency order and validates project-specific constitution constraints before generating the issues.

How does automated issue tracking handle duplicate GitHub issues for the same task?

Deduplication logic intelligently checks existing repository issues to prevent duplicate creation for the same task ID. Before creating a new issue, the system validates prerequisites against the current backlog to avoid redundancy.

Do I need a GitHub MCP server to sync spec-kit project tasks to issues?

A GitHub MCP server is required to perform issue listing and creation operations against the repository remote. This access enables the automated workflow to validate prerequisites and push structured issues directly to GitHub.

Can I add custom validation logic when converting task lists to GitHub issues?

The workflow supports pre- and post-execution hooks to integrate custom project-specific logic or validation steps. This extensible design allows you to enforce additional constitution constraints before synchronizing issues.

What happens to dependency order when generating GitHub issues from a task list?

The conversion process maintains dependency order by parsing task lists sequentially and creating corresponding GitHub issues. This ensures your development backlog stays perfectly aligned with design artifacts and project structure.