why
Use for 'why does X work this way', 'why does this kernel use this tile size', 'why does this dispatch threshold exist', 'why was this perf guard added', design rationale, regressions, or postmortems. Discovers available MCPs and queries each evidence category (code history, source control and PRs, issue tracker, long-form docs, chat) in parallel, with an incident lens for defensive code, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
Pinned to revision bd140d538861, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/why/SKILL.md
- skills/why/references/epistemics.md
- skills/why/references/investigator-prompt.md
- skills/why/references/source-playbook.md
- skills/why/references/sources/code-archaeology.md
- skills/why/references/sources/confluence.md
- skills/why/references/sources/github.md
- skills/why/references/sources/incident-postmortem.md
- skills/why/references/sources/jira.md
- skills/why/references/sources/slack.md
- skills/why/references/synthesizer-prompt.md
Every link opens the file at its source, pinned to the revision this page describes.