Skip to content
Skills Library
Programming · Planning

deviation-rules

/deviation-rules

Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures

Repository
ship ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures

Original author description

Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures

How it works

  1. Rule 1 — Fix and Continue
  2. Rule 2 — Fix with Limits
  3. Rule 3 — Stop and Report
Original SKILL.md headings · 52 lines, 337 words
SKILL.md preview
---
name: deviation-rules
description: Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures
effort: medium
user-invocable: false
---

# Deviation Rules

During build execution, follow these rules when the plan does not match reality.

---

## Rule 1 — Fix and Continue

**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:**
- Plan says `src/auth/login.ts` but the file is `src/auth/auth.ts` — fix it, move on.
- Plan calls `import bcrypt` but bcrypt isn't installed — install it, move on.

---

## Rule 2 — Fix with Limits

**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):**
1. **Read the error** — full output, stack trace, exit code. The error message often contains the answer.
2. **Trace the cause** — where does the bad value originate? Follow it backward, not forward.
3. **One fix at a time** — change one thing, re-verify. Never batch multiple fixes.

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.

---

## Rule 3 — Stop and Report

**Trigger:** An architectural conflict, persistent verification failure (3 attempts exhausted), or any issue that requires fundamentally rethinking the approach.

**Action:**
1. Stop execution immediately
2. Leave the feature status as `building` in CONTEXT.md
3. Output `## CHECKPOINT REACHED` with a clear explanation and recommendation

**Signals:**
- Plan assumes REST API but codebase uses GraphQL — replanning needed, not improvisation
- Each fix attempt reveals a new problem in a different place — architectural mismatch
- Fix requires "massive refactoring" to implement — wrong approach, not wrong code

Versions

The database has no other skills named deviation-rules.

Database snapshot: 13.11.2026 · package version a92ad7055d58 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100log-deviation
    Record a place where the code forced a deviation from the agreed plan. Use mid-implementation whenever reality contradicts the plan, or when the user says "log this deviation". The log feeds future planning and the merge quiz.
  • 90dev-implement
    Execute an approved plan task by task with a check after each file, log every deviation against the acceptance criteria, and apply stop rules for build and type errors. Use after the plan is approved, or when the user says "làm đi" on a planned change, or when a build/typecheck/lint keeps failing.
  • 92kmg-execute-plan
    Enforce zero-deviation plan execution when user invokes plan implementation
  • 90executing-plans
    Use when a plan is approved and you are about to change files. Executes one task at a time with verification between tasks, keeps the todo list honest, and stops rather than improvising when reality diverges from the plan.
  • 90agent-plan-execute-replan
    Separate planning from execution and replan when reality diverges, so a long task does not follow a plan that stopped being true. Use when work has many steps and early assumptions are likely to be wrong.
  • 100docs-as-code
    Treat documentation like code: in the repo, in pull requests, CI-checked, with preview builds. Use when docs drift from reality or the docs workflow is separate from the code workflow.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.