speckit-taskstoissues

Converts Rocket.Chat tasks into GitHub issues preserving order via smart contracts.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dundee31416/ugm_schedule --skill speckit-taskstoissues-dundee31416
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/dundee31416/ugm_schedule/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/dundee31416/ugm_schedule --skill speckit-taskstoissues-dundee31416

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert an existing task list into a set of ready-to-track GitHub issues that are actionable and ordered based on available design artifacts, reducing manual planning work.

Core Features & Use Cases

  • Prerequisite validation and task discovery: Checks repo structure and extracts the tasks list from the spec-kit tooling.
  • Dependency-ordered issue creation: Creates one GitHub issue per task, using the GitHub MCP server, so work is tracked in a usable sequence.
  • Repository safety guardrails: Refuses to proceed unless the Git remote is a GitHub URL, preventing issues from being created in the wrong place.
  • Use case: When you have multiple feature tasks derived from design artifacts, you can generate a clean GitHub issue backlog quickly and consistently from the spec-kit-defined tasks.

Quick Start

Tell the system to run speckit-taskstoissues with no filters to automatically generate GitHub issues for the discovered tasks from the current repo.

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?

To convert spec-kit tasks into GitHub issues, the skill validates your repository, extracts the task list from spec-kit artifacts, and creates one GitHub issue per task while preserving dependency ordering. It uses the GitHub MCP server to generate the backlog automatically.

What is dependency-ordered GitHub issue creation from design artifacts?

Dependency-ordered GitHub issue creation is the process of transforming a spec-kit task list into a sequenced backlog. It reads available design artifacts, preserves the required task execution sequence, and generates one trackable GitHub issue per task.

Do I need a GitHub remote to generate issues from a spec-kit task list?

Yes, you need a GitHub remote to generate issues from a spec-kit task list. The skill includes repository safety guardrails and refuses to proceed unless it validates that the Git remote is configured as a GitHub URL, preventing issues from being created in the wrong place.

How do I prepare my repository for automated task conversion to GitHub issues?

To prepare for automated task conversion, run the spec-kit prerequisite check script to validate your repository structure. This ensures the required design artifacts and task lists are correctly extracted before the GitHub MCP server creates the dependency-ordered issues.

Can I create a GitHub issue backlog from multiple feature tasks at once?

Yes, you can create a GitHub issue backlog from multiple feature tasks at once. By running the skill with no filters, it automatically discovers the spec-kit-defined tasks and generates a clean, consistently ordered set of GitHub issues for the entire repository.