arch-diagrams

Generate architecture diagrams from OpenAPI 3.x YAML files by placing them under inputs/APIs/ and running the skill to parse service names, endpoints, and schemas into Mermaid component and sequence diagrams embedded in the elicitation document.

Yes, create Mermaid sequence diagrams directly from an API specification by extracting operationIds or HTTP method and path definitions from OpenAPI files to produce one happy-path sequence diagram per service interaction flow.

Keep architecture documentation updated when API contracts change by running this skill within requirements engineering pipelines to automatically refresh Section 4 of the elicitation document with traceable Mermaid diagram sources and review placeholders.

Yes, an elicitation document is required as the target artifact for writing generated component diagrams, and it should be produced by the elicitation pipeline under artifacts/01-elicitation/ before running this skill.

Requirements traceability works by mapping extracted OpenAPI service names and endpoints into Mermaid flowchart LR and sequenceDiagram outputs, then embedding those diagram sources directly into the System Architecture Overview section of the elicitation document.

If OpenAPI specifications are missing operationIds for sequence diagram generation, the skill falls back to using the HTTP method and path definitions from the API contract to label the interaction flows in the Mermaid sequence diagrams.