agentleFS
neal-kyleneal-kyle/cosmion/.claude/skills/speckit-taskstoissues/SKILL.md

speckit-taskstoissues

Skill2 starsChanged 30 days agoMITView on GitHub

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

126 other projects use a version of this, 121 of them edited; 96 of 120 edited versions we compared changed its rules; 4 new projects in the last 4 weeks, against 11 the 4 before.

How people change it

96 of 120 edited versions changed its rules, and some changes recur.

Of the 120 edited versions we compared: 23 keep every rule, 1 is an older text, 96 made changes of their own.

Not in older versions

  1. Check if .specify/extensions.yml exists in the project root.missing from 1 of 1
  2. If it exists, read it and look for entries under the hooks.before_taskstoissues keymissing from 1 of 1
  3. If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, …missing from 1 of 1
  4. If the hook has no condition field, or it is null/empty, treat the hook as executablemissing from 1 of 1
  5. If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementationmissing from 1 of 1
  6. When constructing command invocations from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit → /speckit-git-commit.missing from 1 of 1
  7. If no hooks are registered or .specify/extensions.yml does not exist, skip silentlymissing from 1 of 1
  8. Only create issues for tasks that do not yet have a matching issue.missing from 1 of 1

Rules people drop

  1. If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, …dropped by 95 of 96
  2. Only create issues for tasks that do not yet have a matching issue.dropped by 44 of 96
  3. When constructing command invocations from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit → /speckit-git-commit.dropped by 14 of 96
  4. Check if .specify/extensions.yml exists in the project root.dropped by 2 of 96
  5. If it exists, read it and look for entries under the hooks.before_taskstoissues keydropped by 2 of 96
  6. If the hook has no condition field, or it is null/empty, treat the hook as executabledropped by 2 of 96
  7. If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementationdropped by 2 of 96
  8. If no hooks are registered or .specify/extensions.yml does not exist, skip silentlydropped by 2 of 96

Rules people add

  1. If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normallyadded by 93 of 96
  2. A rule we can't quote: its licence doesn't allow itadded by 2 of 96
  3. A rule we can't quote: its licence doesn't allow itadded by 2 of 96
  4. A rule we can't quote: its licence doesn't allow itadded by 2 of 96

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 4 new projects took it in the last 4 weeks, 0.4× the 4 weeks before.

Week of Sep 20: 3 new projectsWeek of Sep 27: 3 new projectsWeek of Oct 4: 2 new projectsWeek of Oct 11: 3 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 2 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use speckit-agent-context-update, speckit-baseline and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    speckit-agent-context-update

    Refresh the managed Spec Kit section in coding agent context file(s)

    Also in 13 projects that use this

  • patterson-agentsSkill

    speckit-baseline

    Generate feature specifications by analyzing existing source code.

    Also in 3 projects that use this

  • patterson-agentsSkill

    claude-command-converter

    Convert Claude Code commands (.claude/commands/*.md) to standard Agent Skills (skills/*/SKILL.md). Use when migrating slash commands to portable skill format, creating skills from existing commands, or standardizing command definitions across AI runtimes.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    agentic-workflows

    Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 4 projects that use this

  • GoogleSkill

    improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 1 is common, 0 are distinctive, and 8 are very specific to this project.

  • 1

    Common

    Most of the 120 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if .specify/extensions.yml exists in the project root.

    line 33
  2. Very specific:

    If it exists, read it and look for entries under the hooks.before_taskstoissues key

    line 34
  3. Very specific:

    If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the …

    line 35
  4. Very specific:

    If the hook has no condition field, or it is null/empty, treat the hook as executable

    line 38
  5. Very specific:

    If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation

    line 39
  6. Very specific:

    When constructing command invocations from hook command names, replace dots (.) with hyphens (-).

    line 40
  7. Very specific:

    If no hooks are registered or .specify/extensions.yml does not exist, skip silently

    line 64
  8. Very specific:

    Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root and parse FEATURE_DIR and …

    line 68
  9. Common:

    Only create issues for tasks that do not yet have a matching issue.

    line 83

“Common” is measured: kept by at least 6 in 10 of the 120 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deprecation Notice

You MUST display the following concise warning first, as the first step of this command and before the User Input and Pre-Execution Checks sections below:

⚠️ /speckit-taskstoissues is deprecated and will be removed in a future minor release. Use the bundled github extension instead: run specify extension add github, then invoke /speckit-github-taskstoissues.

Continue with the existing workflow unchanged. Do not install or enable the extension automatically, do not stop, and do not run the replacement command.

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, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, then 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 command invocations 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.
      After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal {command} id shown above, e.g. a skills-mode agent runs it as /skill:speckit-... or $speckit-...). Emitting the block alone does not run the hook.
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

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").
  2. IF EXISTS: Load .specify/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, build the set of task IDs you are about to process from tasks.md (each is a T followed by at least three digits, e.g. T001 — /speckit-converge assigns new IDs with T{M+1:03d}, which is a floor rather than a cap, so once a file has more than 999 tasks the IDs are four digits or longer). Then use the GitHub MCP server's list_issues tool to look for issues that already cover those IDs. Do not pass a state value, since omitting it makes the tool return both open and closed issues. Request perPage: 100 to keep the number of calls down, and since the tool uses cursor-based pagination, request pages with the after parameter (using the endCursor from the previous response). For each issue title, match it against the task ID pattern \bT\d{3,}\b (the {3,} accepts four-digit and longer IDs — with \d{3} a title containing T1000 would not match at all, because the trailing \b cannot fall between two digits, so that task would be silently neither deduplicated nor created; word boundaries still stop a token like ST001 from matching, and force the whole digit run to be consumed so T100 can never match inside T1000; this also recognises titles written as T001 ..., T001: ... or [T001] ...) and, when it matches one of your task IDs, mark that ID as already having an issue. Stop paginating as soon as every task ID has been matched, or when there are no more pages, so you do not keep fetching the whole repository's issue history once all task IDs are accounted for. This bounds the number of calls on repos with large issue histories and still prevents duplicates 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. Task lines in tasks.md start with a markdown checkbox, so first strip the leading - [ ] (and any [P] / [US#] markers) to recover the task ID and its description. Create the issue with a single canonical title of the form T001: <description>, with the ID written once followed by the task description (for example, the line - [ ] T001 Create project structure becomes the title 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 an issue, 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, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, then 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 command invocations 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}
      After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal {command} id shown above, e.g. a skills-mode agent runs it as /skill:speckit-... or $speckit-...). Emitting the block alone does not run the hook.
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.