migration-runbook-generator

What This Skill Does

The migration-runbook-generator is a specialized OpenClaw agent skill designed to transform raw migration plans into structured, professional, and reliable runbooks. Instead of merely listing steps, this skill proactively identifies critical gaps in your migration strategy, such as ambiguous cutover windows, missing validation signals, or neglected rollback procedures. It acts as an architectural safety net, ensuring that your technical migration documentation adheres to industry best practices for reliability and auditability. By leveraging local resources like spec.json and predefined templates, it forces consistency across your operational documentation while keeping the focus on risk mitigation and clear role assignment.

Installation

To integrate this skill into your environment, run the following command in your terminal or OpenClaw interface: clawhub install openclaw/skills/skills/52yuanchangxing/migration-runbook-generator Once installed, the skill will automatically index the local resources directory, enabling it to reference your team's standard migration templates and specifications during the drafting process.

Use Cases

• Drafting comprehensive cutover runbooks for database migrations or service deployments.
• Formalizing manual intervention steps into a structured checklist with clear go/no-go criteria.
• Standardizing rollback procedures to ensure recovery plans are documented and actionable before any change begins.
• Converting informal Slack or email migration plans into compliant technical documentation for incident review and auditing.

Example Prompts

1. "I need to migrate our legacy user authentication service to the new OAuth2 platform this weekend. Here are the rough steps: 1. Update DNS, 2. Toggle traffic, 3. Monitor errors. Please turn this into a formal runbook with a rollback strategy."
2. "Generate a migration runbook for our database schema update scheduled for the next maintenance window. Include a pre-check section, detailed validation signals, and assign tasks for the DBA and DevOps teams."
3. "Review this migration plan for our legacy storage backend. Identify potential risks, gaps in our validation phase, and suggest a fallback plan in case of latency spikes."

Tips & Limitations

• Safety First: This skill is strictly for documentation generation. It does not possess the authority to execute database changes or trigger production deployments. Always perform a manual review of the generated content against your environment's specific constraints.
• Handling Ambiguity: If your provided information is incomplete, the generator will output an 'Outstanding Items' list. Do not proceed until these dependencies are resolved.
• Workflow Design: Use this tool to generate 'Review Drafts' first. Only after team consensus should you finalize the 'Execution Checklist'. This ensures that the migration plan is vetted by stakeholders rather than blindly executed.