plan-epic

Decompose a product theme into a GitHub epic with linked child issues.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill plan-epic-hirokimry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-epic
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/plan-epic
Command: npx skills add https://github.com/hirokimry/vibecorp --skill plan-epic-hirokimry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of turning one large request into a structured epic with linked child issues, so teams can plan and execute complex work without losing scope or ownership.

Core Features & Use Cases

  • Epic decomposition: Breaks a theme into independent, test-aware child tasks that can be executed in parallel or in sequence.
  • GitHub issue orchestration: Creates the parent epic, opens child issues, and links them through GitHub sub-issues.
  • Guardrailed workflow: Validates the preset, respects approval gates, and keeps the process limited to issue creation and linking.
  • Use case: A CEO asks to "epicize" a platform initiative, and the Skill returns a plan, then creates the parent issue and child issues once approved.

Quick Start

Ask the AI to decompose your theme into an epic and child issues by saying: /vibecorp:plan-epic <theme>.

Frequently Asked Questions about plan-epic

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

FAQPage Schema
How do I break a large product theme into GitHub epics and linked child issues?

To break a large product theme into GitHub epics, this Skill decomposes the request into a parent epic and independent child tasks. It creates the issues and establishes reliable sub-issue linking through GitHub.

Can I automate task decomposition for GitHub issues without writing code?

Yes, you can automate task decomposition without changing code. The Skill orchestrates issue creation and sub-issue linking directly through GitHub CLI authentication, strictly limiting the automated workflow to issue tracking.

Do I need GitHub CLI authentication to create sub-issues for an epic?

Yes, GitHub CLI authentication is required to create sub-issues for an epic. The workflow relies on the GitHub CLI to validate presets, open child issues, and link them to the parent epic reliably.

How do approval gates work when planning GitHub epics?

Approval gates in epic planning ensure the generated task breakdown is reviewed before execution. The Skill validates presets and proposes a plan, then creates the parent and child issues only after explicit approval.

What is the best way to coordinate parallel tasks from a single GitHub epic?

The best way to coordinate parallel tasks from a single GitHub epic is structuring them as independent child issues. This Skill decomposes the theme into test-aware sub-issues linked to the parent for parallel or sequential execution.