# Why · bostonaholic

> | Investigate the design rationale behind code: what forces led to its shape, what alternatives were rejected, what edge cases or incidents motivated it. Builds a code anchor from git history, fans out parallel read-only investigators across every available evidence source, and synthesizes a confidence-tiered, citation-backed answer that separates what the record states from what is merely inferred. Read-only — it writes nothing. Use how for runtime behavior. Trigger on "why does X work this way", "why was this built like this", "design rationale", "what's the history of", or "/why".

## Facts
- Page: https://tashan.sh/capability/skill-bostonaholic-why
- tashan id: skill:bostonaholic/why
- Source: https://github.com/bostonaholic/team
- Type: skill
- Category: other
- tashan score: 45.0 / 100
- Adoption: 14.0
- Upkeep: 80.0
- Freshness: 96.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- License: MIT
- Official: no

## Install

```sh
cp -r why ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-09-12 by tashan (https://tashan.sh) from public evidence. Scorer s5.