config-audit/commands/status.md
Kjell Tore Guttormsen caee558e79 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>
2026-04-08 08:58:35 +02:00

2.9 KiB

name description allowed-tools model
config-audit:status Show current session state and available actions Read, Glob sonnet

Config-Audit: Status

Display current session state and guide next actions.

Usage

/config-audit status

Implementation

  1. Find active session:

    Glob: ~/.claude/config-audit/sessions/*/state.yaml
    Sort by modification time
    Use most recent
    
  2. Read session state:

    session_id: "20250126_143022"
    current_phase: "analyze"
    completed_phases: ["discover", "analyze"]
    next_phase: "interview"
    ...
    
  3. Display status:

    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    Config-Audit Session Status
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
    Session:  20250126_143022
    Started:  2025-01-26 14:30:22
    
    PHASE PROGRESS
    ──────────────
    ✓ Phase 1: Discover   - 15 files found (current directory)
    ✓ Phase 2: Analyze    - report generated
    ○ Phase 3: Interview  - not started (optional)
    ○ Phase 4: Plan       - not started
    ○ Phase 5: Implement  - not started
    
    NEXT ACTION
    ───────────
    Run: /config-audit interview
    Or:  /config-audit plan (skip interview)
    
    SESSION FILES
    ─────────────
    Scope:    ~/.claude/config-audit/sessions/20250126_143022/scope.yaml
    Findings: ~/.claude/config-audit/sessions/20250126_143022/findings/
    Report:   ~/.claude/config-audit/sessions/20250126_143022/analysis-report.md
    
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
  4. If no session found:

    No active config-audit session found.
    
    Start a new audit with:
    /config-audit           # Full audit with auto-scope
    /config-audit discover  # Discovery phase only
    

Session Information

Display based on completed phases:

Phase Info to Display
scope Scope type, paths to scan
discover Files found count, issues count
analyze Conflicts, duplicates, opportunities
interview Preferences summary
plan Actions count, risk level
implement Success/fail counts, backup location

List All Sessions

With all flag:

/config-audit status all

Shows:

All config-audit sessions:

| Session | Phase | Created |
|---------|-------|---------|
| 20250126_143022 | analyze | 2025-01-26 14:30 |
| 20250125_091500 | complete | 2025-01-25 09:15 |
| 20250120_160000 | implement | 2025-01-20 16:00 |

Resume Session

If multiple sessions exist:

/config-audit resume {session-id}

Sets that session as active and continues from last phase.