fraim 2.0.362-next.4 → 2.0.362

package/dist/registry/stubs/jobs/ai-employee/finance/investor-pitch-preparation.md

@@ -0,0 +1,40 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: investor-pitch-preparation
+
+## Intent
+Transform confirmed business strategy and traction data into a draft investor pitch package that separates verified facts, assumptions, projections, and reviewer gaps.
+
+This job builds upon business validation findings to create investment-ready presentations for VCs, board members, and external stakeholders.
+
+## Outcome
+- **Reviewable deliverable**: A draft .pptx presentation at `docs/fundraising/pitch-package-{YYYY-MM-DD}.pptx`.
+- **Source package**: A markdown source at `docs/fundraising/pitch-package-{YYYY-MM-DD}.md` with cited facts, assumptions, projections, gaps, and review notes.
+- **Founder review packet**: Investor questions, objection handling, and external-send approval status.
+
+## Steps
+1. Phase 1: `scoping`
+2. Phase 2: `strategy-discovery`
+3. Phase 3: `comprehensive-market-analysis`
+4. Phase 4: `pitch-narrative-synthesis`
+5. Phase 5: `strategy-recovery-mentoring` (Conditional)
+6. Phase 6: `deck-outline-creation`
+7. Phase 7: `financial-scaffold-creation`
+8. Phase 8: `investor-qa-preparation`
+9. Phase 9: `pitch-package-assembly`
+10. Phase 10: `pitch-submission`
+11. Phase 11: `address-feedback`
+12. Phase 12: `practice-audio-offer` (Optional — consent-gated)
+13. Phase 13: `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: "investor-pitch-preparation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/invoice-generation.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: invoice-generation
+
+## Intent
+To generate professional PDF invoices from minimal input (customer name, user count) by prioritizing automated pricing discovery from project SOWs, followed by high-precision drafting and branded output generation.
+
+## Outcome
+- Final artifact: A professional PDF invoice at `docs/invoicing/{customer-slug}-{date}.pdf`.
+- **Automated Discovery**: Pricing and terms extracted directly from verified project SOWs.
+- **Precision Drafting**: High-fidelity invoice data with 100% accurate financial terms.
+
+## Steps
+1. Phase 1: `gather-input`
+2. Phase 2: `discover-pricing`
+3. Phase 3: `discover-branding`
+4. Phase 4: `generate-invoice-html`
+5. Phase 5: `validate-invoice-completeness`
+6. Phase 6: `convert-to-pdf`
+7. Phase 7: `cleanup-and-confirm`
+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: "invoice-generation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/monthly-close-review.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: monthly-close-review
+
+## Intent
+Run the monthly financial close cycle - collect actuals, compute budget variances, write management commentary, and distribute the board package - in 2 hours instead of a full day.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/finance/monthly-close-review-{YYYY-MM-DD}.pptx containing budget variance analysis table, top 5 material variances with root cause commentary, summary KPIs (gross margin, EBITDA actual vs budget), and executive summary with cash runway.
+- **Variance Analysis**: Every major P&L line analyzed with favorable/unfavorable/material classification.
+- **Management Commentary**: Top 5 variances explained with root cause and forward-looking implication.
+- **Board Package**: Executive summary formatted for board distribution.
+
+## Steps
+1. Phase 1: `actuals-collection`
+2. Phase 2: `variance-analysis`
+3. Phase 3: `commentary-authoring`
+4. Phase 4: `distribution`
+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: "monthly-close-review" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/review-funding-preparation.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: review-funding-preparation
+
+## Intent
+Provide a critical, cold-eyed audit of any existing funding preparation (Pitch Deck, Campaign, Grant) to identify weak points, logical fallacies, and readiness gaps.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/fundraising/readiness-audit-{YYYY-MM-DD}.pptx with readiness audit report including strengths, weaknesses, stop/go recommendations, stress-test results, and actionable gap list.
+- **Readiness Audit Report**: A breakdown of Strengths, Weaknesses, and "Stop/Go" recommendations.
+- **Stress-Test Results**: Identification of "The Question that kills the deal."
+- **Actionable Gap List**: Priority list of fixes required before submission.
+
+## Steps
+1. Phase 1: `scoping`
+2. Phase 2: `package-audit`
+3. Phase 3: `benchmark-analysis`
+4. Phase 4: `readiness-score-delivery`
+5. Phase 5: `submit`
+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: "review-funding-preparation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/tax-strategy-planning.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: tax-strategy-planning
+
+## Intent
+Provide a structured tax planning framework that identifies the entity structure, available deductions, and quarterly estimate obligations - to ensure founders make informed tax decisions before deadlines, not after.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/finance/tax-strategy-planning-{YYYY-MM-DD}.docx with entity structure analysis, deduction inventory with IRC basis and documentation requirements, quarterly estimated tax payment schedule with due dates, CPA handoff checklist, and required documentation list.
+- **Entity Analysis**: Assessment of current entity type and any restructuring considerations.
+- **Deduction Inventory**: Documented list of applicable deductions with supporting rationale.
+- **Quarterly Estimates**: Calculated estimated tax payments for upcoming quarters.
+
+## Steps
+1. Phase 1: `entity-structure-review`
+2. Phase 2: `deduction-inventory`
+3. Phase 3: `quarterly-estimate-calc`
+4. Phase 4: `planning-doc`
+5. Phase 5: `tax-strategy-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: "tax-strategy-planning" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/adhoc-prompt.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "adhoc-prompt",
+  "displayName": "Ad-hoc"
+}
+---
+
+# FRAIM Job: adhoc-prompt
+
+## Intent
+Run any task that does not map to a structured FRAIM catalog job. Use as a fallback when no catalog job matches the user's request — not as a substitute for a structured job when one exists. Agents must not select this job speculatively; it is offered only when no catalog match is found.
+
+## Outcome
+The task described in the manager's instructions is complete, with a lightweight record of what happened and a recommendation on whether to formalize the task as a recurring FRAIM job.
+
+## Steps
+1. Phase 1: `run`
+2. Phase 2: `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: "adhoc-prompt" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/contribute-to-fraim.md

@@ -0,0 +1,30 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: contribute-to-fraim
+
+## Intent
+Allow users to contribute their custom Jobs, Skills, Rules, and Values back to the core FRAIM project. This job asks the user which specific capabilities they want to share, packages them, and files a contribution issue in the FRAIM repository.
+
+## Outcome
+- Final artifact: A detailed contribution issue filed in the FRAIM repository with packaged artifacts.
+- **Improved Ecosystem**: The user's proven capabilities are shared with the broader FRAIM community.
+
+## Steps
+1. Phase 1: `gather-contribution-intent`
+2. Phase 2: `discover-contribution-artifacts`
+3. Phase 3: `confirm-contribution-package`
+4. Phase 4: `file-contribution-issue`
+5. Phase 5: `completion`
+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: "contribute-to-fraim" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/file-fraim-issue.md

@@ -0,0 +1,29 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: file-fraim-issue
+
+## Intent
+File a user-readable bug report in the FRAIM repository. The agent elicits the user's own words about impact and symptoms before harvesting any technical context, then structures the issue so the user experience comes first and the technical detail comes last.
+
+## Outcome
+- Final artifact: A new GitHub issue filed in the FRAIM repository.
+- **User-Readable Report**: The issue opens with user impact and observable symptoms, followed by plain-language repro steps, with technical context appended last and omitted when nothing is found.
+
+## Steps
+1. Phase 1: `gather-issue-details`
+2. Phase 2: `confirm-issue-details`
+3. Phase 3: `file-issue`
+4. Phase 4: `completion`
+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: "file-fraim-issue" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/organizational-learning-synthesis.md

@@ -0,0 +1,40 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: organizational-learning-synthesis
+
+## Intent
+Synthesize cross-user experience into a concrete improvement plan for scrum master review: supported organizational lessons, context corrections and changes to the capabilities that own the work. Apply only approved revisions and preserve their evidence and history.
+
+## Outcome
+- Successful subset completion journals and archives each successfully processed typed raw learning into its source home's configured raw-input archive and each successfully processed typed reflection into its source home's configured reflection archive, setting the successful processing date in `synthesized` while preserving body, event references and immutable `sourceId`, including fully processed sources yielding rejected or no proposed changes. Unreadable, unresolved and dependency-blocked inputs remain pending with attributable deferred reasons and recovery state; cycle completion does not claim complete corpus coverage. The newly written cycle retrospective stays unsynthesized. Rejected proposals retain their full content, exact revision and target, source attribution, reviewer, reason and optional revisit condition in `<run-content-root>/learnings/<reviewer>-rejected-proposals.md`.
+- **Reviewable action plan** with artifact ownership, draft changes, scope, reachability and verification. All learning and capability action revisions use the originating owner’s single run journal. Active guidance remains unchanged before approval; new learning entries use domain filenames (flat for explicit global), and updates receive full domain and concision review, with corrections separately approved against exact source/destination refs.
+- **Demotion candidates flagged**: existing L2 entries where only one user's signal remains active.
+- **Exact approved changes**: write only reviewed targets and revisions after scrum master approval.
+
+Capture corrective coaching immediately with the shared typed raw-input skill; preserve original event references. Newly captured or unread sources and the new cycle reflection remain outside the frozen analyzed set. Record action revisions, exact decisions, reasons and source reconciliations in its run journal. The rejected-proposals file retains declined changes, and source lifecycle updates close only the verified completed subset and retain deferred inputs/actions for recovery.
+
+## Steps
+1. Phase 1: `gather-l1`
+2. Phase 2: `analyze`
+3. Phase 3: `diagnose`
+4. Phase 4: `prioritize`
+5. Phase 5: `plan-actions`
+6. Phase 6: `review`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `apply`
+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: "organizational-learning-synthesis" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/praise-fraim.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: praise-fraim
+
+## Intent
+Turn a genuine positive FRAIM outcome into authentic external praise, recommend the best channels for it, draft channel-appropriate copy, and stage the chosen testimonial or post for final user review before anything is submitted.
+
+## Outcome
+- A reviewed praise pack at `docs/evangelism/praise-fraim/praise-fraim-{YYYY-MM-DD}.md` containing source signals, recommended channels, approved copy, and publish/stage status.
+- One or more channel-ready praise drafts for destinations such as a website testimonial, LinkedIn, X, or Reddit.
+- If the user chooses to publish now, the browser is driven to the final review point and the approved copy is staged on the user's behalf before submission.
+
+## Steps
+1. Phase 1: `context-and-signal-load`
+2. Phase 2: `channel-selection`
+3. Phase 3: `draft-praise-pack`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `publish-or-stage`
+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: "praise-fraim" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/share-with-others.md

@@ -0,0 +1,30 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: share-with-others
+
+## Intent
+Move any manager-owned artifact — learnings, personalized employees, jobs, skills, or rules — from one scope level to another so it reaches the right audience.
+
+## Outcome
+- Every approved artifact has exactly one live copy at the destination level. Nothing is duplicated; the source copy is removed after a verified destination write and an archive of the source copy is created.
+- Artifacts moved to a shared level have every manager-specific value replaced or parameterised before the file is written.
+- Every move is captured in the run evidence: artifact name, type, source, destination, archive path, any de-personalised values, and the pull request URL when the destination is repo-backed.
+- Any backend touched by a move is published, and the manager is told what still has to merge before the change is live.
+
+## Steps
+1. Use `inventory-owned-artifacts` to collect all artifacts at the manager, project, and org levels for all types. Pass `types: ['learnings', 'jobs', 'skills', 'rules', 'templates', 'employees']`.
+2. Present counts per level per type. If a level has nothing for a given type, say so. Flag any type where the same artifact id or learning family exists at more than one level.
+3. Flag any custom employee whose roster jobs live at a different level — those are candidates for a coordinated move.
+4. Report the configured backend for the manager level and the org level, taken from `~/.fraim/config.json`. The manager needs to know before selecting whether a destination will produce a pull request, a cloud publish, or a synced-folder write. If a level has no backend configured, say so now rather than failing at apply time.
+
+---
+
+> [!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: "share-with-others" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/sleep-on-learnings.md

@@ -0,0 +1,41 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: sleep-on-learnings
+
+## Intent
+Learn from past successes and mistakes so useful choices recur and avoidable mistakes do not.
+
+## Outcome
+- Successful subset completion journals and archives each successfully processed typed raw learning into its source home's configured raw-input archive and each successfully processed typed reflection into its source home's configured reflection archive, setting the successful processing date in `synthesized` while preserving body, event references and immutable `sourceId`, including fully processed sources yielding rejected or no proposed changes. Unreadable, unresolved and dependency-blocked inputs remain pending with attributable deferred reasons and recovery state; cycle completion does not claim complete corpus coverage. The newly written cycle retrospective stays unsynthesized. Rejected proposals retain their full content, exact revision and target, source attribution, reviewer, reason and optional revisit condition in `<run-content-root>/learnings/<reviewer>-rejected-proposals.md`.
+- The user can review one concrete action plan: concise lessons, context corrections and improvements to the capabilities that own the work.
+- Approved changes improve future work at the intended scope, with their history intact.
+- Existing applicable learnings receive owner-bound assessments of independent source incidents, with successful application, reported help, relevant misses and uncertainty kept distinct. Persisted assessments retain event dates and provenance; historical totals remain separate when overlap is unknown.
+- Conflicts, rejected ideas and optional revisit conditions remain recorded in evidence without repeatedly asking the same questions.
+
+Capture corrective coaching immediately with the shared typed raw-input skill; preserve original event references. Newly captured or unread sources and the new cycle reflection remain outside the frozen analyzed set. Record action revisions, exact decisions, reasons and source reconciliations in its run journal. The rejected-proposals file retains declined changes, and source lifecycle updates close only the verified completed subset and retain deferred inputs/actions for recovery.
+
+## Steps
+1. Phase 1: `gather-signals`
+2. Phase 2: `analyze`
+3. Phase 3: `diagnose`
+4. Phase 4: `prioritize`
+5. Phase 5: `plan-actions`
+6. Phase 6: `review-pending`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `apply`
+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: "sleep-on-learnings" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/troubleshoot-fraim.md

@@ -0,0 +1,29 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: troubleshoot-fraim
+
+## Intent
+Resolve a FRAIM issue the user is experiencing — connectivity, sync, Hub startup, agent CLI paths, MCP configuration, or job execution — and leave FRAIM in a working state or produce a clear bug report if a code fix is required.
+
+## Outcome
+- FRAIM is working again and the user can continue their work, or
+- The user has a concrete next step (re-sync, restart, file a bug), or
+- A filed GitHub issue with full diagnostic detail if the issue requires a code fix.
+
+## Steps
+1. Phase 1: `collect-symptom`
+2. Phase 2: `diagnose`
+3. Phase 3: `repair-or-escalate`
+4. Phase 4: `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: "troubleshoot-fraim" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/fraim/video-demo-to-sop.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: video-demo-to-sop
+
+## Intent
+Turn a video recording or transcript of a workflow demo into a Standard Operating Procedure (SOP) that documents the workflow clearly enough for `evolve-employee` to generate a FRAIM job file from it.
+
+## Outcome
+- **New SOP file**: `docs/sops/<workflow-name>.docx` — a Word document capturing the workflow's trigger, steps, and expected outcomes, confirmed by the demo author.
+- **evolve-employee invoked**: `evolve-employee` is called with the SOP docx path as input to generate the FRAIM job file.
+- **Author-confirmed**: Intent and Outcome are confirmed by the demo author before the file is written.
+- **Grounded**: every step in the SOP is traceable to something shown or narrated in the recording.
+- **Next step identified**: the SOP is ready to pass to `evolve-employee` to generate a FRAIM job file.
+
+## Steps
+1. Phase 1: `intake-recording`
+2. Phase 2: `correlate-content`
+3. Phase 3: `infer-job-structure`
+4. Phase 4: `gap-fill-review`
+5. Phase 5: `write-sop`
+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: "video-demo-to-sop" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/go-to-market/ad-performance-analysis.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: ad-performance-analysis
+
+## Intent
+Analyze cross-channel ad performance to identify what's working, what's wasting budget, and what to do next — producing a prioritized optimization plan grounded in attribution data, not platform-reported vanity metrics.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/marketing/paid/{date}-ad-performance-analysis.pptx with Channel Attribution tables, Creative Performance rankings, and Optimization Plan with expected impact projections.
+- **Channel Attribution**: Performance by channel with attributed conversions and true CPA (not last-click).
+- **Creative Performance**: Best and worst performing creative assets with statistical significance note.
+- **Optimization Plan**: Prioritized list of budget shifts, pauses, and tests with expected impact.
+
+## Steps
+1. Phase 1: `data-collection`
+2. Phase 2: `attribution`
+3. Phase 3: `optimization-recommendation`
+4. Phase 4: `ad-performance-submission`
+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: "ad-performance-analysis" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/go-to-market/aeo-strategy.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: aeo-strategy
+
+## Intent
+Help buyers find accurate answers about a business through answer engines by identifying valuable questions, evidence gaps, and measurable visibility opportunities.
+
+## Outcome
+- A reviewable AEO strategy brief: buyer question/intent map, observed answer and citation baseline, verified technical/content/authority gaps, and prioritized roadmap with owners and acceptance criteria.
+- A repeatable measurement plan separating technical audit scores, answer inclusion/citations, and referral or conversion outcomes.
+- A scoped implementation handoff through aeo-optimization, with source evidence, page targets, and validation criteria.
+
+## Steps
+1. Phase 1: `aeo-context`
+2. Phase 2: `aeo-opportunities`
+3. Phase 3: `aeo-roadmap`
+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: "aeo-strategy" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/go-to-market/analyze-revenue-system.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: analyze-revenue-system
+
+## Intent
+Analyze existing revenue data to produce a diagnostic of what is working and what is not across the full Winning by Design Bowtie — both the acquisition bow (Educate→Sign) and the expansion bow (Onboard→Advocate).
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/gtm/revenue-system-diagnostic-{YYYY-MM-DD}.pptx with ICP Clusters, Bowtie Left Bow Health, Bowtie Right Bow Health, What's Working/What's Not analysis, and Data Quality Flags.
+- **ICP Clusters**: Top 2–3 ICP clusters by closed-won volume and ACV with conversion rates and velocity.
+- **Bowtie Left Bow Health**: Stage-by-stage conversion rates from Educate through Sign; highest-dollar drop-off stage identified.
+- **Bowtie Right Bow Health**: Onboard completion rate, Adopt milestone rates, Expand trigger hit/miss, Renew rate, Advocate rate by ICP cluster.
+- **What's Working / What's Not**: Evidence-grounded summary with ≥1 recommendation per section.
+- **Data Quality Flags**: Missing fields and low-completion rates called out explicitly — no fabrication.
+
+## Steps
+1. Phase 1: `collect-data-sources`
+2. Phase 2: `analyze-acquisition-bow`
+3. Phase 3: `analyze-expansion-bow`
+4. Phase 4: `synthesize-diagnostic`
+5. Phase 5: `submit`
+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: "analyze-revenue-system" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/go-to-market/build-gtm-motion.md

