What problem does it solve? Software teams lose architectural context when decisions and module designs live only in chat or memory. This Skill standardizes how technical documentation is written so decisions, module contracts, and project knowledge stay versioned alongside the code. ## Core Features & Use Cases - ADR Templates: Produce Architecture Decision Records with status, context, consequences, and alternatives, stored under docs/decisions/ with date-based naming. - Module Specs: Document module responsibility, public interface, dependencies, and data flow in docs/modules/. - Smart Memory in Obsidian Format: Create frontmatter-tagged notes with wiki-style links for persistent project knowledge. - Mermaid Diagrams: Generate flowchart, sequence, ER, and state diagrams that version together with the repository. - Use Case: After choosing a new authentication approach, an Architect agent writes an ADR with a Mermaid sequence diagram, links it from the affected module spec, and records the decision in smart memory for future sessions. ## Quick Start Ask the agent to write an ADR documenting a recent architectural decision, including a Mermaid diagram and links to the affected module specs.
