fraim 2.0.362-next.4 → 2.0.362

package/dist/registry/stubs/jobs/ai-employee/career/career-trajectory-planning.md

@@ -0,0 +1,41 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "career-trajectory-planning",
+  "displayName": "Career Path Plan"
+}
+---
+
+# FRAIM Job: career-trajectory-planning
+
+## Intent
+Research the job market and design a 3-horizon career path grounded in the user's positioning, open roles, salary benchmarks, and industry trends.
+
+## Outcome
+- A `Career Path Plan` DOCX at `docs/career/{slug}-trajectory-plan-{YYYY-MM-DD}.docx`, marked `PERSONAL - CAREER CONFIDENTIAL`
+- Canonical markdown source at `docs/career/{slug}-trajectory-plan-{YYYY-MM-DD}.md`, generated before the DOCX export
+- Salary benchmarks at P25/P50/P75 for the H1 target role, sourced and dated
+- A 3-horizon plan covering 0–6, 6–18, and 18–36 months, each with a target role and company profile
+- A company shortlist of 10-15 companies for Horizon 1 with a fit-alignment rationale for each
+- A gap bridge plan per horizon: skills to develop, experiences to collect, and a target completion date
+- All unverified or user-supplied inputs labeled explicitly
+
+## Steps
+1. Phase 1: `gather-positioning`
+2. Phase 2: `research-market`
+3. Phase 3: `build-trajectory`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "career-trajectory-planning" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/job-applications-and-networking.md

@@ -0,0 +1,40 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "job-applications-and-networking",
+  "displayName": "Job Applications & Networking"
+}
+---
+
+# FRAIM Job: job-applications-and-networking
+
+## Intent
+Operate a finite daily job-search campaign: find fresh roles, choose direct-apply versus referral paths, draft application and networking actions, update the tracker, and stop the recurring work when the campaign ends.
+
+## Outcome
+- A daily application and networking checkpoint sent to the user during the approved campaign window.
+- An approved, time-bounded recurring assignment for the active search campaign.
+- A maintained campaign tracker covering roles, referral paths, outreach drafts, application status, follow-up dates, and blockers.
+- Final campaign summary and recurring-assignment cleanup when the end date, offer, pause, cancellation, or pipeline goal is reached.
+
+## Steps
+1. Phase 1: `campaign-intake`
+2. Phase 2: `source-readiness`
+3. Phase 3: `initial-opportunity-research`
+4. Phase 4: `campaign-plan-recommendation`
+5. Phase 5: `campaign-plan-approval`
+6. Recurrence setup: `create-campaign-assignment`
+7. Recurring work: `daily-application-and-networking-check`
+8. Recurrence completion: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "job-applications-and-networking" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/job-search-strategy-and-application-plan.md

@@ -0,0 +1,41 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "job-search-strategy-and-application-plan",
+  "displayName": "Job Search Strategy & Application Plan"
+}
+---
+
+# FRAIM Job: job-search-strategy-and-application-plan
+
+## Intent
+Create a one-time job-search strategy and application plan for a user who already has enough career direction to pursue roles, without owning the recurring daily application and networking loop.
+
+## Outcome
+- A `Job Search Strategy & Application Plan` DOCX at `docs/career/{slug}-job-search-strategy-and-application-plan-{YYYY-MM-DD}.docx`
+- Canonical markdown source at `docs/career/{slug}-job-search-strategy-and-application-plan-{YYYY-MM-DD}.md`, generated before the DOCX export
+- Target role and company criteria, including geography, seniority, constraints, and compensation floor if known
+- Search positioning and role-fit rationale the user can apply consistently across applications
+- Pipeline stages, tracker fields, weekly application/referral goals, and follow-up rules
+- First-batch recommended roles or target companies with explicit apply / referral / skip decisions
+- Handoff guidance for `job-applications-and-networking` when the user wants daily operating support
+
+## Steps
+1. Phase 1: `search-strategy`
+2. Phase 2: `pipeline-design`
+3. Phase 3: `application-plan`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "job-search-strategy-and-application-plan" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/offer-negotiation.md

