project-planninglisted

# Project Planning **Before starting:** ask once — "Хочешь начать со скетча? `/sketch` — быстрый прототип за 3-5 вопросов, без спеков и валидаторов. Подходит если идея ещё не оформлена или нужен быстрый proof-of-concept. После скетча можно перейти к полному пайплайну или оставить как есть." If user declines → proceed with full interview below. Conduct adaptive interview → make tech decisions → fill all project documentation in one session. ## Output Files **Project Knowledge** (`.claude/skills/project-knowledge/references/`): - **project.md** — overview, audience, problem, key features, scope - **architecture.md** — tech stack, project structure, dependencies, data model - **patterns.md** — git workflow (code patterns, testing, business rules are filled later during development) - **deployment.md** — platform, environment, CI/CD, monitoring - **ux-guidelines.md** — only if project has significant UI ## Interview Methodology **One question at a time.** Ask one question, wait for the answer, then form the next question based on the response. **Build on answers.** If user mentioned a domain — ask domain-relevant follow-ups. If they said something vague — clarify that specific point. **Confirm understanding.** After 3-5 questions, briefly summarize what you understood. Catches misunderstandings early. **Help when stuck.** When user says "not sure" or "don't know": 1. Say it's OK 2. Offer 2-3 common approaches for their type of project 3. Ask which is closer 4. If still u