/**
 * Onboarding-Mode System Prompt v0
 *
 * Loaded by the orchestrator when it enters `onboarding` mode on a fresh
 * Crewly OSS install (no chat history detected). Drives a 5-phase
 * conversation that ends with a materialized AI team, all without Steve
 * (or any operator) on the call.
 *
 * Goal-anchor (Steve's own words, 2026-05-03):
 *   "新的 crewly oss 启动后 如果还没有说过话 就会自动启动这个 onboarding，
 *    然后 orc 就会开始进入 onboarding 模式与用户说话"
 *   = Fresh OSS install → no chat history → auto-launch onboarding →
 *     orc itself enters "onboarding mode" and converses with the user.
 *
 * G/O/E:
 *   - Goal:       Customer onboards fully self-service.
 *   - Outcome:    Fresh OSS install → ≤5 min orc-conversation → user has
 *                 a configured, working AI team.
 *   - Evaluation: Steve or SteamFun runs through it as a real customer,
 *                 no Steve intervention, AI team works.
 *
 * The prompt is intentionally exhaustive: orc must produce *concrete*,
 * *capability-grounded* replies rather than vague AI-marketing speak.
 * That specificity is the differentiator and is enforced by the
 * "feasibility judgment" phase in the body of the prompt.
 *
 * v0 capability list is hardcoded inside the prompt so Mon-EOD demos work
 * without RAG. When Mia's spec v3 + doc 69 land (Wed–Fri), the hardcoded
 * list will be swapped for runtime-injected RAG snippets — the export
 * surface (a single string constant) does not change.
 *
 * @module services/orchestrator/prompts/onboarding-mode.prompt
 */
/**
 * Phase markers — also used by the prompt test to assert structural
 * integrity. Keep in sync with the body of the prompt below.
 */
export declare const ONBOARDING_PHASE_MARKERS: readonly ["PHASE 1 — OPEN", "PHASE 2 — BUSINESS DISCOVERY", "PHASE 3 — FEASIBILITY JUDGMENT", "PHASE 4 — TEAM RECOMMENDATION", "PHASE 5 — CONFIRM + MATERIALIZE"];
/**
 * Capability-grounding language markers. The prompt test asserts these
 * appear so future edits cannot silently strip the differentiator.
 */
export declare const ONBOARDING_CAPABILITY_MARKERS: readonly ["capability-grounded", "no vague claims", "cite the underlying skill"];
/**
 * Few-shot anchor transcript — embedded in the prompt body. The prompt
 * test asserts this anchor stays present (regression guard).
 */
export declare const ONBOARDING_FEW_SHOT_ANCHOR_MARKER = "FEW-SHOT ANCHOR \u2014 TONE + SPECIFICITY BAR";
/**
 * The system prompt orc loads when its mode is `'onboarding'`.
 *
 * Imported by:
 *   - The orchestrator runtime / state machine (Leo) when it detects a
 *     cold-start and swaps to `onboarding` mode.
 *   - The prompt test (this directory) for structural assertions.
 */
export declare const ONBOARDING_MODE_SYSTEM_PROMPT: string;
/**
 * Convenience: validate a candidate prompt body contains every required
 * structural marker. The prompt test uses this; downstream callers may
 * use it as a runtime guard if they ever swap the prompt at runtime.
 *
 * @param prompt - The prompt string to inspect.
 * @returns Array of marker strings that are MISSING. Empty array → ok.
 */
export declare function findMissingPromptMarkers(prompt: string): string[];
//# sourceMappingURL=onboarding-mode.prompt.d.ts.map