HE Runbook

Create or update a runbook (process/checklist) that can evolve per project, while keeping skill-enforced gates immutable.

When to Use

• When a learning or review finding should become a repeatable process
• When a new workflow needs documentation for skill integration
• When an existing runbook needs updating after he-learn

Key Principles

1. Runbooks are additive only — they may add repo-specific steps, but they must not waive or override anything codified in skills.
2. Frontmatter is the integration contract — title, use_when, called_from must be accurate.
3. One runbook, one job — keep scope tight and name it for the workflow it documents.
4. Avoid duplication — before creating or editing, scan existing runbooks for overlap and conflicts.
5. Prefer verifiable steps — commands, file paths, expected outputs; avoid vague guidance.
6. Make it discoverable — link high-leverage runbooks from AGENTS.md (runbook index).