fraim 2.0.362-next.4 → 2.0.362

package/dist/registry/stubs/jobs/ai-employee/customer/survey-campaign-management.md

@@ -0,0 +1,36 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: survey-campaign-management
+
+## Intent
+Launch NPS/CSAT surveys and targeted retention campaigns via the configured CRM, then analyze response clusters to surface actionable insight for the CS team.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/customer-success/survey-campaign-{YYYY-MM-DD}.pptx containing Survey/Campaign Details (type, status, audience), Response Count and Aggregate Scores, Cluster Analysis (top themes, trends, member counts), Delivery Stats, and Recommended Follow-Up Actions
+- Survey or campaign created and launched (or scheduled) in the CRM
+- For surveys with responses: feedback clusters and trend analysis
+- Recommended follow-up actions based on cluster findings
+
+## Steps
+1. Phase 1: `connect`
+2. Phase 2: `scope-intent`
+3. Phase 3: `design-content`
+4. Phase 4: `select-audience`
+5. Phase 5: `launch`
+6. Phase 6: `monitor-and-cluster`
+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: "survey-campaign-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

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

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: update-crm
+
+## Intent
+Update the team's CRM from customer-development context without forcing the user out of the IDE.
+
+## Outcome
+- `docs/customer-development/update-crm-<date>.md`
+- The requested CRM record updates are either applied or clearly blocked with the reason surfaced
+
+## Steps
+1. Phase 1: `scoping`
+2. Phase 2: `collect-source-context`
+3. Phase 3: `plan-update`
+4. Phase 4: `review`
+5. Phase 5: `apply-update`
+6. Phase 6: `completion`
+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: "update-crm" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/customer/user-survey-management.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: user-survey-management
+
+## Intent
+Engage target audiences across multiple social platforms through structured polls and surveys to gather quantitative and qualitative insights for product validation, submitting the content for review and publishing only after the user approves the dispatch.
+
+## Outcome
+- Final artifact: Published surveys on selected social platforms, dispatched only after approval.
+- **Actionable Insights**: Gathered feedback for product roadmap or strategy.
+- **Platform-Optimized Content**: Survey questions tailored for each social channel.
+
+## Steps
+1. Phase 1: `survey-scoping`
+2. Phase 2: `generate-linkedin-content`
+3. Phase 3: `generate-reddit-content`
+4. Phase 4: `generate-x-content`
+5. Phase 5: `generate-facebook-content`
+6. Phase 6: `generate-custom-content`
+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: "user-survey-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/design/brand-creation.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: brand-creation
+
+## Intent
+Create or materially strengthen a brand using one coherent workflow that can support new-brand creation, repositioning, rebrand work, product-brand work, founder-brand work, employer-brand work, and portfolio/architecture needs without fragmenting the catalog into many separate branding jobs.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/branding/brand-system/{slug}-{YYYY-MM-DD}.docx with brand core definition, positioning statement, differentiation logic, messaging system, and optional modules (naming, identity brief, architecture, governance, rebrand migration notes)
+- A brand system that includes brand core, positioning, differentiation, messaging, and downstream execution guidance
+- Optional output modules for naming, identity briefing, architecture recommendations, governance starter guidance, and rebrand migration notes
+
+## Steps
+1. Phase 1: `context-synthesis`
+2. Phase 2: `audience-and-market-framing`
+3. Phase 3: `brand-core-definition`
+4. Phase 4: `positioning-and-differentiation`
+5. Phase 5: `messaging-system`
+6. Phase 6: `optional-modules`
+7. Phase 7: `brand-system-output`
+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: "brand-creation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/design/branding-quality-audit.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: branding-quality-audit
+
+## Intent
+Evaluate the strength and coherence of an existing brand, produce a stable quality score, and emit analytics-friendly quality metrics that can feed FRAIM dashboards and downstream improvement workflows.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/branding/audits/{slug}-{YYYY-MM-DD}.pptx containing dimension scorecard (clarity, differentiation, coherence, proof, identity expressiveness, governance readiness), composite quality score, evidence highlights, and coaching recommendation
+- Flat quality metrics emitted for analytics
+- A coaching recommendation identifying the highest-leverage brand improvement
+
+## Steps
+1. Phase 1: `artifact-discovery`
+2. Phase 2: `brand-surface-review`
+3. Phase 3: `quality-scoring`
+4. Phase 4: `coaching-recommendation`
+5. Phase 5: `quality-score-emission`
+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: "branding-quality-audit" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/design/design-system-creation.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: design-system-creation
+
+## Intent
+Create or strengthen the reusable design system that downstream product surfaces, prototypes, and websites should extend instead of reinventing.
+
+## Outcome
+- **Reviewable deliverable**: A living HTML/CSS reference document at `docs/design-system/{slug}.html` containing rendered foundational tokens (color, typography, spacing, radius, elevation, motion), component library with usage rules and anti-patterns, page-level patterns, and a durable example surface demonstrating system application. A design system is referenced and used — not presented as slides.
+- Baseline design-system artifact under `docs/design-system/`
+- Defined tokens for color, type, spacing, elevation, and motion
+- Reusable component and layout rules for the target surface family
+- At least one durable example surface or specimen showing the system applied
+- Explicit downstream usage guidance for prototypes, websites, and product-facing UI work
+
+## Steps
+1. Phase 1: `design-system-context`
+2. Phase 2: `design-system-foundations`
+3. Phase 3: `design-system-patterns`
+4. Phase 4: `design-system-documentation`
+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: "design-system-creation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/design/ui-quality-assessment.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: ui-quality-assessment
+
+## Intent
+Produce a graded, product-wide UI/UX quality review — look-and-feel/aesthetics, Nielsen's 10 usability heuristics, interaction consistency/efficiency, and accessibility — the way `codebase-quality-assessment` does for code. Use it when the question is "Is our UI/UX any good?", not "does this one PR look right" (`ui-polish-validation`) and not "are we WCAG-compliant" (`accessibility-audit`).
+
+## Outcome
+- **Reviewable deliverable**: A report at `docs/quality-assurance/ui-quality-report-{YYYY-MM-DD}.md` with an overall A-F grade, a dimension scorecard, evidence highlights, and a prioritized remediation plan.
+- **Graded Quality**: An overall grade (A-F) for the product's UI/UX.
+- **Dimension Scorecard**: Scored `lookAndFeel`, `usabilityHeuristics`, `interactionConsistency`, and `accessibility`, each with a rationale.
+- **Prioritized Remediation**: A remediation list ordered by leverage, each item naming the dimension it improves and an effort tier (Quick / Medium / Large).
+- **Dashboard Telemetry**: A row in `fraim_quality_scores`, rendered as a new "UI/UX Quality" tile on the Quality dashboard, tracked run-over-run alongside Code Quality, Test Quality, Branding, and Production Readiness.
+
+## Steps
+1. Phase 1: `surface-scoping`
+2. Phase 2: `accessibility-dimension-resolution`
+3. Phase 3: `score-ui-quality-dimensions`
+4. Phase 4: `remediation-planning`
+5. Phase 5: `quality-score-emission`
+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: "ui-quality-assessment" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/design/user-facing-prototyping.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: user-facing-prototyping
+
+## Intent
+Quickly explore and demonstrate user-facing concepts, prioritizing UX and visual flow over technical perfection. This is a stakeholder-facing artifact meant to validate look, feel, and user utility.
+
+## Outcome
+- **Reviewable deliverable**: A set of interactive HTML/CSS prototype files at `docs/prototypes/{slug}/` that a stakeholder can open in a browser and walk through. The prototype IS the deliverable — not a screenshot or a deck of it.
+- Documented UX findings on flow, usability, and design effectiveness in `docs/prototypes/{slug}/README.md`
+
+## Steps
+1. Phase 1: `prototype-scoping`
+2. Phase 2: `prototype-execution`
+3. Phase 3: `prototype-demo`
+4. Phase 4: `prototype-decision`
+5. Phase 5: `prototype-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: "user-facing-prototyping" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/design/user-journey-mapping.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: user-journey-mapping
+
+## Intent
+Map the end-to-end user journey — from first awareness through ongoing use — with emotion scoring at each touchpoint and identified design opportunities that reduce friction and improve key moments.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/design/{date}-user-journey-map-{YYYY-MM-DD}.pptx containing journey stages and touchpoints with user actions and evidence, emotion curve visualization with high and low points, and prioritized design opportunities ranked by impact and effort
+- **Journey Map**: End-to-end journey with stages, touchpoints, user actions, and emotions at each step.
+- **Emotion Curve**: Emotional high and low points identified and evidence-grounded.
+- **Design Opportunities**: Prioritized opportunities ranked by improvement potential at high-pain touchpoints.
+
+## Steps
+1. Phase 1: `discovery-interviews`
+2. Phase 2: `touchpoint-mapping`
+3. Phase 3: `emotion-scoring`
+4. Phase 4: `opportunity-identification`
+5. Phase 5: `journey-map-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: "user-journey-mapping" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/design/ux-research-synthesis.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: ux-research-synthesis
+
+## Intent
+Run a structured usability test cycle — from participant recruitment through session execution, task scoring, and insight synthesis — producing actionable design recommendations grounded in observed user behavior.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/design/{date}-ux-research-synthesis-{YYYY-MM-DD}.pptx containing test protocol summary, task completion rates, usability issues with severity scoring matrix, key findings and mental model insights, and prioritized design recommendations with effort estimates
+- **Test Protocol**: Defined tasks, success criteria, and observer guidelines.
+- **Usability Scores**: Task completion rates and severity-scored usability issues.
+- **Design Recommendations**: Prioritized recommendations grounded in observed failure patterns.
+
+## Steps
+1. Phase 1: `recruitment`
+2. Phase 2: `test-execution`
+3. Phase 3: `scoring`
+4. Phase 4: `insight-synthesis`
+5. Phase 5: `ux-research-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: "ux-research-synthesis" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/design/website-creation.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: website-creation
+
+## Intent
+Create a modern, appealing, and valuable website that effectively showcases a product's value propositions and use cases, using competitive analysis and user preferences to deliver a professional, conversion-focused web experience.
+
+## Outcome
+- Final artifact: a live, functional, and performance-optimized website
+- User-centric design that reflects user preferences and competitive insights
+- Conversion-focused journeys with clear calls to action
+- Deployment-ready structure with hosting and rollout analysis
+
+## Steps
+1. Phase 1: `discovery-and-research`
+2. Phase 2: `design-and-development`
+3. Phase 3: `optimization-and-testing`
+4. Phase 4: `website-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: "website-creation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/dev-ops/cloud-application-deployment.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: cloud-application-deployment
+
+## Intent
+Prepare and execute an approved cloud deployment plan with source-backed configuration, secret-safe setup, rollback coverage, and post-deploy validation.
+
+## Outcome
+- Final artifact: A deployment plan or completed deployment record at `docs/dev-ops/cloud-deployment-{YYYY-MM-DD}.md`.
+- Draft infrastructure, CI/CD, environment, database, rollback, and validation steps before execution.
+- Proposed commands include purpose, expected effect, preconditions, secret names, validation checks, and rollback or disable steps.
+- Production deployment happens only after explicit approval and verified credentials.
+
+## Steps
+1. Phase 1: `platform-selection`
+2. Phase 2: `infrastructure-setup`
+3. Phase 3: `ci-cd-pipeline-setup`
+4. Phase 4: `environment-configuration`
+5. Phase 5: `database-initialization`
+6. Phase 6: `deployment-validation`
+7. Phase 7: `deployment-submission`
+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: "cloud-application-deployment" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/dev-ops/cloud-cost-optimization.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: cloud-cost-optimization
+
+## Intent
+Reduce cloud spend on a running production environment without breaking it. Systematically analyze costs, identify the biggest savings opportunities, weigh each against its production-impact risk, and implement the safe ones with rollback plans in hand. Single job parameterized by deployment platform — composes the platform-specific skill set (Azure / AWS / GCP) based on a Phase 1 platform decision.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/dev-ops/cloud-cost-optimization-{YYYY-MM-DD}.docx with implemented changes, cost savings summary, prioritized optimization actions with risk assessments, and rollback plans.
+- **Cost Reduction**: Verified reduction in cloud consumption.
+- **Actionable Plan**: Prioritized list of optimization actions with risk assessment and rollback plans.
+
+## Steps
+1. Phase 1: `platform-selection`
+2. Phase 2: `verify-authentication`
+3. Phase 3: `gather-cost-data`
+4. Phase 4: `identify-opportunities`
+5. Phase 5: `prioritize-actions`
+6. Phase 6: `execute-changes`
+7. Phase 7: `cost-optimization-submission`
+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: "cloud-cost-optimization" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/dev-ops/cloud-performance-diagnosis.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: cloud-performance-diagnosis
+
+## Intent
+Diagnose performance constraints (CPU, Memory, Network, Latency) within a cloud-hosted environment. Single job parameterized by deployment platform — composes the platform-specific telemetry / trace / log skills (Azure / AWS / GCP) based on a Phase 1 platform decision. Non-invasive data collection, bottleneck analysis, prioritized recommendations.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/dev-ops/cloud-performance-diagnosis-{YYYY-MM-DD}.docx with metric-backed diagnosis, identified bottlenecks, and prioritized cloud performance optimization recommendations.
+- **Metric-Backed Diagnosis**: Hypothesis based on real-time telemetry, traces, and logs.
+- **Resource Efficiency**: Identification of over-provisioned or under-performing cloud resources.
+
+## Steps
+1. Phase 1: `platform-selection`
+2. Phase 2: `setup-diagnostic-session`
+3. Phase 3: `collect-performance-data`
+4. Phase 4: `analyze-bottlenecks`
+5. Phase 5: `formulate-optimization-plan`
+6. Phase 6: `performance-submission`
+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: "cloud-performance-diagnosis" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/dev-ops/cross-cloud-migration.md

