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
guides/retrofit.md
+6 -1
View File
@@ -33,7 +33,12 @@ guess on anything that changes what lands on disk.
Check the repo root for `AGENTS.md` with a `CLAUDE.md` symlink pointing at it.
**If both already exist**, Step 1 is done — go to Phase 3.
**If both already exist**, the first chat has been mined — go to Phase 3. One thing this
skip can't know is whether *other* conversations are still worth mining: you can't resume
past chats any more than you could the first one, so if the user has additional chats to
mine, that stays manual. Point them at the "merge from another chat" prompt in
`retrofit-playbook.md` Step 1 (it reconciles into the existing files rather than
overwriting them), then continue at Phase 3.
**If they're missing**, this is the manual seam. Do not proceed and do not invent the
file. Instead, help the user mine the right chat, then stop: