Multi-file
analysisOfficial
Official Provider SkillView repo
Design and review guidance for software architecture diagrams (Mermaid, Draw.io). Use when creating, reviewing, or editing diagrams in any markdown documentation. Triggered by: diagram, flowchart, sequence diagram, mermaid, drawio, architecture diagram, data flow, state machine, ER diagram, class diagram, C4 model, system context, high-level overview. Covers readability, accessibility, notation, abstraction levels, tool selection (mermaid vs drawio), and platform-specific rendering rules (GitHub
Files2 files
SKILL.md88 lines
Loading editor…
Install
RecommendedOne command — your agent picks it up automatically.
Select an AI agent above to see the install command.
or
Manual Install
More stepsDownload the archive and add the files to your project manually.
Skill details
Versionv1.0.0
AuthorMicrosoft
Categoryanalysis
Skill IDmicrosoft/devsquad-copilot/.github/plugins/devsquad/skills/diagram-design
Files2 files
Related skills
Adr WorkflowComplete workflow for creating and managing ADRs (Architecture Decision Records). Includes duplicate checking, status determination, Microsoft documentation lookup, Azure cost estimates, and completeness validation. Use when you need to create or update ADRs during planning. Do not use for decisions that don't need an ADR (use conventions in plan.md).Board ConfigConfigure work item platform (GitHub Issues or Azure DevOps), detect process template, and save preference. Use when you need to identify where to create or read work items. Do not use for creating work items (use work-item-creation) or for managing implementation workflow (use work-item-workflow).Complexity AnalysisComplexity analysis for user stories with known work, risks, and scenarios. Use when you need to estimate effort, points, size, or analyze complexity of a user story. Do not use for sprint estimates (use devsquad.sprint) or for artifact quality validation (use quality-gate).Debugging RecoverySystematic debugging with structured triage. Use when tests fail, builds break, runtime behavior does not match expectations, or any unexpected error occurs during implementation. Do not use for planned refactoring (use code review), for test strategy (use `test-discipline` skill), or for security-specific issues (use security-review).Deep ClarificationAsk hard clarifying questions, stress-test assumptions, and challenge a plan or design until ambiguity is resolved. Exhaustively walks each branch of a decision tree. Use when deep clarification is needed during spec creation, planning, triage, or any phase with significant uncertainty. Also use when the user says 'challenge this', 'stress-test this', 'probe this plan', or 'deep dive on requirements'. Do not use for simple yes/no confirmations, for architecture decisions (use ADRs after clarificDocumentation StyleFormatting and style rules for markdown documentation. Use when generating or editing any project markdown document. Do not use for source code, code comments, or commit messages. For work item content (titles, descriptions, comments on GitHub Issues or Azure DevOps), use the Content Style section of the `work-item-creation` skill.