speckit-taskstoissues

Convert spec-kit repository task lists into dependency-ordered GitHub issues.

9|1|Updated Jul 21, 2025
One-click install
npx skills add https://github.com/usepowershell/PoshMcp --skill speckit-taskstoissues-usepowershell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/usepowershell/PoshMcp/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill speckit-taskstoissues-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts repository task lists and available design artifacts into explicit, actionable, dependency-ordered GitHub issues so maintainers and AI agents do not need to create or sequence issues manually.

Core Features & Use Cases

  • Task discovery: Executes the .specify prerequisite script to locate FEATURE_DIR and enumerate AVAILABLE_DOCS and tasks with absolute paths.
  • Safe issue creation: Retrieves and validates the git remote, proceeds only if it is a GitHub URL, and uses the GitHub MCP server to create issues in the matching repository.
  • Dependency-aware issue generation: Produces issues that preserve task dependency ordering and context for feature-based workflows.
  • Use Case: Convert a feature directory's task list into a set of linked, prioritized GitHub issues for cross-team planning and tracking.

Quick Start

Use the speckit-taskstoissues skill to convert the repository's feature tasks into dependency-ordered GitHub issues after running the .specify prerequisite script.

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 automatically?

To convert spec-kit tasks into GitHub issues, run the .specify checklist script to locate feature tasks, then use the GitHub MCP server to generate dependency-ordered issues in your repository.

What is the best way to create dependency-ordered GitHub issues from a task list?

Creating dependency-ordered GitHub issues from a task list requires extracting feature tasks from the .specify directory and using an MCP server to preserve task dependency ordering during issue generation.

Does this task generation work with repositories that do not use the spec-kit structure?

No, task generation only works with repositories following the spec-kit project structure. It requires a .specify directory to locate feature tasks and will not operate on non-matching repositories.

How does the skill validate the GitHub repository before creating issues?

The skill validates the GitHub repository by obtaining the git remote URL and checking that it points to GitHub. It only proceeds with MCP server issue creation if the remote URL is a valid GitHub link.

What prerequisites are needed to generate GitHub issues from repository tasks?

Prerequisites to generate GitHub issues from repository tasks include a spec-kit project structure, a validated GitHub remote URL, and executing the .specify checklist script to enumerate available docs and task paths.

Why are my spec-kit tasks not converting into GitHub issues?

Spec-kit tasks may not convert into GitHub issues if the .specify checklist script fails to locate them, or if the git remote URL does not point to a valid GitHub repository for MCP issue creation.