why - Investigate why code was designed this way
Investigates code motivation and design rationale by querying available historical evidence sources in parallel and returning cited, confidence-calibrated findings.
Tags
Updated: 2026-10-08Capabilities
Typical Inputs
Typical Outputs
What this skill does
- Investigate design rationale
- Query evidence categories in parallel
- Cite historical findings
- Compare alternative explanations
- Calibrate confidence
- Document evidence gaps
Inputs
- User's why question
- Target code and repository
- Available MCP servers
- Git and pull request history
- Issue, document, chat, observability, error, and analytics records
Outputs
- Cited investigation report
- Evidence coverage map
- Confidence-calibrated findings
- Documented gaps and contradictions
Requirements
- Cursor MCP environment
- Git access
- gh CLI access
- Configured investigator model
- General-purpose subagent support