skills/drift-entry/SKILL.md
DRIFT ENTRY SKILL — Log a counter-goal implementation to design/DRIFT.md. USE FOR: any role that identifies an implementation working against a stated goal; adding a new drift item or a new instance to an existing drift item. Enforces the no-duplicate rule and ensures every entry links to a goal. DO NOT USE FOR: resolving drift (create a backlog item instead).
npx skillsauth add zcross00/ProcessDocumentation drift-entryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill whenever you identify an implementation that works against one of the project's stated goals.
Drift is an implementation that actively works against a goal in design/GOALS.md. It is not:
The test: Does this thing make a stated goal harder to achieve? If yes, it is drift.
Open design/DRIFT.md. Scan the active items for one that describes the same drift pattern.
Never create a duplicate. Two entries about the same underlying problem must be merged into one.
Determine the next DR-N ID: find the highest existing ID and add 1.
Add a new entry in the Active section:
<!-- drift: DR-N -->
### DR-N — [Short title describing the drift]
**Against Goal:** G-N — [goal title]
**Severity:** [Low | Medium | High]
**First Observed:** [YYYY-MM-DD]
[One paragraph explaining what the implementation does and why it works against the goal.]
**Instances:**
1. [Specific location or behavior — file, class, method, or user-facing description]
**Resolution:** Pending — see BL-N (if a backlog item has been created) or "No backlog item yet."
Severity guide:
Find the matching DR-N entry. Add a numbered line to the Instances list:
N. [Specific location or behavior]
If the new instance changes the severity (e.g., the pattern is now more widespread), update the severity.
If the drift is Medium or High severity and no BL-N exists for it yet:
Rework.DR-N in the detail block.Pending — see BL-N.development
TEST WRITING SKILL — Write correctly structured JUnit 5 tests that match this project's conventions. USE FOR: adding tests for a new backlog item; flagging missing test coverage; writing tests for engine classes, domain logic, or persistence. Covers class placement, naming conventions, setup patterns, assertion style, and what not to test. DO NOT USE FOR: running tests (use build-verify skill); diagnosing test failures (read the Surefire report directly).
development
STANDARDS CHECK JAVA SKILL — Apply standards/general.md and standards/java.md systematically to a Java file or diff. USE FOR: pre-commit standards compliance check; reviewing a file for standards adherence before or after a change. Produces a categorized violation list with the specific rule cited for each. DO NOT USE FOR: general code review (use planner-review skill for implementation review).
testing
REFINEMENT SKILL — Analyze design, features, backlog, and drift to identify and plan needed work. USE FOR: PLANNER producing new backlog items from gaps between design and current state; evaluating tech debt and drift for resolution; structured backlog growth when the user asks the PLANNER to refine or plan more work. DO NOT USE FOR: implementing backlog items (EXECUTOR work); reviewing completed work (use planner-review skill).
development
PLANNER REVIEW SKILL — Review a completed backlog item and update design artifacts accordingly. USE FOR: PLANNER reviewing an EXECUTOR's completed work; updating FEATURES.md after a feature lands; removing completed items from BACKLOG.md; checking for drift. DO NOT USE FOR: implementing backlog items (EXECUTOR work); initial planning (read GOALS and DESIGN directly).