Name: Analysis Spec Builder
Author: gordonwatts

Workflow

Read the template from ./assets/analysis-specification-template.md (relative to the this file, in the analysis-spec-building sub directory).
Draft a filled-in specification by replacing all {{...}} placeholders with concrete content derived from the user's request.
Ask focused follow-up questions for any missing critical details (datasets, selections, histogram definitions, workflow steps, tooling). Keep questions short and grouped by section.
Iterate revisions until the user confirms the specification is correct.
Write the final content to specification.md unless the user provides a different path.

Drafting Rules

Replace every {{...}} placeholder with real content; do not leave placeholders in the final spec.
Keep the tone concise and technical; preserve the template section order.
If something is unknown, propose a reasonable default and mark it as a question in the next response (do not leave placeholders).
Preserve any explicit dataset identifiers or analysis names verbatim. Assume the user will use PHYSLITE unless told otherwise, or you know the data isn't available there.

Read the template from ./assets/analysis-specification-template.md (relative to the this file, in the analysis-spec-building sub directory).
Draft a filled-in specification by replacing all {{...}} placeholders with concrete content derived from the user's request.
Ask focused follow-up questions for any missing critical details (datasets, selections, histogram definitions, workflow steps, tooling). Keep questions short and grouped by section.
Iterate revisions until the user confirms the specification is correct.
Write the final content to specification.md unless the user provides a different path.

Replace every {{...}} placeholder with real content; do not leave placeholders in the final spec.
Keep the tone concise and technical; preserve the template section order.
If something is unknown, propose a reasonable default and mark it as a question in the next response (do not leave placeholders).
Preserve any explicit dataset identifiers or analysis names verbatim. Assume the user will use PHYSLITE unless told otherwise, or you know the data isn't available there.