Request
Add a new /runbook skill to the Han plugin that produces runbooks in a consistent format.
Issue type
Feature request.
Open questions to resolve before this is plannable
Triaged from the original request, the following are not yet defined and need reporter input:
- Use case / job to be done. Who runs
/runbook, in what situation, and what they do with the output (incident response, deployment, on-call handoff, recurring operational SOP, customer support escalation, etc.).
- Target audience for the runbook. On-call engineers, support, ops, developers new to the system, or mixed.
- The "consistent format" itself. What sections, in what order, at what level of detail. Adopting an existing format (Google SRE, PagerDuty, internal Test Double template) or designing one from scratch.
- Inputs the skill accepts. Free-form description, an incident postmortem, a feature spec, a system area / module, or something else.
- Output location and naming. Where runbooks live in the target project (e.g.
docs/runbooks/) and the file naming pattern.
- Success criteria. What makes a "good" runbook in this format and how we know the skill is done.
- Scope of coverage. Operational runbooks only, or also incident-response playbooks, deployment guides, recurring-task SOPs.
- Specialist dispatch. Whether the skill should pull in
on-call-engineer / devops-engineer agents to harden content, or stay deterministic and structural only.
- Relationship to existing skills. Why
project-documentation, coding-standard, and architectural-decision-record are insufficient and how /runbook differs.
Suspected areas of impact
- New
plugin/skills/runbook/ (SKILL.md + any references/).
- New
docs/skills/runbook.md.
- Index updates in
docs/skills/README.md and the skill catalog in CLAUDE.md.
- Possible overlap with
project-documentation, coding-standard, architectural-decision-record.
- Possible collaboration with
on-call-engineer and devops-engineer agents.
Severity / reproducibility
- Severity: Low (new capability, nothing broken).
- Reproducibility: N/A — feature request.
Recommended next step
Clarify the open questions above with the reporter, then run /plan-a-feature to specify the skill's behavior before implementation.
Request
Add a new
/runbookskill to the Han plugin that produces runbooks in a consistent format.Issue type
Feature request.
Open questions to resolve before this is plannable
Triaged from the original request, the following are not yet defined and need reporter input:
/runbook, in what situation, and what they do with the output (incident response, deployment, on-call handoff, recurring operational SOP, customer support escalation, etc.).docs/runbooks/) and the file naming pattern.on-call-engineer/devops-engineeragents to harden content, or stay deterministic and structural only.project-documentation,coding-standard, andarchitectural-decision-recordare insufficient and how/runbookdiffers.Suspected areas of impact
plugin/skills/runbook/(SKILL.md + anyreferences/).docs/skills/runbook.md.docs/skills/README.mdand the skill catalog inCLAUDE.md.project-documentation,coding-standard,architectural-decision-record.on-call-engineeranddevops-engineeragents.Severity / reproducibility
Recommended next step
Clarify the open questions above with the reporter, then run
/plan-a-featureto specify the skill's behavior before implementation.