What problem does it solve? Teams lose architectural knowledge when documentation lives in wikis or slide decks that drift out of sync with the code. This Skill keeps README, CONTRIBUTING, C4 architecture diagrams, and Architecture Decision Records (ADRs) inside the repository, reviewed in pull requests and rendered in CI. ## Core Features & Use Cases - Living documentation structure: Defines the required content for README.md, CONTRIBUTING.md, docs/ARCHITECTURE.md, docs/SLO.md, and a docs index so newcomers can navigate a repo in under 60 seconds. - C4 diagrams as code: Produces context, container, and component diagrams in PlantUML or Structurizr DSL, rendered to SVG in CI with a pre-commit check that fails when diagrams are stale. - Architecture Decision Records: Provides an append-only ADR template under docs/adr/ capturing context, decision, consequences, and alternatives for every non-trivial design choice. - Use Case: When scaffolding a new Spring Boot service or choosing Kafka over RabbitMQ, apply this Skill to generate the full docs tree and record the decision as an immutable ADR in the same PR. ## Quick Start Apply the documentation-and-adr skill to generate the README, ARCHITECTURE.md with C4 PlantUML diagrams, and an ADR for the technology choice we just made in this repository.
