speckit-taskstoissues_skill

Overview

This skill converts an existing tasks.md for a feature into actionable, dependency-ordered GitHub issues for the same project. It automates extraction of tasks, validates the Git remote is a GitHub URL, and creates one issue per task while preserving task IDs for traceability. The result is a set of issues ready for triage and progress tracking.

How this skill works

The skill runs a prerequisite checker script from the project root to locate the feature directory and available docs, extracting the absolute path to tasks.md. It verifies the project's Git remote is a GitHub URL, then iterates tasks and creates issues using a preferred issue-writing tool (for example gh issue create), including task IDs and concise titles. It enforces safety: it will not create issues unless the remote matches GitHub.

When to use it

• You have a feature with specs/<feature>/tasks.md and want issues created automatically.
• You need tasks converted into traceable, dependency-ordered issues for development planning.
• You want to ensure issues are created only in the correct GitHub project.
• You prefer using CLI tools (gh or similar) to create issues programmatically.
• You want task IDs preserved in issue bodies for linkage to design artifacts.

Best practices

• Run the provided prerequisite checker from the project root to ensure paths are absolute and tasks exist.
• Verify and test issue creation with a dry-run or a test branch before creating many issues in a real project.
• Use consistent labels and grouping preferences as input so created issues match your workflow.
• Keep issue titles concise; put task IDs in the body for reliable cross-referencing.
• Never proceed if git remote is not a GitHub URL—this prevents accidental issue creation elsewhere.

Example use cases

• Convert spec tasks for a new feature into a sequenced issue backlog automatically.
• Onboarding: generate issues from tasks.md so new contributors can pick clearly defined work items.
• Synchronize design artifacts with actionable engineering work by preserving task IDs and references.
• Batch-create labeled issues for a sprint planning session using the preferred CLI tool.