runbook

To generate an incident response runbook, provide a topic and scope to trigger parallel investigation tracks across your codebase and infrastructure. This analyzes configurations and dependencies to output a structured, actionable procedure document.

Yes, you can create deployment and failover procedures that output directly to Obsidian. The tool writes dated Markdown files into your vault, storing them at Runbooks/YYYY-MM-DD-service-operation.md for consistent operational documentation.

An operational runbook is a structured document containing actionable procedures for maintenance, scaling, and troubleshooting. You need one when you want to standardize infrastructure operations and infer context from your codebase to resolve incidents consistently.

Yes, the runbook generator operates without external dependencies. It runs parallel investigation tracks for codebase exploration, infrastructure analysis, and external research to infer context and extract configurations entirely within its internal processing logic.

The best way to document troubleshooting procedures is to use document templates that ensure repeatable, high-quality output. By analyzing your repository and infrastructure, the tool produces precise, dated procedures tailored to your specific service architecture.

Automating runbook generation relies on analyzing codebases and infrastructure to infer context, meaning output quality depends on repository structure and configuration visibility. Generated markdown files are stored in a fixed Obsidian vault path without alternative export formats.