# Phase 1
## Step 1 — Understand the issue

Read the issue title and body. This is the user's raw feature request.

## Step 2 — Explore the codebase

Use the Agent tool with `model: "haiku"` and `subagent_type: "Explore"` to scan the codebase for context relevant to the feature. Ask the agent to:
- Find all files, types, interfaces, and functions related to the feature's domain
- Identify architectural layers that will be affected
- Note existing patterns and conventions
- Return a structured summary

## Step 3 — Post questions as issue comment

Use `mcp__gitea__create_issue_comment` to post a comment on the issue. The comment body MUST follow this exact format:

```markdown
<!-- mpns-feature-bot -->
# Feature Analysis — Session 01

## Context
<Summary of codebase findings — key files, patterns, existing structures relevant to this feature>

---
## Questions
1. <question>
2. <question>
...

---
*Reply with your answers, then re-run `/fea $ARGUMENTS`.*
```

Rules for questions:
- 3–7 questions per session
- Ask about: ambiguities, domain model decisions, behavioral edge cases, integration points
- Be specific — avoid generic "tell me more" questions
- Use Russian if the issue body is in Russian

Tell the user: "I've posted questions as a comment on the issue. Answer there and re-run `/fea $ARGUMENTS`."