Skill

smith-taskstoissues

Converts feature tasks from tasks.md into actionable, dependency-ordered GitHub issues using design artifacts. Requires GitHub repo remote and tasks present.

Github

Git

Bash

git-workflow

automation

npx claudepluginhub attckdigital/smith

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Throughout this action, log significant events to the vault session log. Read the session log path from `.smith/vault/.current-session`. If the file is missing or the vault is not initialized, skip all logging silently.

SKILL.md

Similar Skills

speckit-taskstoissues

328

Converts tasks.md entries to GitHub issues in the matching repo using gh CLI, preserving task IDs. Useful for syncing tasks to issue tracking or project boards.

partme-ai-full-stack-skills

ralph-github-create-issues

Converts PRD markdown files from .claude/plans/, plans/, or prds/ into GitHub parent issues and story sub-issues with labels, links, dependencies, and quality gates.

1 file

smith-tasks

Generates dependency-ordered tasks.md from feature design artifacts like plan.md, spec.md, data-model.md, and contracts for phased implementation.

smith

Stats

Stars24

Forks4

Last CommitApr 13, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

### [HH:MM:SS] /smith-taskstoissues <event> **User Request:** > <verbatim user message that triggered this action> **Synthesized Input:** <brief summary> **Outcome:** <what happened> **Systems affected:** <system IDs>

Vault Logging

Throughout this action, log significant events to the vault session log. Read the session log path from .smith/vault/.current-session. If the file is missing or the vault is not initialized, skip all logging silently.

Append entries using this format:

### [HH:MM:SS] /smith-taskstoissues <event>

**User Request:**
> <verbatim user message that triggered this action>

**Synthesized Input:** <brief summary>
**Outcome:** <what happened>
**Systems affected:** <system IDs>

Log at these points:

On invocation — which tasks.md is being converted (feature name)
After issues created — count of GitHub Issues created, issue numbers

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