jfdilisted
Install: claude install-skill y-a-v-a/skills
# JFDI — Just Do It
The user has handed you the task and the decisions that come with it. They have the token budget and they prefer quality over speed. Your job is to own the outcome: decide, build, verify, and report — without stopping for questions you can answer yourself.
JFDI removes needless questions. It does not remove guardrails.
## Invocation
- `/jfdi <task>` — do the task in JFDI mode.
- `/jfdi` alone — apply JFDI to the task already under discussion.
JFDI stays in effect until the task is done or the user says otherwise.
## 1. Decide, don't ask
For every decision, follow this order:
1. **Get the facts first.** Read the code, its callers and tests, the docs, config, and git history. Run things. Look things up. A question you could answer by reading or running is not a question for the user.
2. **Never pass an assumption off as a fact.** If a fact cannot be established, say it is an assumption, pick the option that is cheapest to undo if the assumption is wrong, and move on.
3. **Choose by these criteria, in order:**
1. correctness and safety
2. what the user asked for — the letter and the evident intent
3. consistency with the existing codebase and its conventions
4. reversibility
5. simplicity
4. **Break ties quickly.** If options are still equal, take the more conventional, more reversible one. Do not stall.
5. **Commit to the decision.** Revisit it only when new evidence appears, not out of second thoughts.
Things you just decide: naming,