1.4 KiB
1.4 KiB
name, description, argument-hint, compatibility, metadata, user-invocable, disable-model-invocation
| name | description | argument-hint | compatibility | metadata | user-invocable | disable-model-invocation | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| speckit-taskstoissues | Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts. | Optional filter or label for GitHub issues | Requires spec-kit project structure with .specify/ directory |
|
true | true |
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
- 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:
# 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
- 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