Runbook Writer FAQs

Question 1

How does the 'Two-Stage Review' work?

Accepted Answer

First, a Spec Reviewer checks if the content aligns with upstream architectural requirements. Second, a Quality Reviewer verifies that all steps are clear, executable, and include validation commands.

Question 2

Does it support custom deployment environments?

Accepted Answer

Yes, by providing context on your infrastructure (K8s, VM, Serverless), the skill tailors the deployment steps, monitoring SLOs, and troubleshooting guides to your specific stack.

Question 3

Why does it use subagents instead of writing directly in the session?

Accepted Answer

Using subagents prevents 'context pollution' in your main Claude session and ensures that the writing and reviewing tasks are performed with fresh, unbiased focus on the technical requirements.

Question 4

What is the primary role of the Runbook Writer skill?

Accepted Answer

It acts as a coordinator rather than just a writer. It extracts technical requirements from your docs, manages subagents to write the content, and performs multi-stage reviews to ensure the output is production-ready.

Question 5

What documents should I provide to get the best results?

Accepted Answer

For best results, provide the PRD, HLD (High-Level Design), LLD (Low-Level Design), and any infrastructure or API contracts to ensure the runbook is accurate and evidence-driven.

Runbook Writer

주요 기능

사용 사례

Runbook Writer

주요 기능

사용 사례