skills.rest
edercnj
edercnjCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

x-internal-build-epic-plan

Build and validate epic execution DAGs using Kahn's algorithm.

Updated Aug 27, 2026
Search Tags:#automation#planning#epic#dag#execution-plan#kahns-algorithm
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-internal-build-epic-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: x-internal-build-epic-plan
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-internal-build-epic-plan
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-internal-build-epic-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This internal skill carves out the Phase 0 / 0.5 pre-flight of epic planning by loading epic metadata, parsing the story table, and anchoring the plan with a stable dependency DAG that downstream orchestrators can consume.

Core Features & Use Cases

  • Load and parse epic metadata and the IMPLEMENTATION-MAP to construct a dependency DAG.
  • Validate declared stories against on-disk artifacts and run a Kahn-based topological ordering to derive phase boundaries.
  • Render a machine-readable envelope and a human-readable execution plan for orchestration and auditing.

Quick Start

Invoke with --epic-id and --mode to generate the epic execution plan and envelope.

Frequently Asked Questions about x-internal-build-epic-plan

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

FAQPage Schema
How do I generate an execution plan from a dependency DAG for epic planning?▼

Cycle detection in a dependency DAG is performed using Kahn's algorithm during topological sorting. If the algorithm cannot process all nodes because remaining nodes still have incoming edges, a cycle exists in the dependency graph and the execution plan will flag the error.

How do I validate declared stories against on-disk artifacts during epic planning?▼

Declared stories are validated against on-disk artifacts by loading the story table from epic metadata files and cross-referencing them with physical files. The execution plan builder checks these artifacts during DAG construction to ensure declared dependencies match actual files.

What is the best way to compute parallel execution phases from an epic implementation map?▼

Epic planning requires epic metadata files at ai/epics/epic-${epic_id}/epic-${epic_id}.md and an implementation map at ai/epics/epic-${epic_id}/IMPLEMENTATION-MAP.md containing dependency edges. These files are parsed to construct the DAG and validate the story table.

Why does topological ordering fail when building an execution plan from dependencies?▼

Topological ordering fails when the dependency DAG contains cycles, detected by Kahn's algorithm as incomplete node processing. Circular dependencies in the implementation map prevent valid phase boundary derivation and halt execution plan generation.

Related Skills

Explore More Software Engineering Skills→
k3sdtwk3sdtw

jira

Create Task, Bug, and Story issues in Jira from templates.

Community
Basic
akaszubskiakaszubski
32

state-management-patterns

Apply standardized state-management patterns for JSON persistence with atomic writes and file locking.

Community
Advanced
5hdaniel5hdaniel

agentic-pm

Generate sprint plans, task files, and dependency graphs from backlogs.

Community
Advanced
curiositechcuriositech
10

dag-dependency-resolver

Validate directed acyclic graphs and produce topological orders with cycle reports.

Official
Advanced