smith-taskstoissues · git:20260413.7c3d3fc · 2026-04-13 · sha256 790d881d79072010
smith-taskstoissues git:20260413.7c3d3fcA
Immutable. This exact content is served forever at /api/v1/blob/790d881d79072010.
--- name: smith-taskstoissues description: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts. tools: ['github/github-mcp-server/issue_write'] --- ## 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: 1. **On invocation** — which tasks.md is being converted (feature name) 2. **After issues created** — count of GitHub Issues created, issue numbers ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## 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"). 1. From the executed script, extract the path to **tasks**. 1. Get the Git remote by running: ```bash git config --get remote.origin.url ``` > [!CAUTION] > ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL 1. 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