Ask Jev

The sources for a piece of work (a design, a spec, a ticket, the code) often leave Open questions: judgment calls they do not settle, such as what an empty state shows or what happens on a failed submit. Instead of stopping to ask about each one, put them to Jev, TypeSafe's System One model, which picks one of the options you give it and reports how sure it is. Adopt the answers Jev is sure of, and send the rest in one questionnaire to the Decider: the one person this run names to settle what Jev cannot, the PM unless the user names someone else.

Your deliverables are a Jev ruling for every Open question, recorded in the project; when you are writing code, the code changes the adopted rulings call for; and a questionnaire when anything still needs the Decider.

If the user passed an argument, it names the work or the Open questions in question. Otherwise take the work in progress in the conversation.

When the source is a Figma design, read references/figma.md in this skill's folder before step 2: it covers the facts, the state, and the screenshots a design calls for.

Keep this run's working files in one run folder: a new folder in the system temp directory, outside the repo, named ask-jev-<topic>-<date>-<suffix>/, with the topic and date from step 2 and a short random suffix. Every run creates its own, so an earlier run of the same topic, or a run in another repo, never leaves files in it.

1. Check the key

The API key lives in ~/.config/typesafe/typesafe-key.header, a one-line file of the form Authorization: Bearer <key>. Check only that the file exists; its contents stay out of the conversation, so never open, print, or echo it.

When it is missing, tell the user to copy typesafe-key.header.example from this skill's folder to that path, replace the placeholder with their key, and run the skill again. Stop there.

Done when the file exists.