skills.rest
AhmedHassaan-7OS
AhmedHassaan-7OSCOMMUNITY
Explore all skills by this author →
GitHub

speckit-taskstoissues

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

Updated Sep 24, 2025
Search Tags:#automation#spec-kit#task-management#github-issues#design-artifacts#dependency-ordering
One-click install
npx skills add https://github.com/AhmedHassaan-7OS/money_follow --skill speckit-taskstoissues-ahmedhassaan-7os
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/AhmedHassaan-7OS/money_follow/tree/main/project_disc/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/AhmedHassaan-7OS/money_follow --skill speckit-taskstoissues-ahmedhassaan-7os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert scattered design tasks into structured, dependency-aware GitHub issues to streamline feature delivery.

Core Features & Use Cases

  • Automated task-to-issue mapping: Converts design artifacts into actionable GitHub issues with clear dependencies.
  • Dependency ordering: Creates issues in an order that respects task prerequisites.
  • Traceability: Links issues back to original design files for context and audit trails.

Quick Start

From the repository root, run the speckit taskstoissues process to generate GitHub issues from design artifacts.

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

Converting design artifacts into GitHub issues is done by extracting tasks from the .specify directory and mapping them into structured issues with dependency-aware ordering via the MCP server.

How does dependency-aware ordering work when creating GitHub issues?▼

Dependency-aware ordering for GitHub issues works by analyzing task prerequisites within design artifacts and sequencing issue creation so that foundational tasks are generated before dependent ones.

Can I create GitHub issues across multiple repositories from a single design source?▼

Yes, you can create issues across repositories by determining the repository remote from the .specify directory and ensuring the remote URL matches the target repository before generating issues.

Do I need a .specify directory structure to generate GitHub issues from tasks?▼

Yes, a .specify directory structure is required for task extraction, as the process scans this path to consolidate scattered design tasks into a prioritized set of GitHub issues.

What is the best way to maintain traceability between GitHub issues and design files?▼

Maintaining traceability between GitHub issues and design files is handled automatically by linking generated issues back to the original design artifacts for context and audit trails.

Why are my GitHub issues not matching the target repository remote URL?▼

GitHub issues may not match the target repository because the process validates the remote URL against the target repository during creation to prevent issues from being generated in the wrong location.

Related Skills

Explore More Product & Management Skills→
xige169xige169

speckit-taskstoissues

Convert .specify/ design artifacts into dependency-ordered GitHub issues.

Community
Intermediate
CalcMarkCalcMark
4

github-project

Manage GitHub issues and project boards with the GitHub CLI.

Official
Advanced
AustinZ21AustinZ21
4

speckit-taskstoissues

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

Community
Intermediate
ZainEldeen-Ashraf-Ibrahim-Ibrahim-SamakZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak

speckit-taskstoissues

Convert tasks into dependency-ordered GitHub issues linked to design artifacts.

Community
Advanced