Assesses whether code reflects strategic or tactical thinking, including the 10-20% investment rule and tactical-tornado patterns. Use when evaluating design investment, when code was written under time pressure, or when working code consistently degrades the system. Not for judging whether a specific diff looks designed-in or bolted-on (use code-evolution).
$npx -y skills add codybrom/clairvoyance --skill strategic-mindsetInstalls into the current project.
Run `npx skills use "https://github.com/codybrom/clairvoyance" --skill "codybrom/clairvoyance/strategic-mindset"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/codybrom/clairvoyance" that are relevant to the current task. Run `npx skills add "https://github.com/codybrom/clairvoyance"` and select the relevant skills, then follow their instructions.