40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
---
|
|
name: "speckit-taskstoissues"
|
|
description: "Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts."
|
|
argument-hint: "Optional filter or label for GitHub issues"
|
|
compatibility: "Requires spec-kit project structure with .specify/ directory"
|
|
metadata:
|
|
author: "github-spec-kit"
|
|
source: "templates/commands/taskstoissues.md"
|
|
user-invocable: true
|
|
disable-model-invocation: true
|
|
---
|
|
|
|
|
|
## User Input
|
|
|
|
```text
|
|
$ARGUMENTS
|
|
```
|
|
|
|
You **MUST** consider the user input before proceeding (if not empty).
|
|
|
|
## Outline
|
|
|
|
1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from 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").
|
|
1. From the executed script, extract the path to **tasks**.
|
|
1. Get the Git remote by running:
|
|
|
|
```bash
|
|
# Prefer jj, fallback to git
|
|
jj git remote list 2>/dev/null || git config --get remote.origin.url
|
|
```
|
|
|
|
> [!CAUTION]
|
|
> ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL
|
|
|
|
1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
|
|
|
|
> [!CAUTION]
|
|
> UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL
|