ktg-plugin-marketplace/plugins/config-audit/commands/plan.md

name	description	allowed-tools	model
config-audit:plan	Phase 4 - Generate prioritized action plan with risk assessment	Read, Write, Glob, Grep, Agent	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:

### 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.