tech-spec-planninglisted

# Tech Spec Planning > **CRITICAL:** NEVER generate multiple artifacts without stopping. After EACH artifact: list controversial points, explain simply, WAIT for user decision. Only then proceed. Create technical specification through code research, adaptive clarification, and multi-validator review. **Input:** `work/{feature}/user-spec.md` + Project Knowledge **Output:** `work/{feature}/tech-spec.md` (approved) **Language:** Technical documentation in English, communication in Russian Before starting, read [quick-ref-tech-spec-planning.md](../quick-learning/references/quick-ref-tech-spec-planning.md) — top reasoning patterns for this skill (if file exists and non-empty). ## Phase 1: Load Context 1. Ask user for feature name if not provided. Check `work/{feature}/` exists, create if needed. 2. Read `work/{feature}/user-spec.md`. Missing → ask user to describe task or create user-spec first. Extract `size: S|M|L` from frontmatter. 3. Read all files in `.claude/skills/project-knowledge/references/` (missing files are fine). 4. user-spec.md is the single input source — interview.yml and code research are already consolidated there. ## Phase 2: Code Research Launch `code-researcher` subagent (opus) with feature path and user-spec path. It reads existing `code-research.md` (from user-spec phase) and deepens for implementation. After completion — read `{feature_path}/code-research.md`. If gap discovered later — re-launch with specific question. ## Phase 3: Clarification (