akka-specifylisted

## User Input You **MUST** consider the user input before proceeding (if not empty). ## Outline The text the user typed after `/akka:specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `the user's request` appears literally below. Do not ask the user to repeat it unless they provided an empty command. Given that feature description, do this: 0. **Prerequisite check**: Before doing anything else, verify the environment is ready: - Call `akka_sdd_list_specs` — if this MCP tool is not available, the Akka MCP server is not configured. Stop and tell the user: *"The Akka MCP server is not running. Run `/akka:setup` first to configure your project, or run `akka specify init .` from the terminal."* - Check if the current directory has a `pom.xml` or `.akka/` directory. If neither exists, warn: *"This doesn't look like an Akka project directory. Run `/akka:setup` to scaffold a new project, or `cd` into an existing one."* - If both checks pass, proceed. 1. **Generate a concise short name** (2-4 words) for the branch: - Analyze the feature description and extract the most meaningful keywords - Create a 2-4 word short name that captures the essence of the feature - Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug") - Preserve technical terms and acronyms (OAuth2, API, JWT, etc.) - Keep it concise but descriptive enough to understand the feature at a g