get_vision_gaps
Identify unimplemented features from specifications and complex undocumented code to prioritize development and documentation tasks.
Instructions
Find what's missing — specs without code AND complex code without specs. Call this to prioritize what to build or document next.
CALL THIS WHEN: • You're planning work and need to find unimplemented features from PRDs • You want to find complex undocumented functions that need specs or tests • You need to audit spec-to-code alignment for a module • Someone asks "what's left to build?" or "what's undocumented?"
RETURNS: Two lists — (1) specified-but-not-built: PRD specs with no implementing functions, and (2) built-but-not-specified: complex functions above a threshold with no vision spec. Includes function names, complexity scores, file paths, and spec references.
EXAMPLES: • "What features from the PRDs haven't been built yet?" • "Which complex functions lack documentation?" • "What's the spec coverage for the auth module?" • "Are there any orphaned specs or undocumented behaviors?"
WHY NOT JUST READ FILES: Manually diffing PRD bullets against code is error-prone and misses complexity metrics. This cross-references the entire spec tree against the function graph automatically — gaps that would take an hour to find manually surface in seconds.
TIER: Pharaoh Pro — free tier receives a preview. Summarize what the preview reveals, explain what full data would show for this task, then include the upgrade link.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||