diagrams-generator

Generate C4 diagrams from a Feature Design Document (FDD). Usage: /generate-c4 <path-to-fdd.md> [output-folder] [--no-images]

Generate Mermaid diagrams from a Feature Design Document (FDD). Usage: /generate-mermaid <path-to-fdd.md> [output-folder]

Use this agent when the user needs to generate C4 diagrams (System Context, Container, Component, and Code levels) in PlantUML format from a Feature Design Document (FDD) or similar technical documentation. The agent should be invoked in scenarios such as: <example> Context: User has completed writing an FDD and wants to visualize the architecture. user: "I just finished the payment-processing FDD. Can you generate the C4 diagrams for it?" assistant: "I'll use the c4-diagram-generator agent to analyze your FDD and create the complete set of C4 diagrams." <agent_invocation> Agent: c4-diagram-generator Task: Generate C4 diagrams from the payment-processing FDD located at docs/payment-processing-fdd.md </agent_invocation> </example> <example> Context: User mentions a feature documentation file and needs architectural visualization. user: "Look at the user-authentication feature doc in the docs folder and create the architecture diagrams" assistant: "I'll launch the c4-diagram-generator agent to process the authentication feature documentation and generate the C4 diagrams." <agent_invocation> Agent: c4-diagram-generator Task: Read docs/user-authentication feature doc and generate C4 diagrams </agent_invocation> </example> <example> Context: User has a folder with multiple FDDs and wants diagrams for a specific one. user: "Generate C4 diagrams for the notification-service FDD" assistant: "I'll use the c4-diagram-generator agent to locate and process the notification-service FDD." <agent_invocation> Agent: c4-diagram-generator Task: Find and process notification-service FDD to generate C4 diagrams </agent_invocation> </example> The agent should be used proactively when: - A user completes or updates an FDD - A user mentions needing architecture visualization - A user asks about documenting system design - A user references a feature design document without explicitly requesting diagrams

Use this agent when you need to generate technical diagrams for Feature Design Documents (FDDs) or similar technical specifications. Examples: <example> Context: User has written a Feature Design Document describing a new payment processing system and wants visual diagrams to enhance understanding. user: "I've finished writing the FDD for our new payment gateway integration. Can you help me create diagrams to illustrate the architecture?" assistant: "I'll use the mermaid-diagram-generator agent to analyze your FDD and create relevant Mermaid diagrams that enhance comprehension." <Task tool call to mermaid-diagram-generator agent with the FDD content> </example> <example> Context: User is working on a technical design document and mentions the need for visual representation. user: "This design doc explains our event-driven notification system with multiple fallback mechanisms. I think it needs some diagrams to make the flow clearer." assistant: "Let me launch the mermaid-diagram-generator agent to create focused, meaningful diagrams for your notification system design." <Task tool call to mermaid-diagram-generator agent> </example> <example> Context: User has completed a logical section of architecture documentation and the agent proactively suggests diagram generation. user: "Here's the complete architecture section describing how our microservices communicate through the message broker, including retry logic and circuit breakers." assistant: "Your architecture section would benefit from visual diagrams. I'm going to use the mermaid-diagram-generator agent to create clear Mermaid diagrams that illustrate the communication patterns and failure handling mechanisms." <Task tool call to mermaid-diagram-generator agent> </example>