grant/standards
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document mining additional chats in the retrofit flow

Browse Source 
The playbook assumed one canonical chat per project. Add a merge prompt to
Step 1 for reconciling further conversations into the existing AGENTS.md/
ROADMAP.md without overwriting, and note in the retrofit guide that the
"files exist" skip can't mine other chats — that stays manual.
This commit is contained in:
Keysat
2026-06-13 07:23:09 -05:00
parent 3bb67d0ea7
commit b9dd7288c4
2 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
retrofit-playbook.md
+6
View File
@@ -88,6 +88,12 @@ Then `/exit`. The old chat's job is done forever.
(Caveat: repeated `/compact` has summarized away some early detail, so treat this as a strong draft — the next step checks it against reality.)
**More than one chat worth mining?** The prompts above *create* AGENTS.md and ROADMAP.md, so run A/B/C only on the first chat. For each additional conversation, `claude --resume` it and paste this *merge* prompt instead — it reconciles into the files rather than overwriting them:
> **Merge from another chat:** First read the current AGENTS.md and ROADMAP.md from disk (and any docs/guides/* they reference) so you know what's already captured. Now go through everything we did in *this* conversation and find what those files don't already have: durable facts (stack, commands, conventions, gotchas, decisions), longer-term backlog, and anything that changes what's currently true. Then reconcile — don't overwrite: add genuinely new durable knowledge to AGENTS.md, add longer-term items to ROADMAP.md (create it if it doesn't exist), and update the "## Current state" section only if this chat reflects more recent state than what's there. Where this chat contradicts what's on disk, don't silently pick one — show me both and ask. Then sweep anything you wrote for secrets and replace them with env-var names. Tell me exactly what you added or changed in each file.
Mine every chat you care about now, while they're the perishable asset; then move to Step 2 and verify the merged result once. (A merged-in chat can be just as compacted as the first — Step 2 is still what checks it against reality.)
### Step 2 — Fresh session: cross-check and verify by running
```