Convert tasks from tasks.md into GitHub Issues with labels and dependencies. Use when exporting work items to GitHub, setting up project boards, or assigning tasks to team members.
83
92%
Does it follow best practices?
Impact
82%
1.74xAverage score across 14 eval scenarios
—
The risk profile of this skill
The canonical home for this skill is tessl-labs/intent-integrity-kit
Convert existing tasks into dependency-ordered GitHub issues for project tracking.
$ARGUMENTSYou MUST consider the user input before proceeding (if not empty).
Run prerequisites check:
bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/check-prerequisites.sh --phase 08 --jsonWindows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/check-prerequisites.ps1 -Phase 08 -Json
Parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Extract path to tasks.md.
If JSON contains needs_selection: true: present the features array as a numbered table (name and stage columns). Follow the options presentation pattern in conversation-guide.md. After user selects, run:
bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/set-active-feature.sh --json <selection>Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/set-active-feature.ps1 -Json <selection>
Then re-run the prerequisites check from step 1.
git config --get remote.origin.urlCRITICAL: Only proceed if remote is a GitHub URL (git@github.com: or https://github.com/). Otherwise ERROR.
Extract: Task IDs, descriptions, phase groupings, parallel markers [P], user story labels [USn], dependencies.
Title format: [FeatureID/TaskID] [Story] Description — feature-id extracted from FEATURE_DIR (e.g. 001-user-auth).
Body: use template from issue-body-template.md. Labels (create if needed): iikit, phase-N, us-N, parallel.
Use the Task tool to dispatch issue creation in parallel — one subagent per chunk of tasks (split by phase or user story). Each subagent receives:
gh issue create if available, otherwise curl the GitHub API# Preferred:
gh issue create --title "[001-user-auth/T012] [US1] Create User model" --body "..." --label "iikit,phase-3,us-1"CRITICAL: Never create issues in repositories that don't match the remote URL. Verify before dispatching.
Collect all created issue numbers from subagents. Verify all returned successfully before proceeding. If some failed: report failures, continue with successful issues only.
After all issues exist, edit bodies to add cross-references using #NNN syntax. Skip dependency links for any issues that failed to create.
Output: issues created (count + numbers), failures (count + details), link to repo issues list.
| Condition | Response |
|---|---|
| Not a GitHub remote | STOP with error |
| Issue creation fails | Report, continue with remaining issues |
| Partial failure | Link dependencies for successful issues only |
Run: bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/next-step.sh --phase 08 --json
Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/next-step.ps1 -Phase 08 -Json
Parse the JSON and present:
next_step will be null (workflow complete)alt_steps non-empty: list as alternativesIf on a feature branch, offer to merge:
git checkout main && git merge <branch>gh pr createFormat:
Issues exported! Review in GitHub, assign team members, add to project boards.
- Dashboard: file://$(pwd)/.specify/dashboard.html (resolve the path)855224b
Canonical home
since Feb 25, 2026
Also appears in
last in sync Apr 6, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.