epic-planner

Converts feature-area ideas into codebase-grounded roadmaps and GitHub epic issues.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/alkampfergit/cisharpai --skill epic-planner-alkampfergit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-planner
Source: https://github.com/alkampfergit/cisharpai/tree/main/.claude/skills/epic-planner
Command: npx skills add https://github.com/alkampfergit/cisharpai --skill epic-planner-alkampfergit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a rough feature idea into trackable GitHub issues often produces roadmaps built on assumptions about what the codebase contains, leading to misdirected work. This Skill grounds every roadmap claim in verified code evidence and produces dependency-ordered epic and child issues with explicit decisions or open questions. ## Core Features & Use Cases - Evidence-Based Roadmapping: Greps the codebase, checks branches and PRs, and verifies external claims before writing any roadmap, with file:line citations for load-bearing statements. - Explicit Prioritization Filter: Defines a one-sentence scope test applied to every candidate item, including a documented out-of-scope table to prevent re-proposals. - GitHub Epic Creation: Verifies gh CLI identity, creates a tracking epic plus dependency-ordered child issues, each carrying a settled design decision or an explicit open question. - Use Case: A maintainer wants to plan a new provider-integration initiative for a .NET LLM client library. The Skill inventories existing interfaces, writes a phased roadmap, then creates an epic with child issues that an automated coding bot can implement without guessing. ## Quick Start Ask the assistant to plan out a new feature area and break it into a roadmap with GitHub epic and child issues.

Frequently Asked Questions about epic-planner

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

FAQPage Schema
How do I break a feature idea into GitHub issues?▼

Start by grounding a roadmap in what the codebase actually contains, then create one tracking epic and dependency-ordered child issues. Each child issue should state its dependencies, a settled design decision or explicit open question, and anything deliberately deferred.

How to create a GitHub epic with child issues using gh CLI?▼

Verify your identity first with gh api user --jq .login, then create the tracking issue and child issues with gh issue create. Link children via GitHub's native sub-issue mechanism rather than prose references so progress tracking survives issue renumbering.

What should a good implementation issue contain for a coding bot?▼

Each issue needs an explicit dependency statement, either a settled design decision with its rationale or a concrete open question with the actual fork in the road, and a note on what was deliberately deferred. Never leave implicit assumptions a bot might guess on.

Does this skill automatically start implementation after creating issues?▼

No. The skill explicitly does not apply any automation-triggering labels when creating issues. It surfaces that choice to the user, since launching multiple unattended implementation runs is not a safe default.

When should I use epic-planner versus epic-orchestrator?▼

Use epic-planner first to turn an idea into a roadmap and GitHub issues. Use epic-orchestrator second, once the epic exists, to drive the created issues through to completion.