Runbook Skill

Run runbook --version, runbook scan, runbook prefer, and at least one task-relevant runbook category ... --lang ... query before non-trivial repository work. runbook scan is only the fact inventory; it is not a complete tool-choice workflow by itself. Turn the scan, preferences, and category candidates into a task-local operating contract before mutating files or running build/test/lint/deploy/database commands.

When tool choice is not obvious, use runbook category to expose the relevant tool candidates instead of guessing from memory. When a repository has repeated or user-confirmed tool choices, read or update them through runbook prefer; never write preferences silently.

Completion Bar

For non-trivial repository work, Runbook preflight is complete only after all of these are true:

• the installed CLI version is known
• project and machine facts have been scanned
• repository preferences have been read
• task-relevant category candidates have been inspected
• the final tool choices are explained by local evidence, preferences, or category comparison

Do not say or imply that Runbook has been "run" or that the operating contract is complete after only runbook scan, unless the user explicitly asked for a scan-only inventory.

Workflow