v1.3.3: Learning Capture Protocol and improved session instructions

This commit is contained in:
2025-12-31 13:07:27 -08:00
parent 6a6b4c6fac
commit 474e591f58
4 changed files with 78 additions and 5 deletions
+1 -1
View File
@@ -387,7 +387,7 @@ Structure every response in this order:
## Session End
When planning is complete (PLAN-DRAFT created), tell the user:
When planning is complete (PLAN-DRAFT created), ALWAYS tell the user:
1. What was accomplished (planning document created)
2. File to attach in next session: `specs/PLAN-DRAFT-<timestamp>.md`
+22 -2
View File
@@ -396,6 +396,26 @@ If the user says "abort", "cancel", "start over", or similar:
- Flag blockers and spec issues clearly - do not silently skip or assume
- Your job is to BUILD according to spec, not to redesign
## Session Hint
## Learning Capture Protocol
If you discovered any project-specific insights, gotchas, or conventions during implementation that future AI agents should know, suggest running `/plan2code---init-update` to capture them in `AGENTS.md`.
At the END of each Implementation session, check:
### Auto-Capture Triggers
Proactively suggest updating `AGENTS.md` if ANY of these occurred:
- [ ] You discovered an undocumented build/test command
- [ ] You found a non-obvious dependency relationship
- [ ] You encountered a "gotcha" that cost > 5 minutes
- [ ] You made a workaround for a framework quirk
- [ ] You found existing patterns not mentioned in `AGENTS.md`
### Capture Format
📚 LEARNING DETECTED
I noticed something future agents should know:
- Category: [Commands / Architecture / Gotchas / Testing / Config]
- Learning: [concise description]
- Context: [why this matters]
Would you like me to update `AGENTS.md` with this? (yes/no)
If user says yes, generate the specific edit and apply it (don't require switching to init-update mode).
+22 -2
View File
@@ -436,6 +436,26 @@ If the user says "abort", "cancel", "start over", or similar:
- Archive specs to `specs--completed/<feature-name>/` - preserve folder name exactly
- This is validation and cleanup only - do NOT write implementation code
## Session Hint
## Learning Capture Protocol
If you discovered any project-specific insights, gotchas, or conventions during finalization that future AI agents should know, suggest running `/plan2code---init-update` to capture them in `AGENTS.md`.
At the END of Finalize session, check:
### Auto-Capture Triggers
Proactively suggest updating `AGENTS.md` if ANY of these occurred:
- [ ] You discovered an undocumented build/test command
- [ ] You found a non-obvious dependency relationship
- [ ] You encountered a "gotcha" that cost > 5 minutes
- [ ] You made a workaround for a framework quirk
- [ ] You found existing patterns not mentioned in `AGENTS.md`
### Capture Format
📚 LEARNING DETECTED
I noticed something future agents should know:
- Category: [Commands / Architecture / Gotchas / Testing / Config]
- Learning: [concise description]
- Context: [why this matters]
Would you like me to update `AGENTS.md` with this? (yes/no)
If user says yes, generate the specific edit and apply it (don't require switching to init-update mode).