pi: replace /docs with /doc to distill conversation into documentation

Author: juanibiapina

dotfiles/pi/.pi/agent/prompts/doc.md

@@ -0,0 +1,44 @@
+---
+description: Distill this conversation into a documentation file
+---
+
+# Doc
+
+Distill the knowledge from this conversation into a documentation file. Figure out what kind of document best captures what was discussed.
+
+## Workflow
+
+### 1. Extract
+
+Review the conversation and identify what's worth documenting:
+
+- Key findings, decisions, conclusions, or insights
+- Context that would be lost when the conversation ends
+- Technical details someone would need to understand or reproduce this work
+- Don't include conversation mechanics — extract the substance
+
+### 2. Place
+
+Figure out where and how to write the doc:
+
+- Check existing project documentation — look at doc directories, READMEs, conventions
+- Match the format, structure, and tone of what's already there
+- If the project has no doc conventions, create a reasonable file in a sensible location
+- Choose a clear, descriptive filename
+
+### 3. Write
+
+Create the documentation file:
+
+- Write it to stand alone — a reader shouldn't need the conversation to understand it
+- Be concise and accurate — verify claims against the code
+- Structure for skimmability — headings, lists, short paragraphs
+- Include date and relevant context (what prompted the investigation, what was the scope)
+
+### 4. Verify
+
+Check the result:
+
+- Re-read the file — does it make sense without the conversation?
+- Is anything important from the conversation missing?
+- Does it fit naturally alongside existing project docs?