Menu
Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when a feature plan has been verified and is ready for implementation — executes tasks with atomic commits
Use when you want to auto-run all remaining Ship steps for a feature without manual step-by-step invocation
Use when a feature has been brainstormed and needs a detailed implementation plan with tasks
Use when a brainstormed feature needs architectural decisions — presents 2-3 approaches for user to choose before planning
Use when a plan has been created and needs independent verification against codebase patterns before building
Use when beginning new feature work, adding functionality, or fixing a bug — runs intensive brainstorming to capture requirements before planning
| name | ship:deviation-rules |
| description | Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures |
| effort | medium |
| user-invocable | false |
During build execution, follow these rules when the plan does not match reality.
Trigger: A file path, function name, minor implementation detail, or missing dependency in the plan is wrong or outdated.
Action: Make the correct change (fix the path, install the dependency, adjust the detail). Continue executing the next task.
Examples:
src/auth/login.ts but the file is src/auth/auth.ts — fix it, move on.import bcrypt but bcrypt isn't installed — install it, move on.Trigger: The <verify> command for a task fails after implementation.
Action: Debug systematically, then fix and re-verify. Maximum 3 attempts. Track each attempt.
Debugging protocol (before each fix attempt):
If verify still fails after the third attempt, escalate to Rule 3.
If each fix reveals a new problem in a different place: This is not a single bug — it's an architectural mismatch. Skip directly to Rule 3.
Do not: Skip the verify step. Do not proceed to the next task with a broken current task. Do not guess — read the error first.
Trigger: An architectural conflict, persistent verification failure (3 attempts exhausted), or any issue that requires fundamentally rethinking the approach.
Action:
building in CONTEXT.md## CHECKPOINT REACHED with a clear explanation and recommendationSignals: