How We Organize Our Development Knowledge Base at OpsMill
Blog post from OpsMill
OpsMill is building a shared development knowledge base intended to give engineers, open-source contributors, and AI coding agents the same operational and architectural context needed to work effectively on its Infrahub codebase. Its repository-centered structure uses a single `.agents/` directory for reusable commands, rules, and skills, while documentation is divided between dynamic materials describing the current system, coding guidelines, and task guides, and static records such as architecture decision records and feature specifications. A concise AGENTS.md file serves as the initial navigation and rules document, directing users to more detailed resources without overloading every agent session. To keep information current, the team manually updates documentation after features ship, has Claude perform retrospectives on session difficulties, and uses a weekly harvesting agent to turn pull-request feedback into reusable rules. OpsMill is still refining automation for documentation updates, but reports that its guardrails have already prevented unapproved dependency changes while helping experienced engineers preserve institutional knowledge and new hires ramp up more quickly.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| AI Model Fine-tuning | 1 | 567 | 160 | 64 | -42% |
| LLM | 1 | 5,223 | 1,058 | 240 | -33% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.