@@ -0,0 +1,42 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "offer-negotiation",
+  "displayName": "Offer Negotiation Plan"
+}
+---
+
+# FRAIM Job: offer-negotiation
+
+## Intent
+Evaluate an offer against market benchmarks, build a negotiation strategy, and produce a step-by-step script for landing the best possible title, compensation, and terms — with word-for-word language for every stage of the conversation.
+
+## Outcome
+- An `Offer Negotiation Plan` DOCX at `docs/career/{slug}-offer-negotiation-{YYYY-MM-DD}.docx`, marked `PERSONAL - CAREER CONFIDENTIAL` and `DRAFT - Review before use`
+- Canonical markdown source at `docs/career/{slug}-offer-negotiation-{YYYY-MM-DD}.md`, generated before the DOCX export
+- Salary benchmarks at P25/P50/P75, sourced and dated
+- Negotiation strategy: opening ask, walk-away floor, concessions, competing offer framing guidance
+- Word-for-word verbal response script and counter-offer email template
+- Pushback handling scripts for "this is our best offer" and "our bands are fixed"
+- Offer lifecycle tracker: received → countered → final outcome
+- Artifact headers: `PERSONAL — CAREER CONFIDENTIAL` and `DRAFT — Review before use in any conversation`
+
+## Steps
+1. Phase 1: `gather-offer-details`
+2. Phase 2: `research-benchmarks`
+3. Phase 3: `build-negotiation-strategy`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "offer-negotiation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/pitch-and-interview-prep.md

@@ -0,0 +1,43 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "pitch-and-interview-prep",
+  "displayName": "Job Interview Prep"
+}
+---
+
+# FRAIM Job: pitch-and-interview-prep
+
+## Intent
+Prepare the user to pitch themselves and ace interviews at a specific company and role, with tailored questions, answers, and a one-page pre-interview card they can review 30 minutes before the call.
+
+## Outcome
+- A `Job Interview Prep` DOCX at `docs/career/{slug}-pitch-and-interview-prep-{YYYY-MM-DD}.docx`
+- Canonical markdown source at `docs/career/{slug}-pitch-and-interview-prep-{YYYY-MM-DD}.md`, generated before the DOCX export
+- A 30-second pitch and 2-minute "tell me about yourself" tailored to the company's current priorities
+- >=10 predicted interview questions with suggested answers in STAR or problem-solution-impact format
+- Per-interviewer research section with likely focus areas (when names are provided or can be inferred)
+- Format-specific content: behavioral story bank, case framework (PM/strategy roles), or technical refresher (engineering roles)
+- A one-page pre-interview card
+- Practice tool recommendations: Yoodli for delivery, Big Interview for mock Q&A
+- All company facts sourced from public web and labeled
+
+## Steps
+1. Phase 1: `gather-interview-context`
+2. Phase 2: `research-company-and-interviewer`
+3. Phase 3: `build-prep-materials`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "pitch-and-interview-prep" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/public-profile-updates.md

@@ -0,0 +1,41 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "public-profile-updates",
+  "displayName": "LinkedIn Profile Refresh"
+}
+---
+
+# FRAIM Job: public-profile-updates
+
+## Intent
+Optimize LinkedIn, X, and social profiles for brand consistency and professional positioning; audit Facebook and Instagram for brand risks; produce copy-ready updates the user can apply immediately.
+
+## Outcome
+- A `LinkedIn Profile Refresh` DOCX at `docs/career/{slug}-public-profile-updates-{YYYY-MM-DD}.docx`
+- Canonical markdown source at `docs/career/{slug}-public-profile-updates-{YYYY-MM-DD}.md`, generated before the DOCX export
+- LinkedIn audit covering all 7 elements: custom URL, profile photo, background image, headline, About section, skills count, thought leader follows
+- Copy-ready alternatives for every flagged LinkedIn item
+- ≥10 relevant thought leader recommendations based on target industry and role
+- Brand risk audit for publicly visible Facebook and Instagram
+- Prioritized action list classifying each action as quick (<15 min) or substantial (>30 min)
+
+## Steps
+1. Phase 1: `gather-brand-context`
+2. Phase 2: `audit-profiles`
+3. Phase 3: `produce-action-list`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "public-profile-updates" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/resilience-planning.md

@@ -0,0 +1,38 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "resilience-planning",
+  "displayName": "Resilience Plan"
+}
+---
+
+# FRAIM Job: resilience-planning
+
+## Intent
+Help someone sustain themselves through hard stretches by building a resilience plan that spans their whole life — work, relationships, finances, health, and identity. Owned by the career persona (CAREEna); useful to any professional, not only founders.
+
+## Outcome
+- A `Resilience Plan` DOCX at `docs/career/resilience/{name}-resilience-plan-{YYYY-MM-DD}.docx`
+- Canonical markdown source at `docs/career/resilience/{name}-resilience-plan-{YYYY-MM-DD}.md`, generated before the DOCX export
+- Whole-life stressor inventory, coping-tactic plan, identity map, support-system map, key-relationship alignment plan, and check-in cadence
+
+## Steps
+1. Phase 1: `resilience-context-intake`
+2. Phase 2: `stressor-and-support-mapping`
+3. Phase 3: `tactics-and-identity-work`
+4. Phase 4: `key-relationship-alignment-plan`
+5. Phase 5: `resilience-plan-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "resilience-planning" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/resume-creation.md

@@ -0,0 +1,40 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "resume-creation",
+  "displayName": "Resume Rewrite"
+}
+---
+
+# FRAIM Job: resume-creation
+
+## Intent
+Build or optimize a resume from the user's qualifications, career strategy, LinkedIn profile, and GitHub, applying evidence-backed resume principles that maximize ATS clearance and human impact in the first 10 seconds.
+
+## Outcome
+- A `Resume Rewrite` artifact at `docs/career/resume-{slug}-{YYYY-MM-DD}.docx` for ATS-safe Word output, `docs/career/resume-{slug}-{YYYY-MM-DD}.html` for HTML/PDF output, or structured Canva-ready content blocks if that format is selected. The artifact includes impact-first bullet format, ATS-safe layout when applicable, consolidated Additional Experience section, and a role-targeted variant with relevant keywords if a job description is provided
+- Canonical source at `docs/career/resume-{slug}-{YYYY-MM-DD}.md` for Word/PDF paths, generated before the DOCX/HTML export or Canva-ready content blocks
+- **Reviewer-facing evidence:** Record the source-to-resume edit map summary, heading sanity result, ATS formatting result, and DOCX semantic formatting result before submission.
+- Every bullet rewritten to impact-first format ("Outcome X through action Y")
+- ATS-safe output: no columns, tables, or text boxes
+- Older roles consolidated into a polished dateless `Additional Experience` section
+- If a job description is provided: a role-targeted variant with relevant keywords surfaced
+
+## Steps
+1. Phase 1: `gather-career-history`
+2. Phase 2: `build-resume`
+3. Phase 3: `submit`
+4. Phase 4: `address-feedback`
+5. Phase 5: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "resume-creation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/crm-case-resolution.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: crm-case-resolution
+
+## Intent
+Resolve support cases end-to-end: receive case events, triage by priority and type, route to the right owner or queue, draft customer replies, and auto-resolve or escalate based on case complexity.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/customer-success/crm-case-resolution-{YYYY-MM-DD}.docx with sections: Cases Received, Triage Classification, Actions Taken, Auto-Resolved Cases, Escalations, and Errors
+- Updated case/conversation records (status, owner, AI-drafted replies or handoff notes)
+- Per-case action log with triage classification, actions taken, and resolution outcome
+
+## Steps
+1. Phase 1: `connect`
+2. Phase 2: `receive-case-event`
+3. Phase 3: `triage-and-route`
+4. Phase 4: `resolve-or-escalate`
+5. Phase 5: `produce-summary`
+6. Phase 6: `submit`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "crm-case-resolution" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/customer-health-review.md

@@ -0,0 +1,36 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: customer-health-review
+
+## Intent
+Surface at-risk customers, accounts, segments, and expansion opportunities so customer success teams can focus on the highest-impact actions - reducing churn and growing NRR.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at `docs/customer-success/customer-health-review-{YYYY-MM-DD}.pptx` containing portfolio health snapshot, risk distribution, revenue or segment impact where available, at-risk customers/accounts/segments, expansion opportunities, anomaly analysis, and CRM update status.
+- Source-mode support: `crm-account`, `segment`, or `mixed`.
+- CRM writeback for top-priority account or member records when the configured CRM adapter supports it.
+- No PII, payment details, raw case content, or raw conversation content in the artifact.
+
+## Steps
+1. Phase 1: `connect`
+2. Phase 2: `select-source-mode`
+3. Phase 3: `load-health-signals`
+4. Phase 4: `score-customers`
+5. Phase 5: `detect-anomalies`
+6. Phase 6: `generate-action-plan`
+7. Phase 7: `produce-summary`
+8. Phase 8: `submit`
+9. Phase 9: `address-feedback`
+10. Phase 10: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "customer-health-review" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/loyalty-program-management.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: loyalty-program-management
+
+## Intent
+Create and manage loyalty programs — designing program rules, enrolling member cohorts, and tracking balances — to drive retention and reward high-value customer behavior.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/customer-success/loyalty-program-{YYYY-MM-DD}.docx with sections: Program Details (name, goal, currency, earning rule, redemption type), Enrollment Results (cohort, member count, balance samples), and Loyalty Overview
+- New loyalty program created in the CRM (if requested), or existing program reviewed
+- Target member cohort enrolled with confirmed enrollment count and initial balances
+- Program summary with enrollment stats, tier distribution, and redemption options
+
+## Steps
+1. Phase 1: `connect`
+2. Phase 2: `review-programs`
+3. Phase 3: `design-program`
+4. Phase 4: `create-program`
+5. Phase 5: `enroll-members`
+6. Phase 6: `produce-summary`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "loyalty-program-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/support-case-resolution.md

@@ -0,0 +1,39 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: support-case-resolution
+
+## Intent
+Resolve support tickets end to end from the support system of record: claim or receive a ticket, choose the approved SOP playbook, invoke the correct fulfillment path, and write the final auditable result back to the support ticket.
+
+## Outcome
+- **Reviewable deliverable**: The support ticket updated in the configured support system with work notes, final state, FRAIM correlation id, selected playbook/action, validation result, fulfillment result, communication status, and backend audit references
+- Ticket intake normalized from the configured support system
+- Fulfillment action executed or clearly blocked with reason
+- Support record updated with status, work note, final disposition, and FRAIM correlation id
+- User communication dispatched or staged through the configured admin delivery path
+- Canonical evidence summarized in the support ticket and correlated to backend audit references
+- Phase-level capabilities available for support-system reads, decision prompt packaging, fulfillment actions, and support-system writeback
+
+## Steps
+1. Phase 1: `connect-support-system`
+2. Phase 2: `load-ticket`
+3. Phase 3: `classify-request`
+4. Phase 4: `validate-and-decide`
+5. Phase 5: `execute-fulfillment`
+6. Phase 6: `notify-user`
+7. Phase 7: `write-support-update`
+8. Phase 8: `submit`
+9. Phase 9: `address-feedback`
+10. Phase 10: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "support-case-resolution" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/support-playbook-evaluation.md

@@ -0,0 +1,37 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: support-playbook-evaluation
+
+## Intent
+Back-test approved support SOP playbooks against historical or golden support tickets, so an enterprise can see whether tickets would have been routed correctly before enabling live support automation.
+
+## Outcome
+- **Reviewable deliverable**: a .docx review copy generated from the final artifact via the author-docx skill at submission; this is the outcome delivered for review, with the .md below as the canonical agent-side record
+- Final artifact: A markdown report at `docs/support/playbook-evaluations/support-playbook-evaluation-{YYYY-MM-DD}.md` with dataset summary, playbooks tested, decision prompt/version, accuracy, confusion matrix, failure examples, automation eligibility, human-review rate, and recommended playbook improvements
+- **Spreadsheet deliverable**: A CSV/XLSX-ready row-level results file at `docs/support/playbook-evaluations/support-playbook-evaluation-{YYYY-MM-DD}.csv` with ticket id, expected decision, actual decision, pass/fail, confidence, failure reason, and recommendation columns
+- Dry-run playbook decision results for every evaluated ticket
+- Evidence that prohibited or ambiguous tickets route to human review
+- Clear recommendation on whether the playbook is ready for live HITL use, autonomous use, or further tuning
+
+## Steps
+1. Phase 1: `evaluation-scoping`
+2. Phase 2: `dataset-preparation`
+3. Phase 3: `decision-backtest`
+4. Phase 4: `analyze-results`
+5. Phase 5: `recommend-improvements`
+6. Phase 6: `produce-report`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "support-playbook-evaluation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/support-queue-management.md

@@ -0,0 +1,36 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: support-queue-management
+
+## Intent
+Monitor, triage, and resolve support conversations — classifying intent, drafting replies, and routing escalations — so the CS team clears the queue with AI assistance while keeping a human in the loop for critical cases.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/customer-success/support-queue-{YYYY-MM-DD}.docx with sections: Queue Summary (breakdown by priority and resolution path), Actions Taken (conversation IDs, intents, actions), Errors, and Annotations Written
+- All open conversations triaged and classified by priority
+- AI-drafted replies sent for L1 conversations after user confirmation
+- L2/L3 conversations routed to human queue with a handoff note
+- Conversation statuses updated in the CRM
+
+## Steps
+1. Phase 1: `connect`
+2. Phase 2: `load-queue`
+3. Phase 3: `triage-and-classify`
+4. Phase 4: `draft-replies`
+5. Phase 5: `send-and-update`
+6. Phase 6: `produce-summary`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "support-queue-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/support-sop-operationalization.md

@@ -0,0 +1,36 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: support-sop-operationalization
+
+## Intent
+Convert an enterprise Tier 1 support SOP into an approved support playbook that an AI support employee can use to choose the right ticket path, validate policy deterministically, and execute only the allowed adapters, scripts, messages, or escalation steps.
+
+## Outcome
+- **Reviewable deliverable**: A compact approved playbook JSON at `playbooks/support/{playbook-id}.json`, plus a human-readable SOP interpretation covering the source policy
+- Ticket decision guidance based on intent definitions, examples, negative examples, required facts, and disambiguation rules
+- Deterministic execution policy containing preconditions, prohibited actions, allowed actions, escalation rules, and evidence requirements
+- Adapter bindings for supported actions such as ServiceNow ticket updates and M365 password reset
+- Test fixtures that prove playbook decisions, missing-fact handling, escalation, and allowed-action selection
+
+## Steps
+1. Phase 1: `ingest-sop`
+2. Phase 2: `deconstruct-sop`
+3. Phase 3: `author-playbook`
+4. Phase 4: `bind-adapters`
+5. Phase 5: `define-validation`
+6. Phase 6: `produce-review-package`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "support-sop-operationalization" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/support-system-operationalization.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: support-system-operationalization
+
+## Intent
+Operationalize the support system once so that support requests can thereafter be resolved deterministically and securely. Connect the support ticket system and every other system support must act on, each through a least-privilege access script provided by the team that owns it, and wire them into the support configuration so downstream support jobs run without further setup.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/support/operationalization/support-operationalization-{YYYY-MM-DD}.docx with sections: Configured Systems, Verification Results, Unconfigured Gaps, Unblocked Jobs, and Remaining Steps
+- `fraim/config.json` wired with one name-to-script pair per system (the ticket system, plus each downstream system support acts on)
+- Every configured access script verified against its least-privilege self-test before downstream support jobs rely on it
+
+## Steps
+1. Phase 1: `discover-systems`
+2. Phase 2: `explain-access-script-contract`
+3. Phase 3: `author-access-scripts`
+4. Phase 4: `wire-config`
+5. Phase 5: `verify-access-scripts`
+6. Phase 6: `produce-operationalization-report`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "support-system-operationalization" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.