get_vision_docs
Retrieve design documents like PRDs and CLAUDE.md files to understand code intent and verify implementation against original specifications.
Instructions
Get the documented intent — CLAUDE.md files, PRDs, roadmaps, skill specs — to understand WHY code exists, not just what it does.
CALL THIS WHEN: • You're implementing a feature and need to check if a PRD or spec exists for it • You want to understand the original design intent behind existing code • You need to verify your implementation matches documented requirements • You're reviewing code and want to check it against the documented vision
RETURNS: All vision documents grouped by type (claude_md, prd, skill, roadmap), with each spec's title, section ID, and implementation status showing which functions implement each spec.
EXAMPLES: • "Is there a PRD for the notification system?" • "What does the CLAUDE.md say about the auth module?" • "What specs exist for the slack integration?" • "Which specs are already implemented vs still pending?"
WHY NOT JUST READ FILES: Vision docs are scattered across CLAUDE.md files, PRDs, and roadmaps in different directories. This aggregates them all AND cross-references against actual implementations so you can see spec-to-code alignment in one call.
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 | |||