Coordinate NAF v4 / ADMBw modeling across all viewpoint categories. Routes requests to specialized skills (Requirements, Architecture Metadata, Concepts, Logical Specification, Physical Resources, Service Specification) and handles cross-viewpoint relationships. Use when the user wants to work with multiple viewpoint categories, create relationships between different viewpoint types (e.g., Requirement → Capability, Capability → Service), or needs guidance on which viewpoint to use.
This coordinator skill manages NAF v4 / ADMBw architecture modeling across all viewpoint categories. It dispatches requests to specialized skills and handles cross-viewpoint relationships.
These rules apply to all NAF v4 modeling tasks:
When the modeling target is unclear, always ask the user where to model:
Default behavior: If not explicitly specified, use the currently open diagram as the modeling target.
Before using element names in any operation, especially when creating connections:
find_elements_by_name to search for elementsThis prevents:
Never apply automatic diagram layout operations:
layout_diagram or similar automatic layout functionsplace_element_on_diagram, but their visual arrangement is left to the user| Skill | Viewpoints | Description |
|---|---|---|
| nafv4-requirements | R2-R6 | Requirements Catalog, Dependencies, Conformance, Derivation, Realization |
| nafv4-architecture-metadata | A1-A8, Ar | Meta-Data, Products, Correspondence, Methodology, Status, Version, Compliance, Standards, Roadmap |
| nafv4-concepts | C1-C8, Cr | Capability Taxonomy, Enterprise Vision, Dependencies, Processes, Effects, Parameters, Assumptions, Roadmap |
| nafv4-logical-specification | L1-L8, Lr | Node Types, Scenario, Interactions, Activities, States, Sequence, Information Model, Constraints, Lines of Development |
| nafv4-physical-resources | P1-P8, Pr | Resource Types, Structure, Connectivity, Functions, States, Sequence, Data Model, Constraints, Configuration Management |
| nafv4-service-specification | S1-S8, Sr | Service Taxonomy, Structure, Interfaces, Functions, States, Interactions, Parameters, Policy, Roadmap |
Analyze the user's request to determine:
For single-viewpoint tasks:
For cross-viewpoint tasks:
Use MCP tools to create connectors between elements from different viewpoint categories.
Common cross-viewpoint relationships:
"I need to..."
| User Need | Recommended Viewpoint | Skill |
|---|---|---|
| "Document requirements" | R2 - Requirement Catalogue | nafv4-requirements |
| "Define capabilities" | C1 - Capability Taxonomy | nafv4-concepts |
| "Show enterprise vision and goals" | C2 - Enterprise Vision | nafv4-concepts |
| "Model logical architecture" | L1-L2 - Node Types, Scenario | nafv4-logical-specification |
| "Define operational activities" | L4 - Logical Activities | nafv4-logical-specification |
| "Catalog physical resources" | P1 - Resource Types | nafv4-physical-resources |
| "Show system structure" | P2 - Resource Structure | nafv4-physical-resources |
| "Define services" | S1-S2 - Service Taxonomy, Structure | nafv4-service-specification |
| "Document architecture metadata" | A1-A2 - Meta-Data, Products | nafv4-architecture-metadata |
Strategic/Conceptual Layer:
nafv4-concepts or nafv4-requirementsLogical Layer:
nafv4-logical-specification or nafv4-service-specificationPhysical/Implementation Layer:
nafv4-physical-resourcesMeta/Governance Layer:
nafv4-architecture-metadataUser: "Link requirement 'FR-001' to capability 'Surveillance'"
Coordinator Actions:
1. Verify FR-001 exists (using nafv4-requirements skill knowledge)
2. Verify Surveillance capability exists (using nafv4-concepts skill knowledge)
3. Determine appropriate relationship stereotype (likely DerivedFrom or MapsToCapability)
4. Create connector using MCP create_or_update_connector:
{
"sourceElementName": "FR-001",
"targetElementName": "Surveillance",
"connectorType": "Dependency",
"stereotype": "MapsToCapability",
"profile": "NAFv4-ADMBw"
}
5. Confirm to user
User: "Show that 'C2 Capability' is provided by 'Command Service'"
Coordinator Actions:
1. Verify capability exists (C1 viewpoint)
2. Verify service exists (S1/S2 viewpoint)
3. Create relationship:
- If service provides capability: Use Provides or ServiceProvision
- If capability needs service: Use Consumes
4. Execute MCP call with correct stereotype
User: "OperationalPerformer 'ISR Node' is implemented by System 'RadarSystem'"
Coordinator Actions:
1. Verify OperationalPerformer exists (L1/L2)
2. Verify System exists (P1/P2)
3. Create Implements relationship (type: Abstraction)
4. Execute MCP call
User: "Service 'AuthService' supports activity 'AuthenticateUser'"
Coordinator Actions:
1. Verify Service exists (S2/S4)
2. Verify OperationalActivity exists (L4)
3. Create ActivitySupportsService relationship (type: Realization)
4. Execute MCP call
Example:
User: "Create a capability diagram"
Coordinator: "I can help you create capability-related diagrams. Which would you like?
1. **C1 - Capability Taxonomy** - Organize capabilities in hierarchies with MoEs
2. **C2 - Enterprise Vision** - Show capabilities in enterprise context with goals
3. **C3 - Capability Dependencies** - Analyze dependencies between capabilities
4. **Cr - Capability Roadmap** - Track capability delivery over time
Which best fits your needs?"
Example:
User: "Add a constraint"
Coordinator: "I can create several types of constraints. What level?
1. **StrategicConstraint** (Concepts C1) - Capability-level rules
2. **OperationalConstraint** (Logical L8) - Logical architecture rules
3. **ResourceConstraint** (Physical P8) - Implementation rules
4. **ServicePolicy** (Services S8) - Service-level policies
5. **Requirements** (R2-R6) - Requirement-level constraints
Which type do you need?"
Before creating cross-viewpoint relationships:
Example:
User: "Link FunctionalRequirement to System"
Coordinator checks:
- FunctionalRequirement (R2, type: Requirement)
- System (P1, type: Class)
- Valid relationships between these types
If valid: Create connector
If invalid: "FunctionalRequirement and System cannot be directly linked.
Consider:
- Link Requirement to Capability (MapsToCapability)
- Then Capability to System (Exhibits)"
Delegation pattern:
Coordinator: "I'm activating the nafv4-logical-specification skill to handle
your request for operational activities..."
[Hand off to specialized skill - no further coordinator involvement unless
cross-viewpoint work is needed]
Requirements to Implementation:
Service-Oriented Development:
System Architecture:
For detailed information about each viewpoint category, consult the specialized skills:
All NAF v4 / ADMBw elements and relationships use profile: NAFv4-ADMbw
Diagram types: