speckit-taskstoissues

Convert design tasks from .specify directories into dependency-ordered GitHub issues.

180|11|Updated Apr 11, 2026

Search Tags:#automation #github #issues #tasks #spec-kit #project-management

Ready to run

npx skills add https://github.com/serverless-dna/tendril --skill speckit-taskstoissues-serverless-dna

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/serverless-dna/tendril/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/serverless-dna/tendril --skill speckit-taskstoissues-serverless-dna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing design tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Core Features & Use Cases

Automates mapping tasks to issues with dependencies derived from design artifacts in the .specify directory.
Generates dependency-ordered issue lists to drive progressive implementation and traceability.
Use Case: Given a feature spec in .specify, this Skill converts tasks into linked issues and surfaces them in the correct order.

Quick Start

Convert the current design tasks into a set of GitHub issues ordered by their dependencies.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema

How do I convert design tasks into ordered GitHub issues?▼

To convert design tasks into GitHub issues, this Skill extracts artifacts from a .specify directory and generates a dependency-ordered list of linked issues. It ensures traceable task execution by mapping design templates directly to your repository's issue tracker.

Can I automatically map feature spec dependencies to GitHub issues?▼

Yes, you can automatically map feature spec dependencies to GitHub issues. The Skill reads task lists derived from design templates in the .specify directory, derives dependencies from those artifacts, and creates linked issues in the correct progressive implementation order.

Do I need a .specify directory to generate dependency-ordered GitHub issues?▼

Yes, you need a .specify directory containing design artifacts and a derived task list. The Skill strictly scopes its task extraction to this directory to ensure accurate dependency mapping and prevent cross-repo risks when generating GitHub issues.

How does the Skill prevent cross-repo risks when creating GitHub issues?▼

The Skill prevents cross-repo risks by requiring strict adherence to repository remotes. It requires access to the Git remote and a functioning MCP-like server to create issues, ensuring that generated GitHub issues map only to the correct target repository.

What is the best way to drive progressive implementation from feature specs?▼

The best way to drive progressive implementation from feature specs is to generate dependency-ordered GitHub issues. By converting design artifacts into linked issues surfaced in the correct order, the Skill enables traceable and sequential task execution for the feature.