speckit-taskstoissues

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

Updated Jan 5, 2026

Search Tags:#github #task planning #issues #speckit #repository validation #dependency ordering

Ready to run

npx skills add https://github.com/demersonpolli/basic-interpreter --skill speckit-taskstoissues-demersonpolli

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit design tasks are converted into concrete, dependency-ordered GitHub issues so teams can track implementation work from the available feature and document inputs.

Core Features & Use Cases

Dependency-ordered issue creation: Creates one issue per discovered task to preserve execution order and reduce coordination overhead.
Repository-safe behavior: Refuses to proceed unless the detected git remote is a GitHub URL, preventing accidental issue creation in the wrong place.
Spec-kit structure integration: Uses the spec-kit .specify layout and prerequisite checking to derive FEATURE_DIR and AVAILABLE_DOCS for consistent conversions.

Quick Start

Run speckit-taskstoissues with the optional argument filter and let it generate GitHub issues from the repo’s task list in the correct dependency order.

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 in dependency order?▼

To convert spec-kit tasks into GitHub issues, the Skill extracts the tasks path via prerequisite PowerShell scripts and uses the GitHub MCP server to create issues sequentially. It requires deriving FEATURE_DIR and AVAILABLE_DOCS from the .specify layout before generating the dependency-ordered issues.

What does dependency-ordered issue creation do for task planning in a GitHub repository?▼

Dependency-ordered issue creation generates one GitHub issue per discovered spec-kit task while preserving the required execution sequence. This task planning approach reduces coordination overhead by ensuring teams address implementation work in the correct dependency order.

Does this task conversion work with any git remote or only GitHub repository URLs?▼

This task conversion exclusively targets GitHub repository URLs. It validates the detected git remote.origin.url and refuses to proceed unless it confirms the remote is GitHub, preventing accidental issue creation in the wrong repository.

What's the best way to automate spec-kit task extraction before creating GitHub issues?▼

The best way to automate spec-kit task extraction is running the prerequisite PowerShell check script to validate the environment and extract the tasks path. This derives FEATURE_DIR and AVAILABLE_DOCS from the .specify scripts to prepare for issue generation.

Why does spec-kit task to issue conversion fail when AVAILABLE_DOCS or FEATURE_DIR cannot be derived?▼

Conversion fails when FEATURE_DIR and AVAILABLE_DOCS cannot be derived from the .specify scripts because these parameters are required to locate and parse the task list. The Skill applies only when these inputs are available for transforming tasks into GitHub issues.