librenotes/.wave/prompts/speckit-flow/specify.md

You are creating a feature specification for the following request:

{{ input }}

Working Directory

You are running in an isolated git worktree checked out at main (detached HEAD). Your working directory IS the project root. All git operations here are isolated from the main working tree and will not affect it.

Use create-new-feature.sh to create the feature branch from this clean starting point.

Instructions

Follow the /speckit.specify workflow to generate a complete feature specification:

1. Generate a concise short name (2-4 words) for the feature branch
2. Check existing branches to determine the next available number:

   git fetch --all --prune
   git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-'
   git branch | grep -E '^[* ]*[0-9]+-'
   

3. Run the feature creation script:

   .specify/scripts/bash/create-new-feature.sh --json --number <N> --short-name "<name>" "{{ input }}"
   

4. Load .specify/templates/spec-template.md for the required structure
5. Write the specification to the SPEC_FILE returned by the script
6. Create the quality checklist at FEATURE_DIR/checklists/requirements.md
7. Run self-validation against the checklist (up to 3 iterations)

Agent Usage

Use 1-3 Task agents to parallelize independent work:

• Agent 1: Analyze the codebase to understand existing patterns and architecture
• Agent 2: Research domain-specific best practices for the feature
• Agent 3: Draft specification sections in parallel

Quality Standards

• Focus on WHAT and WHY, not HOW (no implementation details)
• Every requirement must be testable and unambiguous
• Maximum 3 [NEEDS CLARIFICATION] markers — make informed guesses for the rest
• Include user stories with acceptance criteria, data model, edge cases
• Success criteria must be measurable and technology-agnostic

Output

Produce a JSON status report matching the injected output schema.