Cs Explore

This one helps you explore a codebase and turn your investigation into searchable evidence, so the second time you ask "how does X work here" you find the answer in five minutes instead of two hours. It writes structured exploration docs in three flavors: answering a specific question, mapping out a module, or doing a lightweight technical spike. The format forces you to put conclusions first, then back them with actual file and line references. It checks for overlapping explorations before you start, can update old ones when code changes, and won't let you write "looks like" without proof. Good for onboarding or when you need to build shared knowledge before making design decisions.