documentation-system-design

Activate when creating system design documents, writing runbooks, producing architecture diagrams, documenting API usage guides, writing onboarding documentation for a new engineer, reviewing documentation quality for a milestone or production release, creating incident response runbooks, producing system context diagrams, or evaluating whether documentation meets the standard required for a production deployment. Use when a system lacks sufficient documentation for the team to operate it safely, or when docs need to be assessed before a release gate.