@@ -0,0 +1,37 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: build-gtm-motion
+
+## Intent
+Build the GTM motion playbooks for each priority ICP: structured guides covering outreach through close using SPICED discovery, and expansion trigger playbooks covering the right bow of the Bowtie.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/gtm/gtm-motion-playbook-{icp-label}-{YYYY-MM-DD}.docx with Prospecting Criteria, Outreach Sequence templates, SPICED Discovery Framework, Objection Handling Guide with responses, and Expansion Trigger Playbook.
+- **Prospecting Criteria**: Exact firmographic and trigger-event filters for list building.
+- **Outreach Sequence**: ≥3 ICP-specific message templates with timing across ≥2 channels.
+- **SPICED Discovery Framework**: All 5 dimensions with ICP-tailored questions and a qualification gate.
+- **Objection Handling Guide**: ≥3 objections with responses grounded in revenue diagnostic data, or labeled representative if no data is available.
+- **Expansion Trigger Playbook**: ≥2 expansion signals with corresponding CS/AE actions.
+
+## Steps
+1. Phase 1: `load-icp-context`
+2. Phase 2: `build-outreach-sequences`
+3. Phase 3: `build-spiced-discovery`
+4. Phase 4: `build-objection-guide`
+5. Phase 5: `build-expansion-playbook`
+6. Phase 6: `produce-playbook`
+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: "build-gtm-motion" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.