speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues with deduplication.

Updated Dec 12, 2024
One-click install
npx skills add https://github.com/kipariss1/czech_out_auto_bot --skill speckit-taskstoissues-kipariss1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/kipariss1/czech_out_auto_bot/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/kipariss1/czech_out_auto_bot --skill speckit-taskstoissues-kipariss1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually copying tasks from a spec-kit tasks.md file into GitHub issues is repetitive and error-prone, often producing duplicates or inconsistent titles. This Skill automates the conversion while checking existing issues to prevent duplicates. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries and creates GitHub issues with canonical titles like "T001: Create project structure" via the GitHub MCP server. - Deduplication: Fetches existing open and closed issues with cursor-based pagination and skips tasks that already have matching issues. - Extension Hooks: Supports optional and mandatory pre/post hooks defined in .specify/extensions.yml for customizable workflows. - Use Case: After generating a tasks.md file with spec-kit, run this Skill to publish every task as a tracked GitHub issue in the repository matching your git remote, without re-creating issues on repeat runs. ## Quick Start Ask the assistant to convert the current feature's tasks.md into GitHub issues for this repository.

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 tasks into GitHub issues?▼

Invoke the taskstoissues skill in a spec-kit project. It runs check-prerequisites.sh to locate tasks.md, parses each task line, and creates GitHub issues titled "T001: description" through the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?▼

It fetches existing open and closed issues using the GitHub MCP list_issues tool with cursor-based pagination, matches titles against the task ID pattern \bT\d{3}\b, and skips any task ID that already has an issue.

Does taskstoissues work with non-GitHub remotes?▼

No. The skill reads the git remote origin URL and only proceeds if it is a GitHub URL. It explicitly refuses to create issues in repositories that do not match the remote.

What are extension hooks in spec-kit taskstoissues?▼

Hooks are commands defined in .specify/extensions.yml under hooks.before_taskstoissues or hooks.after_taskstoissues. Optional hooks are suggested to the user, while mandatory hooks are executed automatically before the workflow continues.

Why are some tasks skipped when creating GitHub issues?▼

Tasks are skipped when their ID already appears in an existing issue title, which prevents duplicates on re-runs. The skill reports each skipped task, for example "T001 already has an issue, skipping".