Adding existing toolbox pages to extended diagram

[WarrenKenyon]

I am creating a simple MDG to do some requirements modeling.  I wanted to extend "Requirement" to create a stereotype unique to our current problem, specifically to add a set of tagged values.  I really just want to add my new requirement type to the existing "Requirements" toolbox and diagram type. I believe that is not really possible, so I went ahead and created a tool box and diagram type for my MDG.  That all works fine.  But, I really want the "Extended Requirements", "Requirements Relationships" and "Patterns" pages you get when you create a UML::Requirements diagram. 

Is there any way to simply add those pages to my new diagram type/toolbox?  The Extended Requirements page contains a bunch of stereotyped Requirements, but they are not "UML::xxx". I have not been successful in creating a toolboxpage in my profile that adds those Built-in Types, because they are not Built-in Types.  I believe they are part of "Core Extensions" but I don't know how to address that MDG in my profile (since it is internal and not an XML file)

[WarrenKenyon]

I did extend UML::Feature. What I want is the rest of the requirements tools available in the same tool box.

[WarrenKenyon]

You can type in the meta types manually if they are not present.

q.

Except I cannot, because the other requirements types seem to be extensions themselves, and are not UML::xxxx.  I know how to add UML default meta types to a tool box.  These seem to be in another namespace that is known only internally.

[KP]

The Extended Requirements page contains a bunch of stereotyped Requirements, but they are not "UML::xxx".

EAREQ::FunctionalRequirement(UML::Requirement)

The rest follow the same pattern. If you get stuck, create one in an empty model and then look in t_xref for a definition like this

@STEREO;Name=FunctionalRequirement;FQName=EAREQ::FunctionalRequirement;@ENDSTEREO;

[WarrenKenyon]

The Extended Requirements page contains a bunch of stereotyped Requirements, but they are not "UML::xxx".

EAREQ::FunctionalRequirement(UML::Requirement)

The rest follow the same pattern. If you get stuck, create one in an empty model and then look in t_xref for a definition like this

@STEREO;Name=FunctionalRequirement;FQName=EAREQ::FunctionalRequirement;@ENDSTEREO;

Thank you.  A real answer from someone who seems to have actually read the question.