With AI assistants writing more of our code, projects move faster but architectural consistency is often lost. Each developer or AI can introduce new patterns, and after a few sprints, the structure becomes fragmented. SpecMind helps prevent that by generating and maintaining living architecture specs directly from your code.
It works in three steps: 1. analyze – scans your codebase and generates .specmind/system.sm with architecture diagrams and relationships, 2. design – creates a spec describing how the feature will change the system, 3. implement – applies the spec, updates diagrams, and logs what changed
All specs are plain text files with Markdown and Mermaid diagrams, stored alongside your code. A VS Code extension lets you preview them visually.
Supports TypeScript, JavaScript, Python, and C#, with Go and Rust coming next. Works with Claude Code and Windsurf today, Cursor and Copilot soon.
Demo: https://www.youtube.com/watch?v=4-9gQxw8DQU
Repo: https://github.com/specmind/specmind
Would love to get feedback from engineers working on large or complex codebases.
mushgev•2mo ago
When you run analyze, it creates .specmind/system.sm which includes multiple diagram types such as system view, per service architecture, sequence flows, and entity relationships.
design <feature> creates a spec showing proposed changes, and implement <feature> updates the architecture once the feature is built, keeping the spec and code aligned.
All files are text based and versioned in the repo. The goal is to make architecture a living part of the codebase rather than something updated later in Confluence or diagrams.
Next steps include code-to-spec validation, PR diff integration, and more language support.
Happy to answer any technical questions or hear how others deal with architecture drift in fast moving projects.