runbook

Purpose

Write an operating runbook from the delivered system and verified procedures. Use when the customer team or a successor needs to operate without the original engineer.

Before investigating or acting:

1. Read the task context contract.
2. Read the method.

Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.

Principles

• Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
• If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
• The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
• Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.