Why — multi-source design-rationale investigations (short pointer)
Answer "why does this code exist" with parallel investigator agents over git, tickets, docs, chat, observability, errors and analytics — short pointer
- What
- Answer "why does this code exist" with parallel investigator agents over git, tickets, docs, chat, observability, errors and analytics — short pointer
- Cost
- Free
- Needs
- an agent environment with subagents and MCP access (the workflow is written for Cursor — adapt the orchestration to your harness); no license declared in the source repo — read it yourself before reusing its content
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a short pointer to @cursor's why skill: a rigorous methodology for answering "why does this code work this way" instead of "what does it do". The workflow anchors the investigation in concrete code (blame, log, PR numbers), then spawns parallel investigator agents — one per evidence category: source control, issue tracker, long-form docs, team chat, infrastructure observability, error tracking, product analytics warehouse — over the MCPs available in the environment, and synthesizes the findings under a strict epistemics framework (what we know, what we infer, competing hypotheses, what we don't know, one line per source consulted). Honest caveats: **no license declared in the repository manifest — license unknown**, so this is a short fiche linking to the source, without reusing its content; it is built for Cursor's environment (MCP discovery, Task subagents, `pstack-models.mdc` model slugs) — adapt the orchestration to your own agent harness; expect heavy compute on wide sweeps. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: an agent environment with subagents and MCP access (the workflow is written for Cursor — adapt the orchestration to your harness); no license declared in the source repo — read it yourself before reusing its content Install "Why — multi-source design-rationale investigations (short pointer)" for me. Fetch the SKILL.md from the source repository into a temporary folder, review it for anything suspicious, and report in two or three sentences what the why workflow covers (code anchoring, parallel per-category investigators, epistemics-framed synthesis) so I can adapt it to my own agent setup. Do not copy the workflow's content into my project — this is a reference lookup only. Repository: https://github.com/cursor/plugins/blob/main/pstack/skills/why/SKILL.md GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.