swe-feature-update

## ⚠️ WORKFLOW INITIALIZATION

**If starting a new session**, first read workflow initialization:
```
mcp__plugin_swe_serena__read_memory("WF_INIT")
```
Follow WF_INIT instructions before executing this skill.

---

# /swe-update-feature [KEY]

Update a specific feature's memory files to accurately reflect current codebase state.

## Usage

```bash
/swe-update-feature BLOCKS           # Update BLOCKS feature memories
/swe-update-feature THEME_DISTRICT   # Update THEME_DISTRICT feature memories
/swe-update-feature TESTS            # Update TESTS feature memories
```

## Purpose

Synchronize feature documentation with actual codebase:

- Update directory listings and file inventories
- Refresh architecture layers and patterns
- Update entry points and key files
- Sync related memories (ARCH_*, INDEX_*, DOM_*)

---

## Stage 1: Validate Feature

**Verify feature exists:**

```javascript
mcp__plugin_swe_serena__read_memory("INDEX_FEATURES")
```

**Check:** Feature key exists in registered features table.

**If not found:**
```
> Feature [KEY] not registered. Use /swe-feature-onboard [KEY] to register it first.
```
Exit skill with `needs_clarification` status.

---

## Stage 2: Load Current Feature Memory

```javascript
mcp__plugin_swe_serena__read_memory("FEATURE_[KEY]")
```

**Extract from current memory:**
- Root path(s)
- Primary language
- Framework
- Type
- Architecture layers
- Related memories list

---

## Stage 3: Analyze Current Codebase State

**For each root path in the feature:**

### 3.1 Directory Structure

```javascript
mcp__plugin_swe_serena__list_dir({ relative_path: "[root_path]", depth: 2 })
```

### 3.2 Key Files Inventory

```javascript
mcp__plugin_swe_serena__get_symbols_overview({ relative_path: "[root_path]" })
```

### 3.3 Pattern Detection

Use Serena tools to detect:
- Entry points (main files, index files)
- Configuration files
- Test files
- Template files

---

## Stage 4: Compare and Identify Changes

**Compare current state vs. documente