Case 9/100 · Engineering
Database migration scripts and rollback plan
Use a Skill to define when this applies, which tools to call, and what structured output to return—this page summarizes exit criteria.
This case is grouped under Engineering. Mount it as a Skill in OpenClaw or a similar agent: use SKILL.md to declare triggers, tool boundaries, and output formats for repeatable automation playbooks.
Follow progressive disclosure (metadata → instructions → scripts): load full instructions only when the case matches, to save tokens; for external systems, spell out MCP/API permissions and sandbox-only actions.
- Typical triggers: explicit user requests, tags/keywords, or upstream automation (e.g. PR opened, ticket created).
- Expected output: structured results (lists, tables, or template fields), actionable next steps, and high-risk items that need human review.
- Collaboration: align with team standards (code style, playbooks, metric definitions) so agent output matches real workflows.
- Numbering: case 9/100 is a curated common pattern for search and training—not a vendor ranking.
# Case sketch (paste into SKILL)
- Trigger: tasks or events related to “Database migration scripts and rollback plan”
- Output: structured result + risks/assumptions
- Done: user confirms or hands off to human/next automation
- Category: Engineering