github-planning

Convert brainstormed ideas into GitHub Epics, sub-issues, and Projects.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/fyrsmithlabs/marketplace --skill github-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-planning
Source: https://github.com/fyrsmithlabs/marketplace/tree/main/plugins/fs-dev/skills/github-planning
Command: npx skills add https://github.com/fyrsmithlabs/marketplace --skill github-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates GitHub planning by transforming brainstormed ideas into structured GitHub artifacts, including Epics, native sub-issues, milestones, and Projects, to streamline how teams plan and execute work.

Core Features & Use Cases

  • Tiered planning: SIMPLE (single issue with a checklist), STANDARD (epic + native sub-issues + milestone), COMPLEX (epic + native sub-issues + Projects v2 board with automation)
  • Automated linking and organization: creates and links Epics with their sub-issues and project boards as appropriate
  • Cross-tier workflows: supports planning from initial brainstorm through delivery with bidirectional references and automation
  • Use cases: converting feature ideas into a deliverable GitHub structure, planning milestones, and tracking progress across teams

Quick Start

Start a planning session by issuing a brainstorm command (for example: /brainstorm "Add user authentication"). The skill will generate GitHub artifacts according to the selected tier, including Epics, sub-issues, milestones, and a Projects v2 board when applicable. Follow pre-flight prompts and review created artifacts in the GitHub UI.

Frequently Asked Questions about github-planning

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

FAQPage Schema
How do I automate converting feature ideas into GitHub Epics and sub-issues?

To automate GitHub planning, you can use a skill that converts brainstormed ideas into structured artifacts like Epics, native sub-issues, and Projects v2 boards. It applies tiered structures to streamline how teams plan and execute work.

What is the best way to structure GitHub Projects v2 with native sub-issues for milestones?

Structuring GitHub Projects v2 with sub-issues is best handled by tiered planning approaches. A complex tier creates an Epic with native sub-issues and a Projects v2 board with automation, while standard tiers use milestones for tracking.

Can I link GitHub Epics to sub-issues automatically using GraphQL?

Yes, you can link GitHub Epics to sub-issues automatically. The automation uses GraphQL-based sub-issue linking to ensure bidirectional tracing between parent Epics and their child issues within your repository.

How do I set up tiered GitHub planning for simple, standard, and complex workflows?

Tiered GitHub planning categorizes work into simple, standard, and complex structures. Simple uses a single issue with a checklist, standard includes an epic with sub-issues and a milestone, and complex adds a Projects v2 board with automation.

Does GitHub planning automation support bidirectional tracing and label taxonomy?

GitHub planning automation supports bidirectional tracing and label taxonomy integration. It ensures that Epics, sub-issues, and Projects v2 configurations maintain automated tracking and organizational consistency across workflows.