speckit-taskstoissues

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

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-taskstoissues-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-taskstoissues-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a spec-kit tasks.md file into GitHub issues is repetitive and error-prone, often producing duplicates or issues in the wrong repository. This Skill automates the conversion while verifying the Git remote and skipping tasks that already have issues. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (e.g., - [ ] T001 Create project structure) 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, matches task IDs using the \bT\d{3}\b pattern, and skips tasks already covered. - Safety Guards: Verifies the Git remote is a GitHub URL before creating anything and supports pre/post extension hooks from .specify/extensions.yml. - Use Case: After generating an implementation plan with spec-kit, run this Skill to publish every task as a trackable GitHub issue without re-checking which ones already exist. ## Quick Start Ask the AI 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?▼

Run the taskstoissues command in a spec-kit project after generating tasks.md. It parses each checkbox task, strips markers like [P] and [US#], and creates 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 with perPage 100 and cursor pagination, matching titles against the `\bT\d{3}\b` pattern. Tasks whose IDs already appear in an issue title are skipped and reported.

Does taskstoissues work with non-GitHub remotes like GitLab?▼

No. The skill reads `git config --get remote.origin.url` and only proceeds if the remote is a GitHub URL. It will never create issues in repositories that do not match the remote.

What project structure is required for taskstoissues?▼

A spec-kit project with a .specify/ directory is required. The skill runs check-prerequisites.sh with --require-tasks to locate tasks.md and optionally loads .specify/memory/constitution.md for governance constraints.

What are extension hooks in spec-kit commands?▼

Hooks are entries in .specify/extensions.yml under hooks.before_taskstoissues or hooks.after_taskstoissues. Enabled hooks run as slash commands before or after conversion; optional hooks are suggested, mandatory hooks are executed automatically.