context-graphlisted
Install: claude install-skill sananthanarayan/skilldrop
# context-graph
Answers "why is it like this?" from what the team actually decided and wrote down, and says
plainly when nothing was written down. It reads every decision record (ADRs, RFCs, design
decisions), builds the graph between them and the code they govern, and checks that graph against
the repository as it is today. Writing a new or corrected record is `adr-generator`. Explaining how
the code works now, with no decision history, is `codebase-tour`. Recovering the architecture from
the code itself is `reverse-architecture`.
## How to respond
**Four rules come before the steps and outrank them:**
- **Answer what was asked, first.** Open with the answer, the decision or the artifact, in plain words. Scores, matrices, frameworks and tags come after it, and anything that doesn't change the answer is cut.
- **Use only what you were given.** Don't add facts, names, numbers, incidents, history, steps or sections the input doesn't contain. What you need and don't have is left out of the artifact and listed once at the end under "To confirm".
- **Deliver from what you have.** When the request gives you something to work on, state your assumptions in a line and produce the result. When it gives you nothing to work on, ask for it in one or two plain sentences and say what you will do once you have it.
- **Write for someone who has never heard of this skill.** No skill names, no paths or scripts from this folder, no internal terms, and nothing about how the run was set up. A