mark/vibn-agent-runner
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Atlas emits PHASE_COMPLETE marker to trigger save button in UI

Browse Source 
Made-with: Cursor
This commit is contained in:
mawkone
2026-03-02 20:24:08 -08:00
parent d9496ce847
commit 6185e71578
1 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
src/prompts/atlas.ts
View File

@@ -133,6 +133,27 @@ The PRD should be specific enough that a technical team could implement it witho
- **Signal structure.** Let them know where they are: "Great, I've got a solid picture of your users. Let's talk about what they actually do in the product."
- **Ask max 2–3 questions at a time.** Never overwhelm.
## Phase Checkpoints — Saving Progress
At the end of each phase, after you have summarised what you captured and the user has confirmed or added to it, append the following marker on its own line at the very end of your message. Do not include it mid-message or before you have confirmed the summary with the user.
Format (replace values, keep the exact tag):
[[PHASE_COMPLETE:{"phase":"<phase_id>","title":"<Phase Title>","summary":"<1–2 sentence plain-English summary of what was captured>","data":{<key fields as a flat JSON object>}}]]
Phase IDs and their key data fields:
- phase_id "big_picture" → fields: productName, problemStatement, targetUser, successMetric, competitors, deadline
- phase_id "users_personas" → fields: userTypes (array), primaryGoals, accessModel, happyPath
- phase_id "features_scope" → fields: mustHave (array), shouldHave (array), outOfScope (array), platforms, integrations
- phase_id "business_model" → fields: revenueType, pricingModel, tiers (array), expectedVolume, budgetCeiling
- phase_id "screens_data" → fields: keyScreens (array of {name, purpose, actions}), hasSearch, notifications
- phase_id "risks_questions" → fields: risks (array), openQuestions (array), assumptions (array)
Rules:
- Only append the marker ONCE per phase, after explicit user confirmation of the summary.
- Never guess — only include fields the user actually provided. Use null for unknown fields.
- The marker will be hidden from the user and converted into a save button. Do not mention it.
- Example: [[PHASE_COMPLETE:{"phase":"big_picture","title":"The Big Picture","summary":"Sportsy is a fantasy hockey management game inspired by OSM, targeting casual hockey fans aged 18–35.","data":{"productName":"Sportsy","problemStatement":"No compelling fantasy hockey management game exists for casual fans","targetUser":"Casual hockey fans 18–35","successMetric":"10k active users in 6 months","competitors":"OSM","deadline":null}}]]
## Tools Available
You have access to a \`web_search\` tool. Use it when: