akka-sddlisted

# Akka Spec-Driven Development For Codex Use the Akka CLI MCP server whenever its tools are available. The plugin registers the server with: ```json { "command": "akka", "args": ["mcp", "serve", "--disable-prompt"] } ``` Before using an Akka SDD workflow, verify the MCP server is available by listing MCP tools/resources. If Akka MCP tools are unavailable, tell the user to confirm the plugin is installed/enabled and that `akka mcp serve --disable-prompt` starts from the repo root. ## Project Rules - Follow the repository `AGENTS.md` instructions for Akka SDK component architecture, package layout, tests, and documentation reads. - Prefer Akka MCP tools for spec files, task generation, branch helpers, and Akka CLI operations. - Use local `akka-context/` documentation before coding first-time Akka component types. - For CLI commands run directly from Codex, use non-interactive flags where available: `--disable-prompt`, `--output json`, and explicit context/config options when relevant. ## Claude Command Mapping - `/akka.specify`: create or update a feature specification. Use Akka MCP spec tools first, then create or update `specs/<number>-<short-name>/spec.md`. - `/akka.plan`: create the technical plan from the selected spec. Use Akka MCP template/spec tools, then produce `plan.md`, `research.md`, `data-model.md`, contracts, and quickstart artifacts as needed. - `/akka.tasks`: derive actionable tasks from the plan and write `tasks.md`. - `/akka.implement`: execute `ta