Speckit taskstoissues
Skill dceoy/speckit-agent-skills/skills/speckit-taskstoissues
Agent skills for Spec Kit
npx -y skills add dceoy/speckit-agent-skills --skill speckit-taskstoissuesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
SKILL.md
1.5 KB, as published. Nobody here has run it
Spec 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