Implement an approach to define and manage Requirements record Acceptance Criteria for IBM DevOps Plan

An Agile requirement comprises (or SHOULD comprise!) a high-level statement of what the system needs to do, plus one or more related, detailed scenarios that define system Acceptance Criteria for the high-level statement.  The AC's provide the requirements details.  Most Agile requirement tools, including the default implementation for DevOps Plan, manage only the high-level statement "well".  I've previously defined an approach using IBM ELM for managing both aspects of Agile requirements.  This is described in the accompanying file.  Motivating narrative can be found in my Blog entry: https://elmwatsoniot.wordpress.com/2019/07/03/how-to-effectively-author-manage-and-reuse-work-item-acceptance-criteria-using-elm/. A similar capability can be implemented for DevOps Plan using a Package that provides a new record type for Acceptance Criteria and a custom link type to associate Epic, Feature, or Requirements records with Acceptance Criteria.