byhmbown· 60 skills
Foresight produces bounded forecasts with explicit uncertainty to guide decisions. It is NOT:\n- Preflight checks: Verifying prerequisites before executing a known action (disk space, backups, connection strings). Those are safety gates, not forecasts.\n- Diagnosis/Debugging: Finding what's broken right now (null pointers, deprecated APIs). Those are root-cause analyses, not predictions.\n- Monitoring: Watching real-time metrics or alerting on thresholds. Those are observability tasks, not forward-looking estimates.\n- Reconnaissance: Gathering facts about competitors or systems. Intelligence gathering feeds foresight but isn't foresight itself. Key distinction: If the user wants to know \"what will likely happen if we choose X,\" use Foresight. If they want to know \"is it safe to run X now,\" \"what's broken,\" or \"what are they doing,\" use a different spell.
$npx -y skills add hmbown/wizards-of-the-ghosts --skill foresightInstalls into the current project.
Run `npx skills use "https://github.com/hmbown/wizards-of-the-ghosts" --skill "hmbown/wizards-of-the-ghosts/foresight"` 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/hmbown/wizards-of-the-ghosts" that are relevant to the current task. Run `npx skills add "https://github.com/hmbown/wizards-of-the-ghosts"` and select the relevant skills, then follow their instructions.