log-deviation
/log-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.
- Author
- hiendinhngoc ↗
- Repository
- unknowns ↗
- Licence
- MIT
- Last repository change
- 14.07.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Triggers from the description
Original author description
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.
How it works
- Where the log lives
- Entry format (append, newest last)
- Discovered drift
- Rules
SKILL.md preview
--- name: log-deviation description: 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. version: 1.0.0 author: Hien Dinh license: MIT --- # Deviation Log The plan said one thing; the code demanded another. Record it while it's fresh — these entries are the highest-value input to the next plan. ## Where the log lives - In a git repo: `docs/deviations/YYYY-MM-DD-<task-slug>.md` at the repo root (create `docs/deviations/` if needed). `<task-slug>` = short kebab-case name of the current task. Slugs are minted freely, so two sessions will name the same task differently: before creating a new file, list what already exists in `docs/deviations/` and reuse the slug of any file that is plausibly this task — appending to it even if it's from an earlier day/session — rather than minting a near-duplicate. - Outside a git repo: write to the session scratchpad instead and tell the user the path. ## Entry format (append, newest last) ```markdown ## <YYYY-MM-DD HH:MM> — <one-line summary> - **Plan said:** <what the plan/spec assumed> - **Code forced:** <what was actually done instead> - **Why:** <the real-world constraint that made the plan wrong> - **Ripple:** <other plan steps this invalidates, or "none"> ``` The heading carries the full date: the file spans days by design, and `HH:MM` alone goes ambiguous on the second session. ## Discovered drift Not every deviation is caught live. When work reveals that plans or docs already disagree with the shipped code (a stale roadmap item, a doc promising a design the code abandoned), log it with the same fields plus one more: ```markdown - **Found while:** <the current activity that surfaced it> ``` Date the heading with the *discovery* time; if the deviation's original date is known, name it in **Code forced**. ## Rules - One entry per deviation, logged at the moment it happens — not batched at the end. - "Why" names the constraint (API limitation, hidden coupling, wrong assumption), never just "it didn't work". - If invoked with no deviation to log, ask what deviated rather than inventing one. - Do not commit the log automatically; leave staging to the user's normal flow.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named log-deviation.
Database snapshot: 13.11.2026 · package version 59a762567d53 (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
- 90implementation-notes
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions. - 100deviation-rules
Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures - 92kmg-execute-plan
Enforce zero-deviation plan execution when user invokes plan implementation - 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. - 90change-quiz
After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge. - 90checkpoint-log
Keep a live, committed checkpoint log during any work unit expected to span multiple commits or sessions. Each commit ships with a short note in the log, what the commit did, the key decision and why, any deviation from plan; closing the unit requires an explicit walk of the…