Menu
Convert tasks from tasks.md into GitHub issues. Use after task breakdown to track work items in GitHub project management.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
AI-driven documentation repair with structured research workflow, template-aware generation, and quality validation loops. Generates or fixes canonical documentation by researching the actual codebase, not using placeholders. Iterates until guard passes.
Run DocGuard guard validation against Canonical-Driven Development standards. Parses output, triages severity, suggests targeted fixes, and optionally chains to docguard-fix for automated remediation. Use as a quality gate before commits or after implementation phases.
Cross-document consistency analysis and quality assessment. Performs read-only analysis across all canonical docs, identifies drift, coverage gaps, and quality issues. Produces a structured report with severity-ranked findings. Modeled after speckit-analyze.
CDD maturity assessment with category-aware improvement roadmap. Runs scoring engine, analyzes category breakdown, identifies highest-impact improvements, and generates a before/after improvement plan with projected score gains.
Keep canonical documentation ALWAYS UP TO DATE. Refreshes code-truth doc sections in place (mechanical, idempotent, preserves human prose) and flags the prose sections you must review when code changes.
Perform cross-artifact consistency analysis across spec.md, plan.md, and tasks.md. Use after task generation to identify gaps, duplications, and inconsistencies before implementation.
| name | speckit-taskstoissues |
| description | Convert tasks from tasks.md into GitHub issues. Use after task breakdown to track work items in GitHub project management. |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"templates/commands/taskstoissues.md"} |
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
.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").git config --get remote.origin.url
[!CAUTION] ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL
[!CAUTION] UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL