diagram

What problem does it solve?

This Skill bridges the gap between technical implementation and user value by creating and maintaining "Unified Impact Diagrams." It ensures that all technical decisions are explicitly linked to user benefits, making complex systems understandable for all stakeholders and preventing outdated documentation.

Core Features & Use Cases

• Diagram Driven Development (DDD): Follows a methodology to create diagrams that always show Front-Stage (user experience) and Back-Stage (technical implementation) with clear impact annotations.
• Create & Update Diagrams: Generate new diagrams for features, architectures, user journeys, and refactorings, and keep existing ones synchronized with code changes.
• Audit & Organize: Regularly check diagram quality, coverage, and organization to maintain a single source of truth for system understanding.
• Use Case: "Create a new feature diagram for the user authentication flow, ensuring it highlights security impacts and error recovery paths, following DDD principles."

Quick Start

Create a new sequence diagram for the user onboarding journey, showing both the user's steps and the backend services involved, with impact annotations.