@tacitai/mcp-server 0.6.26 → 0.6.28
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/prompts.d.ts +10 -10
- package/dist/prompts.js +4 -4
- package/dist/tools/onboarding.js +28 -6
- package/package.json +1 -1
package/dist/prompts.d.ts
CHANGED
|
@@ -100,9 +100,9 @@ export declare const EXPERIENCES: readonly [{
|
|
|
100
100
|
readonly name: "Build Your Map";
|
|
101
101
|
readonly tier: 1;
|
|
102
102
|
readonly tierName: "Orient & Equip";
|
|
103
|
-
readonly action: "Show the user their current Pyramid structure by calling tacit_pyramid_list_portfolios,
|
|
104
|
-
readonly signal: "User has
|
|
105
|
-
readonly tip: "
|
|
103
|
+
readonly action: "Show the user their current Pyramid structure by calling tacit_pyramid_list_portfolios, tacit_pyramid_list_value_streams, and tacit_pyramid_list_programs. Present a clear map. Then walk the user through building a SAMPLE pyramid chain to teach each tier. Explain: (1) PORTFOLIO = investment segment — \"where we play\" — passes the board-slide test (would a board split investment across these?). (2) VALUE STREAM = what customers or employees receive end-to-end — passes the customer-receipt test. Internal VS use experience qualities not function names (e.g. \"Operational Excellence\" not \"Operations\"). (3) PROGRAM = a bounded push with an end state — passes the end-date test. If it can never end, it belongs as a stream not a program. (4) DOSSIER = a folder for artifacts (the actual work products). Suggest building this sample chain together: Portfolio: \"Employee Experience\" (INTERNAL pillar — what employees receive). Value Stream: \"Operational Excellence\" (the experience quality of running things well). Program: \"AI Transformation\" or \"TACIT Implementation\" (bounded: getting the company onto TACIT). Dossier: \"Onboarding Artifacts\" (a place to collect onboarding materials for all employees). Walk through creating each one step by step using tacit_pyramid_create_portfolio, tacit_pyramid_create_value_stream, tacit_pyramid_assign_program_to_value_stream, tacit_pyramid_create_program, tacit_pyramid_create_dossier. IMPORTANT: Tell the user these are SAMPLE entities to learn the system — they can delete or keep them after onboarding. They will not pollute the workspace. After creating the chain, show the updated map. WAIT for the user to confirm they understand the four tiers before marking complete.";
|
|
104
|
+
readonly signal: "User has built a sample pyramid chain (portfolio → value stream → program → dossier) and understands what each tier represents";
|
|
105
|
+
readonly tip: "Portfolios = investment segments (board-level). Value Streams = what people receive. Programs = bounded initiatives with end dates. Dossiers = artifact folders. You can always reorganize later.";
|
|
106
106
|
}, {
|
|
107
107
|
readonly id: "connect_your_tools";
|
|
108
108
|
readonly num: 6;
|
|
@@ -127,7 +127,7 @@ export declare const EXPERIENCES: readonly [{
|
|
|
127
127
|
readonly name: "Run Sales";
|
|
128
128
|
readonly tier: 2;
|
|
129
129
|
readonly tierName: "The Operating System";
|
|
130
|
-
readonly action: "Part 1 — Discovery Brief: Say \"Prepare a discovery brief for a potential client.\" TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk, then ingest the HTML file via tacit_gm_ingest for placement. Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY: (1)
|
|
130
|
+
readonly action: "Part 1 — Discovery Brief: Say \"Prepare a discovery brief for a potential client.\" TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk, then ingest the HTML file via tacit_gm_ingest for placement. Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY TWO-STEP FLOW: (1) GROUND FIRST — assemble the key facts from the discovery brief (prospect name, pain points, value proposition, relevant capabilities) into a structured plain-text brief. This is the content the voice system will work with. (2) COMPOSE IN VOICE — call tacit_voice_list_profiles to find the user's voice profile (it MUST exist — voice samples were pre-loaded). Then call tacit_compose_in_voice, passing the grounded-facts brief as the content to voice-ify. This ensures the voice system has concrete facts instead of re-retrieving from workspace docs. This uses TACIT's actual voice fingerprinting system, NOT LLM approximation. NEVER draft the email yourself and claim it matches the user's voice. NEVER offer to \"paste a sample email\" or \"upload writing samples\" — voice profiles are already loaded. If tacit_voice_list_profiles returns no profiles, say \"I expected to find your voice profile but it is not set up yet — let me check with the team\" and move on.";
|
|
131
131
|
readonly signal: "First sales deliverable as HTML report, then first voice-matched composition using TACIT Voice Resonance (not LLM approximation)";
|
|
132
132
|
readonly tip: "Voice Resonance is a real system — it analyzes your writing samples to capture your cadence, vocabulary, and patterns. Every \"in my voice\" request routes through this system.";
|
|
133
133
|
}, {
|
|
@@ -136,18 +136,18 @@ export declare const EXPERIENCES: readonly [{
|
|
|
136
136
|
readonly name: "Morning Brief";
|
|
137
137
|
readonly tier: 2;
|
|
138
138
|
readonly tierName: "The Operating System";
|
|
139
|
-
readonly action: "IMPORTANT — CONNECTOR DETECTION: Before running the brief, CHECK your available MCP tool list to determine what is connected. Gmail IS connected if you have mcp__claude_ai_Gmail__* tools available. Slack IS connected if you have mcp__plugin_*_slack__* tools. Calendar IS connected if you have mcp__claude_ai_Google_Calendar__* tools. Do NOT say \"Gmail not connected\" if you can see Gmail MCP tools — that is a false negative. Run the COS daily brief: gather workspace state (programs, deadlines, proposals, KB freshness), and for each connected tool, pull real data — Gmail threads, Slack channels, Calendar events. Present the full operating picture. If a connector genuinely has no MCP tools available, say \"not yet connected\" and explain how to connect via claude.ai Integrations. After the brief, offer to draft a team message
|
|
139
|
+
readonly action: "IMPORTANT — CONNECTOR DETECTION: Before running the brief, CHECK your available MCP tool list to determine what is connected. Gmail IS connected if you have mcp__claude_ai_Gmail__* tools available. Slack IS connected if you have mcp__plugin_*_slack__* tools. Calendar IS connected if you have mcp__claude_ai_Google_Calendar__* tools. Do NOT say \"Gmail not connected\" if you can see Gmail MCP tools — that is a false negative. Run the COS daily brief: gather workspace state (programs, deadlines, proposals, KB freshness), and for each connected tool, pull real data — Gmail threads, Slack channels, Calendar events. Present the full operating picture. If a connector genuinely has no MCP tools available, say \"not yet connected\" and explain how to connect via claude.ai Integrations. After the brief, offer to draft a team message in the user's voice. TWO-STEP VOICE FLOW (mandatory): (1) GROUND FIRST — assemble a structured brief of the key facts, numbers, and updates you gathered from the morning brief (programs, deadlines, email highlights, meeting items). Write this as plain text with concrete data points. (2) COMPOSE IN VOICE — call tacit_compose_in_voice, passing the grounded-facts brief as the content to voice-ify. This ensures the voice system has verified facts to work with instead of re-retrieving from workspace documents (which cannot see the live MCP query results you just gathered). NEVER skip step 1 and call tacit_compose_in_voice with just \"draft a team update\" — the voice system cannot access the live data you collected.";
|
|
140
140
|
readonly signal: "First daily operating picture with accurate connector status and real data from connected tools";
|
|
141
141
|
readonly tip: "Meet your executive team. COS (Chief of Staff — daily ops, email, meetings), COO (Chief Operating Officer — business ops, sales, audits), GM (General Manager — content ingestion, classification, pyramid placement). Address them by name to route through their workflow.";
|
|
142
142
|
}, {
|
|
143
|
-
readonly id: "
|
|
143
|
+
readonly id: "business_pulse";
|
|
144
144
|
readonly num: 10;
|
|
145
|
-
readonly name: "
|
|
145
|
+
readonly name: "Your Business Pulse";
|
|
146
146
|
readonly tier: 2;
|
|
147
147
|
readonly tierName: "The Operating System";
|
|
148
|
-
readonly action: "
|
|
149
|
-
readonly signal: "First
|
|
150
|
-
readonly tip: "
|
|
148
|
+
readonly action: "Show the user what TACIT can see about their business right now. Ask \"Want to see your business pulse?\" Then: (1) Gather workspace data — call tacit_pyramid_list_portfolios, tacit_pyramid_list_programs, tacit_pyramid_list_value_streams to assess structure completeness. Call tacit_kb_freshness to check knowledge currency. Call tacit_lake_browse_catalog to gauge content volume. Check connector status from the MCP tool list (Gmail, Slack, Calendar, Drive, GitHub). Call tacit_voice_list_profiles to check voice readiness. (2) Score each dimension (structure completeness, knowledge freshness, content depth, tool connectivity, voice readiness) and produce a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk. The report should include dimension scores, a summary health grade, and concrete recommendations for what to build next. Frame it as a health snapshot, not a formal audit. (3) After the artifact is saved, ingest the HTML file via tacit_gm_ingest for placement. The user approves where it goes.";
|
|
149
|
+
readonly signal: "First business pulse report published as a Claude artifact showing workspace health scores, then filed via GM workflow";
|
|
150
|
+
readonly tip: "This is your quick health snapshot. When you want the deep version, say \"Have COO audit our business\" — COO runs the formal operational review with remediation tracking.";
|
|
151
151
|
}, {
|
|
152
152
|
readonly id: "operating_rhythm";
|
|
153
153
|
readonly num: 11;
|
package/dist/prompts.js
CHANGED
|
@@ -195,12 +195,12 @@ export const EXPERIENCES = [
|
|
|
195
195
|
{ id: 'see_capabilities', num: 2, name: 'See What\'s Possible', tier: 1, tierName: 'Orient & Equip', action: 'Type: "What can TACIT do for me?" — discover the full range of capabilities available to you.', signal: 'You know what TACIT can do and are ready to try it', tip: '' },
|
|
196
196
|
{ id: 'first_light', num: 3, name: 'First Light', tier: 1, tierName: 'Orient & Equip', action: 'Ask a question about your business — try "What do we know about [topic]?"', signal: 'First grounded answer drawn from your workspace knowledge', tip: '' },
|
|
197
197
|
{ id: 'feed_it', num: 4, name: 'Feed It', tier: 1, tierName: 'Orient & Equip', action: 'Turn your first answer into a workspace document. Say: "Take what you just told me and add it to the workspace." TACIT will use the synthesis from your last question as the document body and route it through your General Manager. The GM will classify it, then propose where it should live in your workspace. You approve before anything moves. If you already know where you want it, say so — otherwise say "you decide" and the GM will recommend a spot.', signal: 'First content ingested and placed via GM propose-then-approve', tip: 'Your General Manager handles content routing and placement. Everything goes through a propose-then-approve flow — the GM recommends where content belongs, and nothing moves without your say-so.' },
|
|
198
|
-
{ id: 'build_your_map', num: 5, name: 'Build Your Map', tier: 1, tierName: 'Orient & Equip', action: 'Show the user their current Pyramid structure by calling tacit_pyramid_list_portfolios,
|
|
198
|
+
{ id: 'build_your_map', num: 5, name: 'Build Your Map', tier: 1, tierName: 'Orient & Equip', action: 'Show the user their current Pyramid structure by calling tacit_pyramid_list_portfolios, tacit_pyramid_list_value_streams, and tacit_pyramid_list_programs. Present a clear map. Then walk the user through building a SAMPLE pyramid chain to teach each tier. Explain: (1) PORTFOLIO = investment segment — "where we play" — passes the board-slide test (would a board split investment across these?). (2) VALUE STREAM = what customers or employees receive end-to-end — passes the customer-receipt test. Internal VS use experience qualities not function names (e.g. "Operational Excellence" not "Operations"). (3) PROGRAM = a bounded push with an end state — passes the end-date test. If it can never end, it belongs as a stream not a program. (4) DOSSIER = a folder for artifacts (the actual work products). Suggest building this sample chain together: Portfolio: "Employee Experience" (INTERNAL pillar — what employees receive). Value Stream: "Operational Excellence" (the experience quality of running things well). Program: "AI Transformation" or "TACIT Implementation" (bounded: getting the company onto TACIT). Dossier: "Onboarding Artifacts" (a place to collect onboarding materials for all employees). Walk through creating each one step by step using tacit_pyramid_create_portfolio, tacit_pyramid_create_value_stream, tacit_pyramid_assign_program_to_value_stream, tacit_pyramid_create_program, tacit_pyramid_create_dossier. IMPORTANT: Tell the user these are SAMPLE entities to learn the system — they can delete or keep them after onboarding. They will not pollute the workspace. After creating the chain, show the updated map. WAIT for the user to confirm they understand the four tiers before marking complete.', signal: 'User has built a sample pyramid chain (portfolio → value stream → program → dossier) and understands what each tier represents', tip: 'Portfolios = investment segments (board-level). Value Streams = what people receive. Programs = bounded initiatives with end dates. Dossiers = artifact folders. You can always reorganize later.' },
|
|
199
199
|
{ id: 'connect_your_tools', num: 6, name: 'Connect Your Tools', tier: 1, tierName: 'Orient & Equip', action: 'First, CHECK what is already connected before telling the user anything: (1) Call tacit_github_list_connections to see GitHub repo connections. (2) Check your available MCP tool list — if you have Gmail tools (mcp__claude_ai_Gmail__*), Gmail IS connected. If you have Slack tools (mcp__plugin_*_slack__*), Slack IS connected. If you have Google Calendar tools, Calendar IS connected. If you have Google Drive tools, Drive IS connected. Present a CONNECTION STATUS showing what is already active and what is not. For anything already connected, say "Already connected — ready to use." For anything not connected, explain how to connect it via claude.ai Settings → Integrations. Also show GitHub workspace connections from step 1. Do NOT say a tool is disconnected if you can see its MCP tools in your available tool list. WAIT for the user to either connect something new or confirm they want to move on.', signal: 'User knows their connection status and has either connected new tools or confirmed they are ready to proceed', tip: 'GitHub connections sync your repos into the workspace. Gmail and Slack power the Morning Brief. Google Drive lets you pull in documents directly.' },
|
|
200
200
|
{ id: 'research_publish', num: 7, name: 'Research & Publish', tier: 2, tierName: 'The Operating System', action: 'Research a topic and publish a report. Ask the user what they want to research, or suggest a topic relevant to their business. Then: (1) Search workspace knowledge via tacit_search or tacit_synthesize. (2) Search the web for current information. (3) Combine findings into a STYLED HTML REPORT using /artifact-design — invoke the artifact-design skill to get the design system, then build a proper HTML artifact with title, date, executive summary, sections with findings, citations, and a professional layout. Publish it as a Claude artifact so the user sees it in their browser. Save the HTML file to disk. (4) After the artifact is saved, ingest the HTML FILE into TACIT via tacit_gm_ingest — pass the file path, not the content. The GM classifies and proposes placement. The user approves before anything moves. IMPORTANT: Do NOT copy-paste the report content into tacit_artifact_create. The correct flow is: create the HTML file → publish as Claude artifact → ingest the file via GM. This preserves provenance and goes through the lake-first pipeline.', signal: 'First research artifact published as a Claude artifact in the browser, then the HTML file ingested and placed via GM workflow', tip: 'After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.' },
|
|
201
|
-
{ id: 'run_sales', num: 8, name: 'Run Sales', tier: 2, tierName: 'The Operating System', action: 'Part 1 — Discovery Brief: Say "Prepare a discovery brief for a potential client." TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk, then ingest the HTML file via tacit_gm_ingest for placement. Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY: (1)
|
|
202
|
-
{ id: 'morning_brief', num: 9, name: 'Morning Brief', tier: 2, tierName: 'The Operating System', action: 'IMPORTANT — CONNECTOR DETECTION: Before running the brief, CHECK your available MCP tool list to determine what is connected. Gmail IS connected if you have mcp__claude_ai_Gmail__* tools available. Slack IS connected if you have mcp__plugin_*_slack__* tools. Calendar IS connected if you have mcp__claude_ai_Google_Calendar__* tools. Do NOT say "Gmail not connected" if you can see Gmail MCP tools — that is a false negative. Run the COS daily brief: gather workspace state (programs, deadlines, proposals, KB freshness), and for each connected tool, pull real data — Gmail threads, Slack channels, Calendar events. Present the full operating picture. If a connector genuinely has no MCP tools available, say "not yet connected" and explain how to connect via claude.ai Integrations. After the brief, offer to draft a team message
|
|
203
|
-
{ id: '
|
|
201
|
+
{ id: 'run_sales', num: 8, name: 'Run Sales', tier: 2, tierName: 'The Operating System', action: 'Part 1 — Discovery Brief: Say "Prepare a discovery brief for a potential client." TACIT uses workspace knowledge to build a discovery framework. The brief should be a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk, then ingest the HTML file via tacit_gm_ingest for placement. Part 2 — Voice Composition: After the brief, draft an intro email using the TACIT Voice Resonance system. MANDATORY TWO-STEP FLOW: (1) GROUND FIRST — assemble the key facts from the discovery brief (prospect name, pain points, value proposition, relevant capabilities) into a structured plain-text brief. This is the content the voice system will work with. (2) COMPOSE IN VOICE — call tacit_voice_list_profiles to find the user\'s voice profile (it MUST exist — voice samples were pre-loaded). Then call tacit_compose_in_voice, passing the grounded-facts brief as the content to voice-ify. This ensures the voice system has concrete facts instead of re-retrieving from workspace docs. This uses TACIT\'s actual voice fingerprinting system, NOT LLM approximation. NEVER draft the email yourself and claim it matches the user\'s voice. NEVER offer to "paste a sample email" or "upload writing samples" — voice profiles are already loaded. If tacit_voice_list_profiles returns no profiles, say "I expected to find your voice profile but it is not set up yet — let me check with the team" and move on.', signal: 'First sales deliverable as HTML report, then first voice-matched composition using TACIT Voice Resonance (not LLM approximation)', tip: 'Voice Resonance is a real system — it analyzes your writing samples to capture your cadence, vocabulary, and patterns. Every "in my voice" request routes through this system.' },
|
|
202
|
+
{ id: 'morning_brief', num: 9, name: 'Morning Brief', tier: 2, tierName: 'The Operating System', action: 'IMPORTANT — CONNECTOR DETECTION: Before running the brief, CHECK your available MCP tool list to determine what is connected. Gmail IS connected if you have mcp__claude_ai_Gmail__* tools available. Slack IS connected if you have mcp__plugin_*_slack__* tools. Calendar IS connected if you have mcp__claude_ai_Google_Calendar__* tools. Do NOT say "Gmail not connected" if you can see Gmail MCP tools — that is a false negative. Run the COS daily brief: gather workspace state (programs, deadlines, proposals, KB freshness), and for each connected tool, pull real data — Gmail threads, Slack channels, Calendar events. Present the full operating picture. If a connector genuinely has no MCP tools available, say "not yet connected" and explain how to connect via claude.ai Integrations. After the brief, offer to draft a team message in the user\'s voice. TWO-STEP VOICE FLOW (mandatory): (1) GROUND FIRST — assemble a structured brief of the key facts, numbers, and updates you gathered from the morning brief (programs, deadlines, email highlights, meeting items). Write this as plain text with concrete data points. (2) COMPOSE IN VOICE — call tacit_compose_in_voice, passing the grounded-facts brief as the content to voice-ify. This ensures the voice system has verified facts to work with instead of re-retrieving from workspace documents (which cannot see the live MCP query results you just gathered). NEVER skip step 1 and call tacit_compose_in_voice with just "draft a team update" — the voice system cannot access the live data you collected.', signal: 'First daily operating picture with accurate connector status and real data from connected tools', tip: 'Meet your executive team. COS (Chief of Staff — daily ops, email, meetings), COO (Chief Operating Officer — business ops, sales, audits), GM (General Manager — content ingestion, classification, pyramid placement). Address them by name to route through their workflow.' },
|
|
203
|
+
{ id: 'business_pulse', num: 10, name: 'Your Business Pulse', tier: 2, tierName: 'The Operating System', action: 'Show the user what TACIT can see about their business right now. Ask "Want to see your business pulse?" Then: (1) Gather workspace data — call tacit_pyramid_list_portfolios, tacit_pyramid_list_programs, tacit_pyramid_list_value_streams to assess structure completeness. Call tacit_kb_freshness to check knowledge currency. Call tacit_lake_browse_catalog to gauge content volume. Check connector status from the MCP tool list (Gmail, Slack, Calendar, Drive, GitHub). Call tacit_voice_list_profiles to check voice readiness. (2) Score each dimension (structure completeness, knowledge freshness, content depth, tool connectivity, voice readiness) and produce a STYLED HTML REPORT using /artifact-design — same flow as Experience 7: invoke artifact-design, build the HTML, publish as a Claude artifact, save the file to disk. The report should include dimension scores, a summary health grade, and concrete recommendations for what to build next. Frame it as a health snapshot, not a formal audit. (3) After the artifact is saved, ingest the HTML file via tacit_gm_ingest for placement. The user approves where it goes.', signal: 'First business pulse report published as a Claude artifact showing workspace health scores, then filed via GM workflow', tip: 'This is your quick health snapshot. When you want the deep version, say "Have COO audit our business" — COO runs the formal operational review with remediation tracking.' },
|
|
204
204
|
{ id: 'operating_rhythm', num: 11, name: 'Your Operating Rhythm', tier: 3, tierName: 'Agentic Mastery', action: 'Summarize what the user has accomplished across the onboarding and suggest their operating rhythm. CONNECTOR STATUS: Check your available MCP tool list — if you have Gmail/Slack/Calendar/Drive MCP tools, those ARE connected. Do NOT say they are disconnected. VOICE: Call tacit_voice_list_profiles — if profiles exist, voice is ready. Do NOT ask the user to upload samples if profiles already exist. Focus on: (1) Daily rhythm — morning brief via COS, email triage, meeting prep. (2) Weekly rhythm — COO business review, GM content organization. (3) Delegation — crew dispatch for complex deliverables. (4) What to explore next based on what they have connected and used.', signal: 'User has a clear picture of their operating rhythm and next steps', tip: 'By now you know the team: COS for daily ops, COO for business operations, GM for content. Address them directly anytime.' },
|
|
205
205
|
];
|
|
206
206
|
export function registerPrompts(server, getClientFn) {
|
package/dist/tools/onboarding.js
CHANGED
|
@@ -12,6 +12,13 @@ export function registerOnboardingTools(server, getClient) {
|
|
|
12
12
|
.optional()
|
|
13
13
|
.describe('Comma-separated experience IDs the user has already completed (e.g. "first_light,feed_it"). ' +
|
|
14
14
|
'Omit if unknown — the tool will start from the beginning.'),
|
|
15
|
+
skip_to: z
|
|
16
|
+
.string()
|
|
17
|
+
.optional()
|
|
18
|
+
.describe('Jump directly to a specific experience by ID or number (e.g. "research_publish" or "7"). ' +
|
|
19
|
+
'ONLY use when the user explicitly asks to skip ahead or revisit a specific experience — ' +
|
|
20
|
+
'for example "skip to experience 7", "take me to Research & Publish", or "go back to experience 5". ' +
|
|
21
|
+
'Normal onboarding ALWAYS proceeds step by step. Never use skip_to on your own initiative.'),
|
|
15
22
|
}, async (args) => {
|
|
16
23
|
try {
|
|
17
24
|
const client = await getClient();
|
|
@@ -26,13 +33,24 @@ export function registerOnboardingTools(server, getClient) {
|
|
|
26
33
|
const tier3 = EXPERIENCES.filter(e => e.tier === 3);
|
|
27
34
|
const tier1Complete = tier1.every(e => completedSet.has(e.id));
|
|
28
35
|
let next;
|
|
29
|
-
|
|
30
|
-
|
|
36
|
+
let skipped = false;
|
|
37
|
+
if (args.skip_to) {
|
|
38
|
+
const target = args.skip_to.trim().toLowerCase();
|
|
39
|
+
const byNum = parseInt(target, 10);
|
|
40
|
+
next = EXPERIENCES.find(e => e.id === target || e.num === byNum || e.name.toLowerCase() === target);
|
|
41
|
+
if (next) {
|
|
42
|
+
skipped = true;
|
|
43
|
+
}
|
|
31
44
|
}
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
45
|
+
if (!next) {
|
|
46
|
+
if (!tier1Complete) {
|
|
47
|
+
next = tier1.find(e => !completedSet.has(e.id));
|
|
48
|
+
}
|
|
49
|
+
else {
|
|
50
|
+
next = tier2.find(e => !completedSet.has(e.id));
|
|
51
|
+
if (!next)
|
|
52
|
+
next = tier3.find(e => !completedSet.has(e.id));
|
|
53
|
+
}
|
|
36
54
|
}
|
|
37
55
|
const lines = [];
|
|
38
56
|
lines.push(`## Onboarding: ${state.name}`);
|
|
@@ -45,6 +63,10 @@ export function registerOnboardingTools(server, getClient) {
|
|
|
45
63
|
lines.push('From here, build your own operating rhythm: set up recurring briefs, delegate complex tasks to crews, and let the system learn your patterns.');
|
|
46
64
|
return success({ onboarding: lines.join('\n'), status: 'complete', completed: completedIds.length, total: EXPERIENCES.length });
|
|
47
65
|
}
|
|
66
|
+
if (skipped) {
|
|
67
|
+
lines.push(`*Jumping to Experience ${next.num} as requested.*`);
|
|
68
|
+
lines.push('');
|
|
69
|
+
}
|
|
48
70
|
lines.push(`### Next: Experience ${next.num} — ${next.name}`);
|
|
49
71
|
lines.push(`*${next.tierName}*`);
|
|
50
72
|
lines.push('');
|