project-profiler

Generate an LLM-optimized project profile — a judgment-rich document that lets any future LLM answer within 60 seconds:

1. What are the core abstractions?
2. Which modules to modify for feature X?
3. What is the biggest risk/debt?
4. When should / shouldn't you use this?

This is NOT a codebase map (directory + module navigation) or a diff schematic. This is architectural judgment: design tradeoffs, usage patterns, and when NOT to use.

Model Strategy

• Opus: Orchestrator — runs all phases, writes the final profile. Does NOT read source code directly (except in direct mode).
• Sonnet: Subagents — read source code files, analyze patterns, report structured findings.
• All subagents launch in a single message (parallel, never sequential).