ogutdgn

Use at the start of every session (confirm the active chunk is still right) and at the end of every session (set the next chunk). Also use whenever the immediate next-chunk focus shifts mid-session in the vetkit project.

Use when a chunk completes, an open decision resolves, the phase backlog reorders, or scope shifts in or out of any phase. Keeps project-documentation/plan.md authoritative as the source of truth for what gets built, in what order, in the vetkit project.

Use when about to create a git commit in the vetkit project, before composing the commit message. Enforces Conventional Commits prefix, English, lowercase imperative, max 3-4 sentences total, and forbids any Claude/AI attribution footer.

Use before closing a chat session, before any major operation that could end the session (multi-file refactor, deploy, schema migration, large dependency install), or whenever the working tree state is about to change significantly in the vetkit project. Snapshots the state so the next session picks up cold.

Use before any git commit in saminn-background-check. Defines subject-line scope tags, body detail requirements, staging discipline, and PR-vs-direct-commit guidance.

Use when starting or ending a work session in saminn-background-check, after finishing a phase or a source/subsystem branch, or whenever the project's current phase, branch, or next step changes — so docs/plan/ never goes stale.

Use before any git commit. Defines Conventional-Commit subject lines with scope tags, body detail requirements, explicit staging discipline, the no-AI-authorship rule, and PR-vs-direct-commit guidance. Adapt the scope list to the current project.