@@ -0,0 +1,42 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: cross-cloud-migration
+
+## Intent
+Move cloud infrastructure between providers (AWS → GCP, GCP → Azure, AWS → Azure, or any combination) with full resource inventory, per-resource strategy selection, IaC translation, network cutover planning, and validated rollback before a production switch.
+
+## Outcome
+- `workListPath`: `docs/migration/{issue_number}-cloud-migration-{runId}-work-list.md`
+- `migrationInventoryPath`: `docs/migration/{issue_number}-cloud-migration-{runId}-inventory.md`
+- **Migration summary**: `docs/migration/{issue_number}-migration-summary.md` — final record of migration scope, strategy decisions, IaC locations, and the DNS cutover runbook
+- **Target infrastructure**: Fully provisioned in the target cloud and validated, running in parallel. Source infrastructure remains live until the user executes the DNS cutover runbook to flip the final bit.
+
+## Steps
+1. Phase 1: `cloud-migration-scoping`
+2. Phase 2: `resource-inventory`
+3. Phase 3: `migration-strategy-selection`
+4. Phase 4: `iac-translation`
+5. Phase 5: `network-and-dns-planning`
+6. Phase 6: `dry-run-validation`
+7. Phase 7: `rollback-planning`
+8. Phase 8: `execute-migration`
+9. Phase 9: `post-migration-validation`
+10. Phase 10: `cutover-readiness`
+11. Phase 11: `execute-cutover`
+12. Phase 12: `submit`
+13. Phase 13: `address-feedback`
+14. Phase 14: `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: "cross-cloud-migration" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/dev-ops/incident-response.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: incident-response
+
+## Intent
+Run structured incident command from first alert to blameless postmortem — cutting MTTR by eliminating coordination overhead and ensuring every incident produces action items, not just a resolved ticket.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/incidents/incident-postmortem-{YYYY-MM-DD}.docx containing incident timeline, SEV classification, root cause analysis, contributing factors, and action items with owners. This requested human incident investigation is separate from the run's routine learning reflection and does not enter the pending learning queue.
+- Live incident channel: structured coordination with role assignments, timeboxed investigation rounds, and status page updates.
+- **SEV Classification**: Severity determined in < 2 minutes using the 4-tier matrix.
+- **Role Assignment**: IC, Comms Lead, Tech Lead, and Scribe assigned at incident open.
+- **Postmortem**: Timeline, root cause, contributing factors, and action items with owners.
+
+## Steps
+1. Phase 1: `severity-classification`
+2. Phase 2: `role-assignment`
+3. Phase 3: `investigation-timeboxing`
+4. Phase 4: `resolution`
+5. Phase 5: `postmortem`
+6. Phase 6: `incident-submission`
+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: "incident-response" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/dev-ops/production-readiness-review.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: production-readiness-review
+
+## Intent
+Perform a standalone production-readiness review for a real production workload. This job evaluates whether a system can be operated safely and repeatedly in production by reviewing security posture, high availability, backup and restore, observability, release safety, and operational runbooks against the declared scope.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/quality-assurance/production-readiness-{YYYY-MM-DD}.pptx with six-dimension scorecard (security posture, availability/resilience, backup/restore, observability/ops, release safety, governance), launch decision gate (pass/flag/fail), and remediation queue with priority scoring.
+- A durable production-readiness review with launch blockers, validation evidence, control-by-control status, remediation queue, and an explicit go / flag / fail decision
+- A rich quality score emitted to `fraim_quality_scores` so the analytics Quality tab shows a dedicated Production Readiness tile with sub-dimension breakdown
+
+## Steps
+1. Phase 1: `readiness-scope-and-context`
+2. Phase 2: `evidence-collection`
+3. Phase 3: `control-validation`
+4. Phase 4: `readiness-report`
+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: "production-readiness-review" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/dev-ops/reliability-review.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: reliability-review
+
+## Intent
+Conduct a quarterly reliability review that gives engineering leadership a data-driven view of SLO health, error budget consumption, runbook coverage, and on-call burden — with a prioritized action plan to address the most impactful gaps.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/dev-ops/reliability-review-{YYYY-MM-DD}.pptx containing SLO compliance table, error budget consumption analysis, runbook gap report with scoring, executive summary with RAG status, and prioritized action plan with owners and due dates.
+- **SLO Audit**: Assessment of every SLO against its target for the review period.
+- **Error Budget Analysis**: Budget consumption trend by SLO with forecast.
+- **Runbook Gap Report**: Identified runbook gaps with frequency and impact scoring.
+- **Action Plan**: Prioritized findings with owners, severity, and due dates.
+
+## Steps
+1. Phase 1: `slo-audit`
+2. Phase 2: `error-budget-review`
+3. Phase 3: `runbook-review`
+4. Phase 4: `action-plan`
+5. Phase 5: `reliability-review-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: "reliability-review" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.