des-create-epic

To convert data engineering design artifacts into an implementation backlog, you can generate an Epic Catalog that maps upstream lifecycle artifacts into traceable, dependency-ordered work packages. This process groups design themes into phased delivery areas for structured implementation planning.

Planning CI/CD readiness involves extracting implementation themes from completed design artifacts and grouping them into phased delivery chunks. This approach defines epic dependencies, acceptance criteria, and priority levels to ensure infrastructure and pipeline work is sequenced correctly.

Grouping data pipeline requirements into traceable epics requires reading configured planning artifacts and extracting implementation themes. The resulting Epic Catalog maps each epic back to upstream sources like business requirements, data products, layers, and contracts for full traceability.

Yes, generating an epic backlog requires minimum DES planning artifacts for product, sources, architecture, ingestion, Gold transformations, quality, and CI/CD testing to be available. These completed design artifacts provide the necessary implementation themes for accurate epic extraction.

Yes, you can define phased delivery and dependencies before creating stories by grouping work into foundation, MVP, and later phases. The generated Epic Catalog specifies epic dependencies, priority levels, and acceptance criteria to guide subsequent detailed story creation.

A limitation of generating an epic catalog directly from design artifacts is that it stops at the epic level and does not produce detailed user stories. It requires validation of the generated backlog before handing off to a story-creation skill for further implementation breakdown.