Comment by mushgev

SpecMind works by combining static code analysis with AI generated specs. It uses Tree-sitter to parse the entire codebase and build a structured model of services, layers, entities, and dependencies.

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.