User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Pre-Execution Checks
Check for extension hooks (before tasks-to-issues conversion):
- Check if
.specify/extensions.yml exists in the project root.
- If it exists, read it and look for entries under the
hooks.before_taskstoissues key
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where
enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
- For each remaining hook, do not attempt to interpret or evaluate hook
condition expressions:
- If the hook has no
condition field, or it is null/empty, treat the hook as executable
- If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- When constructing slash commands from hook command names, replace dots (
.) with hyphens (-). For example, speckit.git.commit → /speckit-git-commit.
- For each executable hook, output the following based on its
optional flag:
- Optional hook (
optional: true):## Extension Hooks
**Optional Pre-Hook**: {extension}
Command: `/{command}`
Description: {description}
Prompt: {prompt}
To execute: `/{command}`
- Mandatory hook (
optional: false):## Extension Hooks
**Automatic Pre-Hook**: {extension}
Executing: `/{command}`
EXECUTE_COMMAND: {command}
Wait for the result of the hook command before proceeding to the Outline.
- If no hooks are registered or
.specify/extensions.yml does not exist, skip silently
Outline
- Run
.specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks 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
Post-Execution Checks
Check for extension hooks (after tasks-to-issues conversion):
Check if .specify/extensions.yml exists in the project root.
- If it exists, read it and look for entries under the
hooks.after_taskstoissues key
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where
enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
- For each remaining hook, do not attempt to interpret or evaluate hook
condition expressions:
- If the hook has no
condition field, or it is null/empty, treat the hook as executable
- If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- When constructing slash commands from hook command names, replace dots (
.) with hyphens (-). For example, speckit.git.commit → /speckit-git-commit.
- For each executable hook, output the following based on its
optional flag:
- Optional hook (
optional: true):## Extension Hooks
**Optional Hook**: {extension}
Command: `/{command}`
Description: {description}
Prompt: {prompt}
To execute: `/{command}`
- Mandatory hook (
optional: false):## Extension Hooks
**Automatic Hook**: {extension}
Executing: `/{command}`
EXECUTE_COMMAND: {command}
- If no hooks are registered or
.specify/extensions.yml does not exist, skip silently
1---
2name: "speckit-taskstoissues"
3description: "Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts."
4argument-hint: "Optional filter or label for GitHub issues"
5compatibility: "Requires spec-kit project structure with .specify/ directory"
6metadata:
7 author: "github-spec-kit"
8 source: https://skillmd.com/skills/unoplatform/speckit-taskstoissues
9 upstream: "templates/commands/taskstoissues.md"
10user-invocable: true
11disable-model-invocation: false
12---
13
14
15## User Input
16
17```text
18$ARGUMENTS
19```
20
21You **MUST** consider the user input before proceeding (if not empty).
22
23## Pre-Execution Checks
24
25**Check for extension hooks (before tasks-to-issues conversion)**:
26- Check if `.specify/extensions.yml` exists in the project root.
27- If it exists, read it and look for entries under the `hooks.before_taskstoissues` key
28- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
29- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
30- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
31 - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
32 - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
33- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
34- For each executable hook, output the following based on its `optional` flag:
35 - **Optional hook** (`optional: true`):
36 ```
37 ## Extension Hooks
38
39 **Optional Pre-Hook**: {extension}
40 Command: `/{command}`
41 Description: {description}
42
43 Prompt: {prompt}
44 To execute: `/{command}`
45 ```
46 - **Mandatory hook** (`optional: false`):
47 ```
48 ## Extension Hooks
49
50 **Automatic Pre-Hook**: {extension}
51 Executing: `/{command}`
52 EXECUTE_COMMAND: {command}
53
54 Wait for the result of the hook command before proceeding to the Outline.
55 ```
56- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
57
58## Outline
59
601. Run `.specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks` 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").
611. From the executed script, extract the path to **tasks**.
621. Get the Git remote by running:
63
64```bash
65git config --get remote.origin.url
66```
67
68> [!CAUTION]
69> ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL
70
711. 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.
72
73> [!CAUTION]
74> UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL
75
76## Post-Execution Checks
77
78**Check for extension hooks (after tasks-to-issues conversion)**:
79Check if `.specify/extensions.yml` exists in the project root.
80- If it exists, read it and look for entries under the `hooks.after_taskstoissues` key
81- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
82- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
83- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
84 - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
85 - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
86- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
87- For each executable hook, output the following based on its `optional` flag:
88 - **Optional hook** (`optional: true`):
89 ```
90 ## Extension Hooks
91
92 **Optional Hook**: {extension}
93 Command: `/{command}`
94 Description: {description}
95
96 Prompt: {prompt}
97 To execute: `/{command}`
98 ```
99 - **Mandatory hook** (`optional: false`):
100 ```
101 ## Extension Hooks
102
103 **Automatic Hook**: {extension}
104 Executing: `/{command}`
105 EXECUTE_COMMAND: {command}
106 ```
107- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently