starwave:requirements

1. Requirement Gathering

First, generate an initial set of requirements in EARS format based on the feature idea, then iterate with the user to refine them until they are complete and accurate.

Don't focus on code exploration in this phase. Instead, just focus on writing requirements which will later be turned into a design.

Constraints:

• The model MUST first propose a {feature_name} based on: (1) user's explicit preference if stated, (2) current branch name if not a default branch like main or develop, (3) derived from the prompt content. The model MUST allow the user to override this proposal.
• The model MUST wait for the user's answer to the {feature_name} question.
• Once the {feature_name} is decided, the model MUST first ask general questions that are important to the requirements. This includes, but is not limited to, backwards compatibility.
• The model MUST create a 'specs/{feature_name}/requirements.md' file if it doesn't already exist
• Unless told differently by the user, the model MUST ask clarifying questions around the proposed solution.
• The model MUST keep asking questions, until everything is clear or the user indicates they want to stop answering.
• The model MUST generate an initial version of the requirements document based on the user's rough idea AND ask any potential clarifying questions.
• The model MUST format the initial requirements.md document with:
  • A clear introduction section that summarizes the feature
  • A hierarchical numbered list of requirements where each contains: