new-spec

Create a new spec file in specs/ by interviewing the user to fill each section of the template. The goal: produce a spec that would pass /analyze-spec with zero ambiguity on the first try.

Steps

1. Initialize

1. Validate the argument: must be lowercase alphanumeric with dashes (e.g. streaming-prover). Reject otherwise.
2. Get the GitHub username: run gh api user --jq .login.
3. Get today's date in YYYY-MM-DD format.
4. Read specs/TEMPLATE.md to understand the required sections.
5. Read jolt-eval/README.md to understand the eval framework — you'll reference it when prompting the user about mechanical verifiability.
6. Explore the codebase to understand what areas the feature name suggests — run an explore agent to gather context. This informs your questions.

2. Interview — Section by Section

Walk through each template section with the user. For each section, ask targeted questions until you have enough to write it with zero ambiguity. Do NOT move to the next section until the current one is clear.

One question at a time. Never batch.