ワンクリックで
planning-rollback-mechanism
Rollback mechanics and scenario: criteria, steps, data impact, recovery
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Rollback mechanics and scenario: criteria, steps, data impact, recovery
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Mandatory baseline rules for any agent. Must be loaded before any work
Frontend design system practices: tokens, typography, color, layout, and component consistency.
Frontend UI/UX practices: flows, interaction states, accessibility-first UX, forms, and perceived performance.
Clean code execution rules for coding agents with verifiable quality gates.
Debugging requirements protocol from reproducible issue to verified fix and regression protection.
Requirement quality rules for coding tasks with traceable MUST/SHOULD and verifiable acceptance criteria.
SOC 職業分類に基づく
| name | planning-rollback-mechanism |
| description | Rollback mechanics and scenario: criteria, steps, data impact, recovery |
<output_format>
<quality_rules> Rollback is feasible within a clear timeframe and described step-by-step Data impact is stated (what happens to partially applied changes) </quality_rules>
<do_not> Do not leave rollback as "we will roll back if needed" without mechanics Do not plan a rollback that requires manual data edits without verification </do_not>