Restructure Dex system based on new role or preferences
Re-run the onboarding flow to restructure your Dex system. Useful when:
When the user types /reset, execute the following:
Say: "Let's reset your Dex setup. I'll walk you through the same questions as initial setup, then reorganize your structure. Your existing content will be preserved - I'll move files to match the new structure, not delete them."
Before asking questions, check and display:
Say: "Here's your current setup: [summary]. Want to change it?"
If user wants to change role, present the numbered role list:
**Core Functions**
1. Product Manager
2. Sales / Account Executive
3. Marketing
4. Engineering
5. Design
**Customer-Facing**
6. Customer Success
7. Solutions Engineering
**Operations**
8. Product Operations
9. RevOps / BizOps
10. Data / Analytics
**Support Functions**
11. Finance
12. People (HR)
13. Legal
14. IT Support
**Leadership**
15. Founder
**C-Suite**
16. CEO
17. CFO
18. COO
19. CMO
20. CRO
21. CTO
22. CPO
23. CIO
24. CISO
25. CHRO / Chief People Officer
26. CLO / General Counsel
27. CCO (Chief Customer Officer)
**Independent / Advisory**
28. Fractional CPO
29. Consultant
30. Coach
Type a number, or describe your role:
1. 1-100 people (startup/small)
2. 100-1,000 people (scaling)
3. 1,000-10,000 people (enterprise)
4. 10,000+ people (large enterprise)
Ask: "What are your 2-3 main priorities right now?"
Before making changes, show the user:
Ask: "Does this look right? Type 'yes' to proceed or suggest changes."
00-Inbox/ for user to sortSystem/user-profile.yaml with new role and preferencesAfter completion, show:
NEVER delete user content during reset. Follow these rules:
Pipeline/ → Opportunities/), move content00-Inbox/To_Sort/ with a note about original locationPeople/ folder structure00-Inbox/Meetings/ contentGovernance/ folderRelationships/ with more stakeholder categoriesPipeline/ → Portfolio/Health/, Renewals/ foldersTeam/ folder for 1:1s, hiring04-Projects/ and Systems/If something goes wrong:
/reset as many times as neededSystem/reset_log.mdUpdate System/usage_log.md to mark vault reset as used.
Analytics (Silent):
Call track_event with event_name vault_reset and properties:
This only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".