<!-- SYNC:critical-thinking-mindset -->

Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.

<!-- /SYNC:critical-thinking-mindset --> <!-- SYNC:ai-mistake-prevention -->

AI Mistake Prevention — Failure modes to avoid on every task:

• Check downstream references before deleting. Deleting components causes documentation and code staleness cascades. Map all referencing files before removal.
• Verify AI-generated content against actual code. AI hallucinates APIs, class names, and method signatures. Always grep to confirm existence before documenting or referencing.
• Trace full dependency chain after edits. Changing a definition misses downstream variables and consumers derived from it. Always trace the full chain.
• Trace ALL code paths when verifying correctness. Confirming code exists is not confirming it executes. Always trace early exits, error branches, and conditional skips — not just happy path.
• When debugging, ask "whose responsibility?" before fixing. Trace whether bug is in caller (wrong data) or callee (wrong handling). Fix at responsible layer — never patch symptom site.
• Assume existing values are intentional — ask WHY before changing. Before changing any constant, limit, flag, or pattern: read comments, check git blame, examine surrounding code.
• Verify ALL affected outputs, not just the first. Changes touching multiple stacks require verifying EVERY output. One green check is not all green checks.
• Holistic-first debugging — resist nearest-attention trap. When investigating any failure, list EVERY precondition first (config, env vars, DB names, endpoints, DI registrations, data preconditions), then verify each against evidence before forming any code-layer hypothesis.
• Surgical changes — apply the diff test. Bug fix: every changed line must trace directly to the bug. Don't restyle or improve adjacent code. Enhancement task: implement improvements AND announce them explicitly.
• Surface ambiguity before coding — don't pick silently. If request has multiple interpretations, present each with effort estimate and ask. Never assume all-records, file-based, or more complex path.

<!-- /SYNC:ai-mistake-prevention -->

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Workflow End

Finalize and close the active workflow, clearing state so the next user prompt triggers fresh workflow detection.

---

When This Runs

This skill is the last step of every workflow sequence. It runs automatically after the final functional step (e.g.,

/watzup

,

/status

,

/acceptance

).

NOT for: Manual invocation mid-workflow (use workflow switching via

/workflow-start

instead).

---

What To Do

1. Integration test coverage check (skip if workflow is docs/design/investigation/e2e-only, or project has no test suite):

   git diff --name-only HEAD && git ls-files --others --exclude-standard
   

   (The second command lists untracked files not yet staged — catches brand-new handler files before first git add)

   • Scan changed files for those likely requiring integration test coverage: business logic files such as handlers, commands, queries, services, controllers, resolvers, event processors. Naming varies by stack — infer from the project's existing file patterns (e.g.,

     *Service.*

     ,

     *Handler.*

     ,

     *Controller.*

     ,

     *Command.*

     ,

     *Query.*

     ).
   • For each identified file → search for a corresponding test file. Infer the project's test naming convention from existing tests (e.g.,

     *.test.ts

     ,

     *Tests.java

     ,

     *_test.py

     ,

     *.spec.js

     ,

     *Tests.cs

     ). Check standard test directories (

     tests/

     ,

     spec/

     ,

     __tests__/

     , or adjacent test projects).
   • If ANY identified file lacks a corresponding test → MANDATORY: use

     AskUserQuestion

     :
     • Option A: "Run

       /integration-test

       now" (Recommended)
     • Option B: "Tests already written/updated — proceed"
   • No silent skip. Business logic changes without test coverage MUST be surfaced to the user.
   • If no business logic files changed, or all have matching tests → skip silently

2. Sync knowledge graph (skip if

   .code-graph/

   dir doesn't exist):

   if [ -d ".code-graph" ]; then python .claude/scripts/code_graph sync --json && python .claude/scripts/code_graph update --json; fi
   

   Report results briefly.

3. Mark this task as

   completed

   via

   TaskUpdate

4. Announce to the user: "Workflow [name] completed. Next prompt will trigger fresh workflow detection."

5. The

   workflow-step-tracker

   hook handles the actual state cleanup automatically when this skill completes

---

See Also

• Skill:

  /workflow-start

  - Start/switch workflows
• Hook:

  workflow-step-tracker.cjs

  - Clears state on final step completion
• Hook:

  workflow-router.cjs

  - Detects active vs inactive workflows

---

Closing Reminders

• IMPORTANT MUST ATTENTION break work into small todo tasks using

  TaskCreate

  BEFORE starting
• IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
• IMPORTANT MUST ATTENTION cite

  file:line

  evidence for every claim (confidence >80% to act)
• IMPORTANT MUST ATTENTION add a final review todo task to verify work quality <!-- SYNC:critical-thinking-mindset:reminder -->
• MUST ATTENTION apply critical thinking — every claim needs traced proof, confidence >80% to act. Anti-hallucination: never present guess as fact. <!-- /SYNC:critical-thinking-mindset:reminder --> <!-- SYNC:ai-mistake-prevention:reminder -->
• MUST ATTENTION apply AI mistake prevention — holistic-first debugging, fix at responsible layer, surface ambiguity before coding, re-read files after compaction. <!-- /SYNC:ai-mistake-prevention:reminder -->