speckit-taskstoissues

スター11

フォーク0

更新日2026年3月31日 16:37

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

uespi-phb

uespi-phb/20261-pbk

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

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-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").
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, 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

このリポジトリの他の Skills

同じリポジトリ

speckit-analyze

uespi-phb/20261-pbk

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

2026-03-3111

speckit-checklist

uespi-phb/20261-pbk

Generate a custom checklist for the current feature based on user requirements.

2026-03-3111

speckit-clarify

uespi-phb/20261-pbk

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

2026-03-3111

speckit-constitution

uespi-phb/20261-pbk

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

2026-03-3111

speckit-implement

uespi-phb/20261-pbk

Execute the implementation plan by processing and executing all tasks defined in tasks.md

2026-03-3111

speckit-plan

uespi-phb/20261-pbk

Execute the implementation planning workflow using the plan template to generate design artifacts.

2026-03-3111

name	speckit-taskstoissues
description	Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
compatibility	Requires spec-kit project structure with .specify/ directory
metadata	{"author":"github-spec-kit","source":"templates/commands/taskstoissues.md"}

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-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").
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, 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