doc-at-run

To standardize incident response documentation in Obsidian, this Skill enforces diopside operational standards by generating AT-RUN runbooks with mandatory frontmatter, incident classification, initial response, recovery procedures, and judgment criteria sections.

An incident response runbook must include mandatory frontmatter, structured incident classification, initial response steps, recovery procedures, and judgment criteria, while facilitating links to related incident and dependency documents.

To create an incident response procedure document for a system outage, use this Skill to draft a compliant AT-RUN file, ensuring all stakeholders can quickly understand the issue and the structured steps required to resolve it.

Yes, you can revise existing AT-RUN runbooks by using this Skill to verify that all necessary sections, including recovery procedures and judgment criteria, are included and properly linked to dependency documents.

No specific dependencies are required to manage procedural documentation with this Skill, as it operates independently using scripts and references to enforce Obsidian operational standards for AT-RUN documents.

You need to generate an AT-RUN document when a new critical system failure occurs, ensuring the official incident response procedures adhere to diopside naming conventions and frontmatter requirements for clarity and consistency.