choose-by-consequencelisted
Install: claude install-skill theonly1me/shadowclone
# Choose by Consequence
## Use when
The code must decide what happens when something is unusual or fails. Examples: a file is a symbolic link, a tool is missing, or a step times out. Each of these is a behavior choice. A choice is risky when it touches owned or shared files, data, security, or public behavior such as output and exit codes.
## Gates
1. For each option, can you say what the user sees and what happens to their files and data? If not, check before you choose.
2. While you plan, did you give each risky choice to the user as an open decision? Put the option that fails loudly first.
3. While you execute, did you pick the option that fails loudly? A skip is loud only when the summary counts it, the final output names it, and the exit code shows it.
4. Do all counts, totals, and statuses in the output still match what happened?
5. Does any write go through a file that the change does not own, such as a symbolic link target? If so, block, and name both paths.
6. Does the handoff list each choice with the real output line that shows it?
## Process
### While you plan
1. List the options. Usual options: do the full job safely, block with an error, skip with a visible line, ask, or fall back.
2. For each option, write its hidden cost: who finds the problem, when, and what the recovery costs.
3. Put each risky choice to the user as one question with 2 to 4 options. Put the option that fails loudly first, and give one reason for it.
### While you execute
1. Do not a