Individual skill
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
skills/why/SKILL.md
Source commit 09909ebb5c0125e27fad3e57d96b81e832696d69
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 161
- Repository last updated
- Oct 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,154 bytesSKILL.mdcore · 10,154 bytesSKILL.mdcore · 10,154 bytesSKILL.mdcore · 10,154 bytesSKILL.mdcore · 10,154 bytesSKILL.mdcore · 10,154 bytesreferences/epistemics.mddoc · 7,749 bytesreferences/investigator-prompt.mddoc · 7,118 bytesreferences/source-playbook.mddoc · 1,366 bytesreferences/sources/code-archaeology.mddoc · 3,489 bytesreferences/sources/databricks.mddoc · 6,994 bytesreferences/sources/datadog.mddoc · 5,323 bytesreferences/sources/incident-postmortem.mddoc · 1,973 bytesreferences/sources/linear.mddoc · 2,996 bytesreferences/sources/notion.mddoc · 2,853 bytesreferences/sources/sentry.mddoc · 4,947 bytesreferences/sources/slack.mddoc · 3,105 bytesreferences/synthesizer-prompt.mddoc · 8,084 bytes
Read excerpt
# Why
Investigate the motivation and intent behind code.
Companion to the `how` skill. `how` answers what the code does and how it works. `why` answers what forces led to its shape.
Each delegation below names a role line in `p3-models.md`. Resolve it through `orchestrator_capabilities` and pass that provider and model to `delegate_task`. Never hardcode a slug. If the line or the file is missing, use the session default and say so.
## Operating Posture
Operate as a **careful, cautious, and precise investigator**. Be honest about what you know vs what you're inferring. Read `references/epistemics.md` for the full confidence framework and phrasing guide. The synthesizer must follow it.
## Step 1. Understand the Target and the Question
