skills.rest
intel-agency
intel-agencyOFFICIAL
Explore all skills by this author →
GitHub

gh-issue-tracking-init

Initializes a GitHub plan-epic-story-task issue hierarchy with Projects v2 board, milestones, and labels.

Updated Jul 21, 2026
Search Tags:#automation#github#issue tracking#sub-issues#powershell#projects v2#planning hierarchy
One-click install
npx skills add https://github.com/intel-agency/gap-miner-v2-foxtrot79 --skill gh-issue-tracking-init-intel-agency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-issue-tracking-init
Source: https://github.com/intel-agency/gap-miner-v2-foxtrot79/tree/main/.agents/skills/gh-issue-tracking-init
Command: npx skills add https://github.com/intel-agency/gap-miner-v2-foxtrot79 --skill gh-issue-tracking-init-intel-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Setting up structured project planning on GitHub manually means creating dozens of issues, labels, milestones, and a Projects v2 board by hand, then linking them all together. This Skill automates the entire setup from a plan document, building a linked plan → epic → story → task hierarchy of sub-issues in one orchestrated run. ## Core Features & Use Cases - Hierarchy scaffolding: Parses a plan document (or plan_docs/ folder) into numbered plan, epic, story, and task issues, linked via GitHub sub-issues with blocking/blocked-by dependencies. - Board and taxonomy setup: Creates the canonical label set, milestones, and a Projects v2 board with Level, Priority, Estimate, and optional Phase fields. - Idempotent re-runs with dry-run: Every PowerShell operation script matches existing items and skips or updates rather than duplicating, and supports -DryRun previews before applying changes. - Use Case: Point the Skill at a repository containing a development plan, and it creates the full issue tree, links sub-issues, sets board fields, and records dependencies — ready for sprint tracking. ## Quick Start Ask the agent to set up GitHub issue tracking for your repository using the plan in the plan_docs folder, previewing with a dry run first.

Frequently Asked Questions about gh-issue-tracking-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a GitHub issue hierarchy from a plan document?▼

Invoke the skill with a target repo and a plan source; it parses the plan into plan, epic, story, and task nodes, then creates issues top-down and links them as sub-issues. With no arguments it defaults to the current repo and resolves the plan from the plan_docs folder.

How do I create GitHub sub-issues and issue dependencies with the gh CLI?▼

The skill's link-sub-issue.ps1 and set-dependency.ps1 scripts call the GitHub REST API through gh api, using each issue's numeric database ID. This works even on older gh versions like 2.46 that lack native sub-issue flags.

Can I re-run the setup without creating duplicate GitHub issues?▼

Yes, every operation script is idempotent: issues are matched by exact numbered title, and labels, milestones, fields, links, and dependencies are skipped or updated if they already exist. Re-running after editing the plan syncs additions without duplicates.

Does this work with GitHub Projects v2 custom fields?▼

Yes, ensure-project.ps1 creates the Project and its Level, Priority, Estimate, and optional Phase single-select fields via gh project commands. Project views cannot be created through the API, so the script prints the four recommended views to add manually in the UI.

What are the limitations of automating GitHub Projects with gh CLI?▼

Project views cannot be created programmatically, and gh cannot add options to an existing single-select field, so extra Status values like In Review must be added once in the UI. Defect-level issues are also deferred because the Level field options cannot be extended after creation.

What prerequisites are needed to run the issue tracking scripts?▼

You need PowerShell 7 or later and the GitHub CLI authenticated with the project scope, with GITHUB_TOKEN honored automatically. Scripts run from the repository root and every operation supports a -DryRun preview before applying changes.

Related Skills

Explore More Software Engineering Skills→
ripabakripabak

breakdown-feature-prd

Generate structured PRD documents from Epic summaries for engineering teams.

Community
Advanced
a-ng-da-ng-d
1

glab-issue

Manage GitLab issues from the CLI with create, list, view, and update commands.

Community
Intermediate
outfitter-devoutfitter-dev
28

Scenario Testing

Run end-to-end scenario tests against real dependencies without mocks.

Official
Advanced
Lobbi-DocsLobbi-Docs
18

jira

Automate Jira issue, sprint, board, and workflow tracking via API.

Official
Intermediate