specify

Prompt file imported from fetinin/tongi (.codex/prompts/specify.md). Fill in {{arguments}} before use. Copyright stays with the author.

The user input to you can be provided directly by the agent or in {{arguments}} - you MUST consider it before proceeding with the prompt (if not empty).

User input:

{{arguments}}

The text the user typed after /specify in the triggering message is the feature description. Assume you always have it available in this conversation even if {{arguments}} appears literally below. Do not ask the user to repeat it unless they provided an empty command.

Given that feature description, do this:

1. Run the script .specify/scripts/bash/create-new-feature.sh --json "{{arguments}}" from repo root and parse its JSON output for BRANCH_NAME and SPEC_FILE. All file paths must be absolute. IMPORTANT You must only ever run this script once. The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for.
2. Load .specify/templates/spec-template.md to understand required sections.
3. Write the specification to SPEC_FILE using the template structure, replacing placeholders with concrete details derived from the feature description (arguments) while preserving section order and headings.
4. Report completion with branch name, spec file path, and readiness for the next phase.

Note: The script creates and checks out the new branch and initializes the spec file before writing.