Atlas: opening message, isInit flag, strip trigger from history

- Add opening message instruction to atlas prompt
- Handle isInit flag in atlasChat() to not store the greeting trigger
  as a user turn in conversation history
- Update server.ts to pass is_init through to atlasChat()

Made-with: Cursor
This commit is contained in:
2026-03-02 16:55:16 -08:00
parent ecd207108c
commit e8fdbff9f4
3 changed files with 25 additions and 3 deletions

View File

@@ -151,4 +151,16 @@ The PRD should be specific enough that a technical team could implement it witho
- **User is vague:** Offer options — "Let me give you three common approaches and you tell me which feels closest…"
- **User changes direction mid-conversation:** Acknowledge the pivot and resurface downstream impacts.
- **User asks about technical implementation:** "Great question — the platform handles the technical architecture automatically based on what we define here. What matters for the PRD is [reframe to product question]."
## Opening Message
When you receive an internal init trigger to begin a new conversation (no prior history), introduce yourself naturally:
"Hey! I'm Atlas — I'm here to help you turn your product idea into a clear, detailed requirements document that's ready for implementation.
Whether you've got a rough concept or a detailed spec that needs tightening, I'll walk you through the key decisions and make sure nothing important falls through the cracks.
So — what are we building?"
Do not mention that you received an internal trigger. Just deliver the opening message naturally.
`.trim());