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

name	description	allowed-tools	model
config-audit:interview	Phase 3 - Interactive interview to gather user preferences	Read, Write, Edit, AskUserQuestion	sonnet

Config-Audit: Interview (Phase 3)

Gather user preferences to inform the action plan.

IMPORTANT: Inline Execution Only

This command runs AskUserQuestion directly in the main context — NOT via a Task subagent. AskUserQuestion requires synchronous terminal interaction and does not work when delegated to a Task subagent.

Prerequisites

• Must have completed Phase 2 (analysis)
• Read analysis from ~/.claude/config-audit/sessions/{session-id}/analysis-report.md

Implementation Steps

1. Load session state: Verify analysis phase completed, read analysis report for context
2. Conduct interview inline: Use AskUserQuestion tool directly (NOT via Task). Adapt questions based on analysis findings.
3. Save interview results: Write to ~/.claude/config-audit/sessions/{session-id}/interview.md
4. Update state (see state-management rule)
5. Output summary

Interview Questions

Ask these using AskUserQuestion (skip questions that don't apply based on analysis):

1. Config Style — Centralized vs Distributed vs Hybrid organization
2. Unused Hooks — Wire up, review individually, delete, or leave (only if found)
3. Duplicate Permissions — Remove from local, consolidate, or keep (only if found)
4. Modular Rules — Use .claude/rules/ pattern? Yes/No
5. Path-Scoped Rules — Which patterns (tests, src, config, docs) — only if Q4=Yes
6. Conflict Resolution — Per-conflict: global vs project vs custom value (only if conflicts found)
7. Permission Audit — Audit or keep (only if >30 patterns in settings.local.json)
8. Project Inheritance — Per-project: inherit or isolate (only if multiple projects)

Adaptive Questioning

Skip questions that don't apply:

• No unused hooks question if all hooks are wired
• No duplicates question if no duplicates found
• No conflict questions if no conflicts detected
• No path-scoping if user said no to modular rules
• Fewer project questions if only one project
• No permission audit if <30 patterns

Skip Interview Option

If user runs /config-audit plan without interview:

• Use sensible defaults (centralized, inherit, enable rules)
• Flag decisions in plan as "assumed"

Error Handling

• If user selects "Other" for any question, ask follow-up with AskUserQuestion
• If interview is cancelled, save partial results
• If no analysis report found, report error and exit
• If AskUserQuestion fails, STOP — do not use alternative methods