Skip to content

taskstoissues.md

Latest commit

 

History

History
103 lines (83 loc) · 4.83 KB

taskstoissues.md

File metadata and controls

103 lines (83 loc) · 4.83 KB
description Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
tools
github/github-mcp-server/list_issues
github/github-mcp-server/issue_write
scripts
sh ps
scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks
scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks

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
  • 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

  1. Run {SCRIPT} 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").
  2. IF EXISTS: Load /memory/constitution.md for project principles and governance constraints.
  3. From the executed script, extract the path to tasks.
  4. 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

  1. Fetch existing issues for deduplication: Before creating anything, use the GitHub MCP server's list_issues tool to list the repository's issues with state all, so both open and closed issues are covered. Build a set of task IDs that already have an issue by extracting the leading task ID (e.g. T001) from each issue title. This prevents duplicate issues when the command is re-run after tasks.md is regenerated or the skill is re-invoked.
  2. 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. Prefix the issue title with the task ID so it can be matched on later runs (for example, T001: Create project structure).
    • Skip any task whose ID is already present in the set of existing issues from the previous step, and report it (for example, T001 already has issue #42 — skipping).
    • Only create issues for tasks that do not yet have a matching issue.

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
  • 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