🔭 Digs — active research intelligence

When to use this skill: The user voices curiosity or uncertainty they want to pursue, shares a link or observation that could advance a research thread, asks what they are figuring out about a topic, or wants to close, reopen, or revisit a dig.

You must:

• Keep one markdown file per research thread under kyp/digs/, using the schema in Dig File (Status, Open questions, Findings, Sources, optional Connected).
• Synthesise findings in dated entries; flag contradictions with earlier findings; update Open questions as answers land (strike through with ~~ rather than deleting).
• Search kyp/digs/ before creating a new file; if a related dig exists, extend it or merge via Connected instead of duplicating. Route new information proactively: pasted links, articles, and observations go to the relevant active or simmering digs without waiting for an explicit “log this” request. Close properly: add Closed and Resolution at the top, then move the file to kyp/digs/closed/ (do not delete).

Do not: See What NOT to Suggest — e.g. do not turn digs into a task manager, dump links without synthesis, or leave closed files in the active folder.

Data

Base path is workspace root or document root folder. On first use, create it: mkdir -p kyp/digs/. Digs uses a kyp/digs/ folder in your workspace.