What problem does it solve? Engineering teams often treat documentation as an afterthought, leaving architecture decisions, incident learnings, and deployment procedures undocumented or scattered. This Skill establishes a docs-as-code workflow where ADRs, design docs, postmortems, and runbooks live in the repo, version with code, and serve both humans and AI agents. ## Core Features & Use Cases - Nine Document Types: Templates and conventions for AGENTS.md, ADRs, design docs, architecture minimaps, feature timelines, incident postmortems, deploy runbooks, API contracts, and contribution guides. - Generation Scripts: Bun-based scripts (adr:new, design:new, incident:new, openapi:gen) that scaffold documents from templates with automatic dating and numbering. - Docs CI Pipeline: Markdown linting, link checking, and automated OpenAPI/AsyncAPI generation via GitHub Actions. - Use Case: After a production WebSocket outage, run the incident script to scaffold a postmortem in docs/incidents/, fill in the timeline and root cause, and check off prevention items in the same PR as the fix. ## Quick Start Ask the agent to scaffold the docs structure and create a new ADR for your latest architecture decision using the nerdev-docs templates.
