feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command

Add /ultraresearch-local for structured research combining local codebase
analysis with external knowledge via parallel agent swarms. Produces research
briefs with triangulation, confidence ratings, and source quality assessment.

New command: /ultraresearch-local with modes --quick, --local, --external, --fg.
New agents: research-orchestrator (opus), docs-researcher, community-researcher,
security-researcher, contrarian-researcher, gemini-bridge (all sonnet).
New template: research-brief-template.md.

Integration: --research flag in /ultraplan-local accepts pre-built research
briefs (up to 3), enriches the interview and exploration phases. Planning
orchestrator cross-references brief findings during synthesis.

Design principle: Context Engineering — right information to right agent at
right time. Research briefs are structured artifacts in the pipeline:
ultraresearch → brief → ultraplan --research → plan → ultraexecute.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

commands/plan.md

@@ -0,0 +1,82 @@
+---
+name: config-audit:plan
+description: Phase 4 - Generate prioritized action plan with risk assessment
+allowed-tools: Read, Write, Glob, Grep, Agent
+model: opus
+---
+
+# Config-Audit: Plan Generation (Phase 4)
+
+Generate a prioritized action plan based on analysis results.
+
+## Prerequisites
+
+- Must have completed Phase 2 (analysis)
+- Phase 3 (interview) is optional — plan works with or without it
+
+## Implementation
+
+### Step 1: Verify session state
+
+Find the most recent session with analysis completed. If none found: "No analysis results found. Run `/config-audit` first to scan your configuration."
+
+### Step 2: Tell the user what's happening
+
+```
+## Creating Action Plan
+
+Building a prioritized plan based on your analysis results...
+Actions are ordered by impact, with risk assessment and dependency tracking.
+```
+
+### Step 3: Spawn planner agent
+
+Tell the user: **"Generating your action plan (this takes about 30 seconds)..."**
+
+```
+Agent(subagent_type: "config-audit:planner-agent")
+  model: opus
+  prompt: |
+    Generate action plan based on:
+    - Analysis: ~/.claude/config-audit/sessions/{session-id}/analysis-report.md
+    - Interview: ~/.claude/config-audit/sessions/{session-id}/interview.md (if exists)
+    Create prioritized plan with:
+    - Risk assessment per action (low/medium/high)
+    - Rollback strategy
+    - Dependency ordering
+    - Effort estimates
+    Output to: ~/.claude/config-audit/sessions/{session-id}/action-plan.md
+```
+
+### Step 4: Present the plan summary
+
+Read the generated plan and show a concise overview:
+
+```markdown
+### Action Plan Ready
+
+**{N} actions** organized by priority:
+
+| # | Action | Risk | Effort |
+|---|--------|------|--------|
+| 1 | {title} | {low/med/high} | {quick/moderate/involved} |
+| 2 | ... | ... | ... |
+| ... | ... | ... | ... |
+
+Full plan: `~/.claude/config-audit/sessions/{session-id}/action-plan.md`
+
+You can edit the plan file to remove, reorder, or modify actions before implementing.
+
+### What's next
+
+- **`/config-audit implement`** — Execute the plan with automatic backup and verification
+- **`/config-audit interview`** — Set preferences first to customize the plan (optional)
+```
+
+### Step 5: Update state
+
+Update `state.yaml` with `current_phase: "plan"`, `next_phase: "implement"`.
+
+## Plan Modification
+
+Users can edit `action-plan.md` before implementation — remove unwanted actions, adjust priority, or add custom actions. The implementer parses the modified plan.