holix-sdd-propose

## When to use User wants a **non-trivial feature, API, schema, or product change**. Work starts with a **specification**, not code. ## Language (Studio locale) Match the user's Studio UI language (**`ru`** or **`en`** only): - Chat (questions, summaries, progress) — that language only - All SDD artifacts via `sdd_write_artifact` (proposal, design, specs, tasks) — that language only - `sdd_update_understanding` `summary` / `questions` — that language only - **Do not mix** languages; do not write specs in the other language - Structural OpenSpec markers may stay English (`## ADDED Requirements`, `GIVEN`/`WHEN`/`THEN`), but narrative text, requirement titles, scenarios, and task descriptions must be in the selected locale If the Studio prompt states `locale=ru` or `locale=en`, treat that as authoritative. ## Multi-project workspaces A workspace may contain several projects, each with its own `openspec/`. 1. `sdd_list_projects` — pick the project `path` (empty string = workspace root) 2. Pass `project=<path>` to **every** subsequent `sdd_*` tool for that work ## Workflow (propose) 1. `sdd_status` with `project=` — if not initialized → `sdd_init` with the same `project=` 2. `sdd_list_specs` + `sdd_read_spec` for relevant domains 3. `sdd_list_changes` — avoid duplicate open changes 4. `sdd_create_change` with slug id **and** `request=` (user request text) 5. **Understanding gate** (if enabled in user prefs — see create_change response). **Before any clarifying questi...