speckit-taskstoissues

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

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-taskstoissues-apothecaryman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agent/skills/speckit-taskstoissues
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-taskstoissues-apothecaryman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the conversion of existing tasks into actionable GitHub issues, ensuring a smooth transition from task management to issue tracking within the spec-kit project structure.

Core Features & Use Cases

  • Task Conversion: Converts tasks into GitHub issues based on spec-kit design artifacts.
  • Dependency Ordering: Ensures issues are created in the correct order of dependency.
  • Compatibility: Requires spec-kit project structure with a .specify/ directory for full functionality.
  • Use Case: Ideal for teams using spec-kit for feature development, simplifying the process of tracking tasks and issues.

Quick Start

Run the speckit-taskstoissues command within your spec-kit project directory to convert tasks to GitHub issues.

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 to GitHub issues?▼

To convert spec-kit tasks to GitHub issues, run the conversion command within your spec-kit project directory. It automatically reads design artifacts from the .specify/ directory and creates corresponding issues in your GitHub repository.

Does spec-kit task conversion support dependency ordering for GitHub issues?▼

Yes, dependency ordering is supported during task conversion to GitHub issues. The Skill ensures issues are created in the correct order based on the spec-kit project structure, preventing tracking conflicts.

Do I need a .specify directory to automate GitHub issue creation from spec-kit?▼

Yes, you need a .specify directory to automate GitHub issue creation from spec-kit. The Skill requires the spec-kit project structure with this directory to read design artifacts and function properly.

Can I use this tool with any task management workflow or is spec-kit required?▼

Spec-kit is required. This Skill specifically requires the spec-kit project structure with a .specify directory to read design artifacts and function properly, meaning other task management workflows are not supported.

What is the best way to track spec-kit feature development tasks in GitHub?▼

The best way to track spec-kit feature development tasks in GitHub is by automating task conversion to GitHub issues. This ensures a smooth transition from design artifacts to issue tracking while maintaining dependency order.