Compare PRD.md against all files in the /src folder to find missing implementations, discrepancies, or deviations from the requirements. Use this skill when the user asks to verify implementation status against the PRD.
This skill guides you through the process of systematically comparing the PRD.md document with the contents of the src/ directory to identify what has been implemented, what is missing, and what deviates from the defined requirements.
To perform a comprehensive comparison, follow these steps:
Use the view_file tool to fully read and analyze PRD.md. Extract a mental checklist or use task.md to list the core features, functional requirements, and workflows required by the PRD.
Instead of attempting to read every single file manually (which would exceed context limits), map each PRD requirement to expected file names, API routes, components, or database models. Use the following tools to verify implementations:
find_by_name: Locate relevant files (e.g., *Actions.ts, *Dialog.tsx).grep_search: Look for specific keywords, function names, or business logic defined in the PRD across the directory.src/For each PRD requirement:
view_file on the key files to ensure the business logic inside matches the PRD requirements (e.g., verifying roles, permissions, API responses).Compile your findings into an artifact (like PRD_COMPARISON.md). The report should include:
/src.cat or Get-Content to print the entire /src folder contents. Rely on grep_search and targeted file viewing.