generate-intent-epics

To generate structured product epics from capability data, use a schema-driven transformation process that reads enriched capabilities and project profiles to populate goals, constraints, and failure scenarios in human-readable YAML files.

An intent epic is a deterministic, reviewer-friendly YAML file that uses the four-section ICE schema to structure goals, constraints, and failure scenarios, preparing enriched capabilities for downstream expectation drafting and validation.

Ensure generated epics include only vertical capabilities by applying component-to-parent merging before schema-driven generation, which absorbs component capabilities into parent verticals and prevents them from becoming standalone epics.

Yes, schema-driven generation can track decisions by emitting a decision-manifest.yaml file alongside intent epics, recording key inferred decisions with tiering and grounding to provide full traceability for product teams during review.

Yes, you need a project profile and market brief alongside enriched capability data to populate the mandatory ICE schema fields with plain language goals, constraints, and failure scenarios for human-readable intent epics.

The limitation of deterministic workflows for epic generation is that outputs rely entirely on the quality of enriched capability data and project profiles, as the schema-driven process strictly populates mandatory fields and avoids banned legacy key shapes.