The ambient execution discipline — predict the outcome of every consequential command BEFORE running it and treat any surprise (better or worse) as a model error to investigate; choose the next action by information gain; estimate blast radius before touching anything shared. Trigger this continuously during hands-on work: before running a command/test/query whose outcome matters, when choosing among several possible next actions, and before editing anything with dependents. Do NOT confuse with verification-loop (which says WHEN to run checks — after each edit) or debugging-methodology (which owns hypothesis-testing once a failure is confirmed): this skill governs the epistemic stance around every execution — it is usually what DETECTS the failure those skills then handle.
$npx -y skills add unpaidattention/fable5-methodology --skill predictive-executionInstalls into the current project.
Run `npx skills use "https://github.com/unpaidattention/fable5-methodology" --skill "unpaidattention/fable5-methodology/predictive-execution"` 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/unpaidattention/fable5-methodology" that are relevant to the current task. Run `npx skills add "https://github.com/unpaidattention/fable5-methodology"` and select the relevant skills, then follow their instructions.