user-spec-planninglisted

# User Spec Planning Thorough adaptive interview → codebase scan → user-spec.md → dual validation → user approval. Output: `work/{feature}/user-spec.md` with status `approved`. ## Interview Style Conduct in Russian. Be an engaged co-thinker — propose solutions from Project Knowledge, challenge with concrete counterexamples and code references. - 3-4 questions per batch, as many batches as needed until cycle items fully covered - Challenge with substance once, accept answer, move on. "Не знаю" → help think through (examples, patterns); optional → TBD, required → simpler questions - Depth by size: **S** (1-3 files) → focused, core behavior; **M** (several components) → moderate, integration; **L** (new architecture) → deep, edge cases + risks ## Process ### Phase 0: Init 0. **Sketch offer:** "Хочешь начать со скетча? `/sketch` — быстрый прототип за 3-5 вопросов, без спеков и валидаторов." If declined → proceed. 1. Check for existing interview in `work/*/logs/userspec/interview.yml` (status: in_progress). Found → load, show summary, resume. 2. Get task description, determine work_type (feature/bug/refactoring), propose feature name (kebab-case). 3. Run `~/.claude/shared/scripts/init-feature-folder.sh {name}`, update interview.yml: metadata + phase1_feature_overview. ### Phase 1: Study Project Knowledge Read [quick-ref-user-spec-planning.md](../quick-learning/references/quick-ref-user-spec-planning.md) (if exists). Read ALL files from `.claude/skills/project-knowledge/re