feat: Enhance learning session guidelines to prioritize durable understanding and high-leverage questioning
This commit is contained in:
@@ -47,6 +47,8 @@ These are also loaded through `opencode.json`.
|
||||
- If the user asks for the latest/last/recent Mattermost message, the latest message from Jeff/current manager, or what someone just said, synchronize Mattermost first instead of relying on existing inbox context.
|
||||
- If automatic refresh is uncertain, use the explicit latest-message flow: run the Mattermost sync command, then answer from the refreshed inbox only.
|
||||
- For learning-style questions, answer from known context and verified facts only; label unknowns, assumptions, and inferences instead of inventing missing details.
|
||||
- For learning sessions, prioritize durable architecture, process, ownership, debugging strategy, release mechanics, domain concepts, and decision rules over transient ticket status.
|
||||
- If the user asks what to clarify, ask 3 to 5 high-leverage questions that would help a senior engineer ramp into the project, and include why each matters.
|
||||
- Ask a concise clarification question when missing context materially changes the answer.
|
||||
- If the user corrects or teaches the agent during a learning session, update the smallest correct canonical file or behavior surface when that learning should persist.
|
||||
- For any meaningful prompt, decide whether the interaction introduces or corrects project memory.
|
||||
|
||||
Reference in New Issue
Block a user