Drawio Flowchart
Generate or edit draw.io-compatible flowcharts and process diagrams for specs, runbooks, and architecture docs inside the agent workflow.
Overview
Drawio-flowchart is an agent skill most often used in Build (also Validate, Ship) that helps solo builders produce draw.io-style flowcharts for documentation and planning.
Install
npx skills add https://github.com/teachingai/full-stack-skills --skill drawio-flowchartWhat is this skill?
- draw.io / diagrams.net oriented flowchart output for agent-editable documentation
- Supports process, decision, and system-flow diagrams for specs and README-adjacent visuals
- Fits full-stack-skills bundles where diagram skills complement implementation plans
- Apache 2.0 licensed skill package suitable for redistribution in teaching and template repos
- Pairs with narrative docs so solo builders avoid blank-canvas diagram work during build and ship
Adoption & trust: 680 installs on skills.sh; 475 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have steps and dependencies in prose but no consistent visual flow teammates or future-you can scan in minutes.
Who is it for?
Indie developers documenting user flows, CI/CD paths, or service interactions who already use diagrams.net or draw.io exports in the repo.
Skip if: High-fidelity UI design, automated cloud topology discovery without human intent, or teams standardized on Mermaid-only diagrams with no draw.io pipeline.
When should I use this skill?
You need draw.io-style flowcharts for specs, onboarding docs, or process documentation while building or shipping a product.
What do I get? / Deliverables
You get draw.io-compatible flowchart files or XML the agent can iterate and drop next to specs, ADRs, or ship checklists.
- Draw.io-compatible flowchart source or export
- Updated diagram iterations aligned to spec changes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build docs because flowcharts most often ship as living documentation alongside code, even when drafted earlier in planning. Docs subphase covers visual artifacts—sequence, deployment, and decision flows—that explain how the product works to future-you and collaborators.
Where it fits
Sketch a decision flow for MVP feature cuts before committing to the backlog.
Add a service interaction flowchart next to the API readme for your backend module.
Publish a release checklist flow for deploy and rollback steps before going live.
How it compares
Skill-backed diagram drafting—not an MCP server and not a live whiteboard; use when you want editable .drawio artifacts beside markdown specs.
Common Questions / FAQ
Who is drawio-flowchart for?
It is for solo and indie builders who document systems with draw.io flowcharts and want the coding agent to draft or update those diagrams during build and docs work.
When should I use drawio-flowchart?
Use it in Build docs for architecture and runbooks; in Validate when scoping prototypes as flow sketches; in Ship launch prep when you need deployment or release process diagrams for stakeholders.
Is drawio-flowchart safe to install?
It is a documentation-oriented skill package under Apache 2.0 in the published readme; review the Security Audits panel on this page before installing from third-party skill bundles.
SKILL.md
READMESKILL.md - Drawio Flowchart
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this