Diagnose

When invoked with $ARGUMENTS, match the described symptom against the decision tree below and route to the appropriate skill. If code paths are referenced, read them first to confirm the match before routing. This skill routes to other skills from Clairvoyance (https://clairvoyance.fyi). It works best when the full collection is installed.

Decision Tree

1. "Something feels wrong but I can't say what"

The symptom is a general sense of unease with no concrete complaint.

→ complexity-recognition: Apply the three-symptom framework to locate the source.

2. "Simple changes require edits in many files"

Change amplification. Branch by cause:

• Shared knowledge is scattered across modules → information-hiding (look for leaked implementation details)
• Old abstractions no longer fit the current shape of the system → code-evolution (check whether the design has kept pace with requirements)
• Module boundaries cut across concerns instead of encapsulating them → module-boundaries (re-evaluate decomposition)