runbook-writer

To generate a runbook from upstream PRD and HLD documents, provide the operational constraints to the coordinator. It extracts context, tasks writer subagents to draft the runbook, and runs spec and quality reviews to output executable documentation.

Automating operational documentation for incident response involves orchestrating writer and reviewer subagents to convert guardrails into standardized templates. This produces production-ready manuals covering monitoring, deployment, rollback, and on-call procedures.

Yes, you can use this runbook generation process for complex system rollbacks. It applies template-driven outputs specifically designed for rollback procedures, ensuring production-ready operational documentation through a two-phase review workflow.

Yes, you need to provide upstream guardrails, PRD, or HLD before creating an on-call runbook. The coordinator extracts operational constraints from these inputs to initiate writer subagents and ensure the final documentation is executable.

The two-phase review workflow ensures runbook quality by applying spec and quality review stages after writer subagents draft the content. This collaborative process verifies completeness, enforces standard templates, and validates evidence citations before final output.