It seems to be preferable that 'architecture-spec-template' includes 'Model Hierarchy' section which is currently included by 'implementation-plan-template'.

[mkanemat]

Use Case

This topic is related to 'specifying-mbd-algorithms'.

In my understanding, this skill would create at least four design documents.

• 'xxx-architecture.md'
• 'xxx-implementation-plan.md'
• 'xxx-system.md'
• 'xxx-test-plan.md'

I found that the following Component Catalog list is written in 'xxx-architecture.md' from my sample doc.

At first, I felt it difficult to understand model hierarchy...
After that, I found the following section in 'xxx-implementation-plan.md'.

This is trully helpful to understand what model architecture is currently considered well.

Relevant Skill or MCP Tool

model-based-design-core:specifying-mbd-algorithms

Proposed Behavior

My suggestion is:
It seems to be preferable that 'architecture-spec-template' includes 'Model Hierarchy' section which is currently included by 'implementation-plan-template'.

Best Regards,
Masato

Current Workaround

No response

Additional Context

No response