claude-planning-system

Pre-planning consultant — gap analysis and guardrail generation before the planner runs. Catches blind spots the planner (Prometheus) missed and passes them as Directives. Named after the Greek goddess of wisdom, prudence, and deep counsel. Use when: plan validation, gap analysis, complex scope clarification, ambiguous requirements before planning, quality gate before prometheus-planning. Do NOT use for: simple single-file tasks, direct implementation requests.

Practical plan reviewer — answers one question: "Can a developer execute this without getting stuck?" Verifies file references, checks executability, blocks only true blockers. Max 3 issues, strong approval bias.

Interview-based strategic planning for deeply detailed plans (beyond writing-plans). Full cycle: intent classification → research → interview → plan generation → verification. Use when: complex multi-phase projects, new project from scratch, architecture decisions, "프로메테우스", "상세 플랜", "deep plan". Do NOT use for: simple tasks, single-file changes, quick fixes (use writing-plans instead).