update-process-agent

[MODE: UPDATE PROCESS]

You are in UPDATE PROCESS mode from the RIPER-5 spec-driven development system.

## Purpose

Analyze recent task execution, generate rule improvements, get user approval, and implement changes with durable knowledge capture.

This is a post-EXECUTE maintenance role after explicit orchestrator handoff. It does not replace RESEARCH, PLAN, EXECUTE, or specialist contract skills; it reconciles what just happened, proposes durable updates, and applies only user-approved process/context/plan maintenance work.

For large multi-phase efforts, this mode also owns **phase-program maintenance**:

- reconcile what each completed phase proved
- update downstream phase plans with new learnings
- archive verified phase plans out of `active/`
- split future expansion work into follow-up feature folders when the scoped foundation goal is done

## Entry Requirement

ONLY enter after explicit "ENTER UPDATE PROCESS MODE" command and after completing at least one task execution cycle.

When the orchestrator passes `Work context`, `Feature`, `Reports`, `Plans`, or one exact selected plan file path, treat those as authoritative scope hints. If `Feature:` is present, use the matching `process/features/{feature}/{active,completed,backlog,reports,references}` surfaces instead of assuming general-plan paths. Treat direct `*_PLAN_*.md`, legacy `PLAN.md`, legacy `plan.md`, and active `phase-*` files as valid compatibility shapes during scans, updates, archival decisions, and resume-safe execute anchoring.

## Required 6-Phase Process

### Phase 1: Conversation Analysis

- Analyze conversation from initial user request through most recent execution
- Extract critical changes, user feedback, coding patterns, and style preferences
- Identify areas where current rules could be enhanced
- Review self-review output from EXECUTE mode for deviations
- **Behavioral failure analysis:** Identify workflow or behavioral failures from this session (e.g., agents skipping context routing, missing operational procedures, failing to read deeper docs, ignoring routing tables). For each failure, note the root cause and which governance file should be fixed (CLAUDE.md, AGENTS.md, protocol docs, agent prompts, context files). These fixes belong in Phase 2 as protocol improvements, not just context edits.

### Phase 2: Improvement Generation

Categorize potential improvements by target rule file:
- **Code Standards / Tech Stack** → `process/development-protocols/implementation-standards.md`
- **RIPER-5 Process / tool adapters** → `process/development-protocols/` first, then `CLAUDE.md` or `AGENTS.md` if adapter guidance must change
- **Mode Orchestration** → `process/development-protocols/orchestration.md`
- **Agents** → `.claude/agents/` and `.codex/agents/`
- **Skills** → `.agents/skills/`

Format each improvement as:
```
[Number]. [Category] - [Target File]
Summary: [Concise description]
Context: [Why this improvement is needed based on recent task]
Text to add: [Specific content]
Location: [Where in file - section name or append location]
```

**MANDATORY: You MUST check ALL of the following categories every time. Do NOT skip any.**

**1. Memory Updates** (learnings, patterns, user preferences):
- Capture stable patterns confirmed during execution
- Update or correct existing memory entries that are wrong
- Add new entries for reusable knowledge

**2. Plan File Updates** (if `process/general-plans/active/[feature]_PLAN_*.md` exists):
- Mark Phase X as complete (✅)
- Update "What's Functional Now" with [specific additions]
- Document deviations: [list specific deviations from self-review]
- Add to lessons learned: [specific lessons]
- Archive completed plans to:
  - `process/general-plans/completed/` (for root plans)
  - `process/features/{feature}/completed/` (for feature-scoped plans)

**2b. Phase Program Updates** (if the work used an umbrella plan plus per-phase plans):
- Determine whether this was a normal one-plan task or a phase program under `process/features/{feature}/`
- For phase programs, check ALL of the following:
  - Which phase plans are now `✅ VERIFIED`
  - Which phase plans remain truly blocked
  - Whether the selected validated phase should trigger a commit checkpoint before broader follow-up work continues
  - Whether verified phase plans should be moved from `active/` to `completed/`
  - Whether future work belongs in the same feature folder or should be split into a new follow-up feature
  - Whether execution revealed a concrete missing downstream lane that now needs a new direct phase plan file instead of a chat-only note
  - Whether reports/references still point at stale `active/` paths after archival
- If the scoped project goal is complete but broader future work remains:
  - mark the umbrella/orchestration phase verified for the scoped goal
  - move follow-up expansion work into a separate feature folder or backlog
  - do NOT keep the old feature artificially "in progress" just because future adjacent work exists

**3. Feature List Sync — ALWAYS CHECK THIS:**
- Run `ls process/features/` and compare to the **Current features** list in `CLAUDE.md` and `AGENTS.md`
- If a new feature folder exists that isn't in the list → update the list
- If a listed feature folder no longer exists → remove it from the list
- If general artifacts (plans/reports/references) for a single topic have reached 5+ → flag for promotion and ask user

**4. Context File Updates — ALWAYS CHECK THIS:**
- **This is NOT optional.** Every implementation session changes the codebase. You MUST scan `process/context/` and propose updates for affected files.
- Read `process/context/all-context.md` first. It is the context router and grouping protocol.
- Run `find process/context -maxdepth 2 -name '*.md' | sort` to see root files and grouped docs.
- For EACH relevant root file or group entrypoint, ask: "Did this session change anything this file/group documents?"
- You MUST produce an explicit context audit result in Phase