speckit-taskstoissues
npx machina-cli add skill dceoy/speckit-agent-skills/speckit-taskstoissues --openclawSpec Kit Tasks-to-Issues Skill
When to Use
- You want to convert
tasks.mdinto GitHub issues in the same repository.
Inputs
specs/<feature>/tasks.md- The repository's Git remote URL
- Any user-provided issue labeling or grouping preferences
If tasks are missing, ask the user to run speckit-tasks first.
Workflow
- Run
.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasksfrom repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). - From the executed script, extract the path to tasks.
- Get the Git remote by running:
git config --get remote.origin.url
[!CAUTION] ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL
- For each task in the list, create a new issue in the repository that matches the Git remote.
- Prefer a GitHub issue-writing tool if available (e.g., MCP server or
gh issue create). - Keep titles concise and include the task ID in the issue body for traceability.
- Prefer a GitHub issue-writing tool if available (e.g., MCP server or
[!CAUTION] UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL
Outputs
- GitHub issues created from
tasks.md(one per task), in the repository matching the Git remote
Source
git clone https://github.com/dceoy/speckit-agent-skills/blob/main/skills/speckit-taskstoissues/SKILL.mdView on GitHub Overview
Speckit-taskstoissues converts specs/<feature>/tasks.md into actionable GitHub issues for the corresponding feature. It orders issues by task dependencies inferred from design artifacts, making implementation flow clearer. It also enforces creating issues only in the repository that matches the Git remote and stitches traceability by including the task ID in each issue body.
How This Skill Works
From the repo root, it runs the prereqs to locate tasks.md, validates the GitHub remote URL, and then creates an issue per task in the matching repository. It leverages a GitHub writing tool (gh or MCP) when available and appends the task ID for traceability, while applying any user-provided labels or groupings.
When to Use It
- Convert specs/<feature>/tasks.md into GitHub issues in the same repository
- Maintain dependency order across tasks based on design artifacts
- Generate traceable issues by embedding the task ID in each issue
- Apply user-specified labels or grouping to organize issues
- Validate the remote repository is hosted on GitHub before creating issues
Quick Start
- Step 1: From repo root, run the prerequisite script to locate specs and tasks
- Step 2: Confirm the Git remote is a GitHub URL and extract the repo name
- Step 3: Create one GitHub issue per task using a tool like gh or MCP, including the task ID in each body and applying any labels
Best Practices
- Ensure you have generated tasks.md with the required IDs
- Run the prerequisites script from repo root with absolute paths
- Double-check that git remote.origin.url points to a GitHub URL before creating issues
- Include the feature name and task IDs in issue bodies for traceability
- Use a GitHub issue writing tool (gh or MCP) when available to streamline creation
Example Use Cases
- Feature: payments — tasks.md lists T1, T2, T3; issues created in the payments-backend repo with IDs in bodies
- Feature: onboarding — tasks with dependencies order issues so T1 precedes T2 in the backlog
- Missing tasks.md triggers a prompt to run speckit-tasks first
- Design references included in each issue body to show alignment with artifacts
- Issues labeled with spec and design-review per user preferences
