portable-agent-layer 0.30.1 → 0.31.0

package/assets/skills/consulting-report/demo/components/quote-block.tsx

@@ -0,0 +1,17 @@
+interface QuoteBlockProps {
+  quote: string;
+  attribution: string;
+  role?: string;
+}
+
+export function QuoteBlock({ quote, attribution, role }: QuoteBlockProps) {
+  return (
+    <div className="quote-block">
+      <p className="quote-text">{quote}</p>
+      <p className="quote-attribution">
+        — {attribution}
+        {role && <span className="text-muted">, {role}</span>}
+      </p>
+    </div>
+  );
+}

package/assets/skills/consulting-report/demo/components/recommendation-card.tsx

@@ -0,0 +1,52 @@
+import { ArrowRight, Clock, Zap } from "lucide-react";
+import type { Recommendation } from "@/lib/report-data";
+import { cn } from "@/lib/utils";
+
+interface RecommendationCardProps {
+  recommendation: Recommendation;
+  index: number;
+}
+
+const priorityConfig = {
+  immediate: {
+    icon: Zap,
+    label: "Immediate",
+    className: "bg-destructive/10 text-destructive border-destructive/20",
+  },
+  "short-term": {
+    icon: Clock,
+    label: "Short-term",
+    className: "bg-warning/10 text-warning border-warning/20",
+  },
+  "long-term": {
+    icon: ArrowRight,
+    label: "Long-term",
+    className: "bg-primary/10 text-primary border-primary/20",
+  },
+} as const;
+
+export function RecommendationCard({ recommendation, index }: RecommendationCardProps) {
+  const config = priorityConfig[recommendation.priority];
+  const Icon = config.icon;
+
+  return (
+    <div className="finding-card">
+      <div className="finding-header">
+        <div className="flex items-start gap-3">
+          <span className="text-primary font-bold font-sans text-lg">{index + 1}</span>
+          <span className="finding-title">{recommendation.title}</span>
+        </div>
+        <span
+          className={cn(
+            "inline-flex items-center gap-1.5 px-3 py-1 rounded-full text-xs font-semibold border",
+            config.className
+          )}
+        >
+          <Icon className="h-3 w-3" />
+          {config.label}
+        </span>
+      </div>
+      <p className="text-foreground ml-8">{recommendation.description}</p>
+    </div>
+  );
+}

package/assets/skills/consulting-report/demo/components/section.tsx

@@ -0,0 +1,16 @@
+import { cn } from "@/lib/utils";
+
+interface SectionProps {
+  title: string;
+  children: React.ReactNode;
+  className?: string;
+}
+
+export function Section({ title, children, className }: SectionProps) {
+  return (
+    <section className={cn("report-section", className)}>
+      <h2>{title}</h2>
+      {children}
+    </section>
+  );
+}

package/assets/skills/consulting-report/demo/components/severity-badge.tsx

@@ -0,0 +1,19 @@
+import { cn } from "@/lib/utils";
+
+type Severity = "critical" | "high" | "medium" | "low";
+
+interface SeverityBadgeProps {
+  severity: Severity;
+}
+
+const severityConfig: Record<Severity, { label: string; className: string }> = {
+  critical: { label: "Critical", className: "severity-critical" },
+  high: { label: "High", className: "severity-high" },
+  medium: { label: "Medium", className: "severity-medium" },
+  low: { label: "Low", className: "severity-low" },
+};
+
+export function SeverityBadge({ severity }: SeverityBadgeProps) {
+  const config = severityConfig[severity];
+  return <span className={cn("severity-badge", config.className)}>{config.label}</span>;
+}

package/assets/skills/consulting-report/demo/components/timeline.tsx

@@ -0,0 +1,20 @@
+import type { TimelinePhase } from "@/lib/report-data";
+
+interface TimelineProps {
+  phases: TimelinePhase[];
+}
+
+export function Timeline({ phases }: TimelineProps) {
+  return (
+    <div className="timeline">
+      {phases.map((phase) => (
+        <div key={`${phase.phase}-${phase.title}`} className="timeline-item">
+          <div className="timeline-phase">{phase.phase}</div>
+          <div className="timeline-title">{phase.title}</div>
+          <div className="timeline-description">{phase.description}</div>
+          <div className="text-xs text-primary font-medium mt-1">{phase.duration}</div>
+        </div>
+      ))}
+    </div>
+  );
+}

package/assets/skills/consulting-report/demo/lib/report-data.ts

@@ -0,0 +1,247 @@
+export interface Finding {
+  id: string;
+  title: string;
+  description: string;
+  evidence: string;
+  source: string;
+  severity: "critical" | "high" | "medium" | "low";
+}
+
+export interface Recommendation {
+  id: string;
+  title: string;
+  description: string;
+  priority: "immediate" | "short-term" | "long-term";
+}
+
+export interface TimelinePhase {
+  phase: string;
+  title: string;
+  description: string;
+  duration: string;
+}
+
+export interface ReportData {
+  clientName: string;
+  reportTitle: string;
+  reportDate: string;
+  classification: string;
+  consultancyName: string;
+  preTitle?: string;
+
+  executiveSummary: {
+    context: string;
+    methodology: { interviewCount: number; roles: string[] };
+    keyFindings: string[];
+    primaryRecommendation: string;
+    expectedOutcomes: string[];
+  };
+
+  situationAssessment: {
+    currentState: string;
+    clientAsk: string;
+    whyNow: string;
+  };
+
+  findings: Finding[];
+
+  riskAnalysis: {
+    existentialRisks: string[];
+    competitiveThreats: string[];
+    timelinePressures: string;
+  };
+
+  strategicOpportunity: {
+    goodNews: string;
+    requirements: string[];
+  };
+
+  recommendations: Recommendation[];
+
+  targetState: {
+    description: string;
+    keyCapabilities: string[];
+    successMetrics: string[];
+  };
+
+  roadmap: TimelinePhase[];
+
+  callToAction: {
+    immediateSteps: string[];
+    decisionPoints: string[];
+    commitmentRequired: string;
+  };
+}
+
+export const reportData: ReportData = {
+  clientName: "Acme Industries",
+  reportTitle: "Operational Readiness Assessment",
+  reportDate: "April 21, 2026",
+  classification: "CONFIDENTIAL",
+  consultancyName: "Northbridge Advisory",
+  preTitle: "Operational Assessment",
+
+  executiveSummary: {
+    context:
+      "Acme Industries asked for an independent read on whether their engineering operations are ready to support the 3× revenue growth planned over the next 18 months. The assessment ran for six weeks and covered tier-1 production services, on-call practice, and incident response.",
+    methodology: {
+      interviewCount: 5,
+      roles: ["Head of Platform", "SRE Lead", "Senior Engineers (3)", "VP Engineering"],
+    },
+    keyFindings: [
+      "Production deploys lack a tested rollback path — the single largest operational risk.",
+      "Runbooks are stale across half of tier-1 services.",
+      "On-call coverage is concentrated in three engineers; knowledge has not diffused.",
+    ],
+    primaryRecommendation:
+      "Add a tested rollback gate to the production deploy pipeline within four weeks. It is the single highest-leverage operational fix available and unblocks the rest of the readiness work.",
+    expectedOutcomes: [
+      "Mean time to recovery within 1.5× peer benchmark by end of Q3",
+      "Zero production deploys without a successful rollback dry-run in staging",
+      "On-call coverage spread across 8 engineers within six months",
+    ],
+  },
+
+  situationAssessment: {
+    clientAsk:
+      "An independent read on whether engineering operations are ready to support the planned 3× revenue ramp over the next 18 months.",
+    currentState:
+      "Engineering operations are competent but carry three structural gaps: an untested rollback path in production, stale runbooks across half of tier-1 services, and dangerous concentration of on-call coverage in three engineers. MTTR is currently running at 3× peer benchmarks.",
+    whyNow:
+      "The 3× revenue ramp begins in Q3 2026 and pulls forward operational scale that today's processes cannot absorb. Each gap that goes into Q3 unaddressed compounds under load — the cost of remediation rises sharply once growth begins.",
+  },
+
+  findings: [
+    {
+      id: "F1",
+      title: "Release pipeline lacks a rollback path",
+      description:
+        "Production deploys are one-way: the pipeline lacks a tested rollback step. Of the last 12 incidents, 4 required manual database surgery because the deploy couldn't be reverted.",
+      evidence:
+        "Mean time to recovery is 3× peer benchmarks, and engineers report avoiding late-week deploys — slowing feature delivery.",
+      source: "Pipeline review + Q1 incident post-mortems (12)",
+      severity: "critical",
+    },
+    {
+      id: "F2",
+      title: "Runbooks are out of date across half the critical services",
+      description:
+        "7 of 14 tier-1 services have runbooks last updated more than 18 months ago. Three of those services have been re-architected since.",
+      evidence:
+        "Runbook inventory: 5 fresh (≤6 months), 2 aging (6–18 months), 7 stale (>18 months).",
+      source: "Runbook inventory audit",
+      severity: "high",
+    },
+    {
+      id: "F3",
+      title: "On-call rotation is concentrated in three engineers",
+      description:
+        "Over the last quarter, three engineers covered 71% of the on-call minutes. The shadow-rotation system exists on paper but is not enforced.",
+      evidence:
+        "Engineer A: 28%, Engineer B: 24%, Engineer C: 19%. Remaining 8 engineers split 29%. Zero shadow rotations completed in the last two quarters.",
+      source: "On-call coverage logs (90 days)",
+      severity: "medium",
+    },
+  ],
+
+  riskAnalysis: {
+    existentialRisks: [
+      "Production deploys with no rollback path during the growth ramp — a single bad deploy at peak load could require live database surgery during the busiest hour.",
+      "Knowledge concentration in three engineers means a single departure or unavailability event compromises incident response across half the platform.",
+    ],
+    competitiveThreats: [
+      "MTTR running at 3× peer benchmarks materially limits feature velocity at exactly the moment competitors are accelerating.",
+      "Engineers self-report avoiding late-week deploys; growth requires the opposite — confidence to deploy at any time.",
+    ],
+    timelinePressures:
+      "The Q3 2026 ramp begins in roughly three months. Operational fixes that take a sprint today take a quarter once the team is also absorbing 3× load.",
+  },
+
+  strategicOpportunity: {
+    goodNews:
+      "All three findings are process gaps, not capability gaps. The team is competent and well-intentioned — the fixes don't require new hires, only sequencing and leadership commitment.",
+    requirements: [
+      "Treat the rollback gate as a P0 platform initiative, not a sprint task",
+      "Create a cross-team runbook refresh ritual that doesn't depend on individual heroics",
+      "Make on-call rotation breadth a leadership-tracked KPI",
+    ],
+  },
+
+  recommendations: [
+    {
+      id: "R1",
+      title: "Add a tested rollback gate to the deploy pipeline",
+      description:
+        "Before any production deploy, require a successful rollback dry-run in staging. Block the pipeline on red. Validate monthly via chaos day. Owner: Platform team. Target: implemented within 4 weeks.",
+      priority: "immediate",
+    },
+    {
+      id: "R2",
+      title: "Runbook refresh sprint",
+      description:
+        "Allocate one sprint in Q3 to refresh all tier-1 runbooks. Each owner writes a 10-minute 'what wakes me up at 3am' paragraph. Reviewed as pair exercise with on-call. Owner: Service owners + SRE.",
+      priority: "short-term",
+    },
+    {
+      id: "R3",
+      title: "Broaden on-call to 8 engineers within 6 months",
+      description:
+        "Rotate 2 new engineers through a 4-week shadow period each quarter. Gate solo rotation on a resolved-incident checklist, not tenure.",
+      priority: "long-term",
+    },
+  ],
+
+  targetState: {
+    description:
+      "Engineering operations that can absorb 3× load without operator heroics — every tier-1 service has a fresh runbook, every production deploy has a tested rollback, and on-call is a shared discipline rather than a three-person tax.",
+    keyCapabilities: [
+      "Single-command rollback validated monthly",
+      "Tier-1 runbook freshness as a service-owner KPI",
+      "8-engineer on-call rotation with a tracked shadow program",
+    ],
+    successMetrics: [
+      "MTTR within 1.5× peer benchmark",
+      "Zero deploys without successful rollback dry-run in staging",
+      "No engineer carries more than 15% of monthly on-call minutes",
+    ],
+  },
+
+  roadmap: [
+    {
+      phase: "Phase 1",
+      title: "Rollback Gate",
+      description:
+        "Implement and validate the tested rollback step in the production pipeline. Block deploys that haven't passed the rollback dry-run.",
+      duration: "Weeks 1-4",
+    },
+    {
+      phase: "Phase 2",
+      title: "Runbook Refresh",
+      description:
+        "Q3 dedicated sprint refreshing all tier-1 runbooks with current architecture and on-call pair review.",
+      duration: "Weeks 5-12",
+    },
+    {
+      phase: "Phase 3",
+      title: "On-Call Broadening",
+      description:
+        "Run two cohorts of shadow rotations; reach 8-engineer coverage with tracked solo-readiness checklist.",
+      duration: "Weeks 13-26",
+    },
+  ],
+
+  callToAction: {
+    immediateSteps: [
+      "Approve P0 status for the rollback gate initiative",
+      "Block the first runbook refresh sprint slot in Q3",
+      "Identify the five engineers entering shadow rotation in Q3",
+    ],
+    decisionPoints: [
+      "Approve dedicated platform-team capacity for the rollback gate",
+      "Approve sprint allocation for the Q3 runbook refresh",
+      "Approve the on-call expansion target of 8 engineers",
+    ],
+    commitmentRequired:
+      "Treat operational readiness as a leadership priority through Q4. Without sustained executive attention, the rollback gate ships and then drifts; the runbook refresh becomes one-time. The discipline must be visible from the top.",
+  },
+};

package/assets/skills/consulting-report/demo/lib/utils.ts

@@ -0,0 +1,6 @@
+import { type ClassValue, clsx } from "clsx";
+import { twMerge } from "tailwind-merge";
+
+export function cn(...inputs: ClassValue[]) {
+  return twMerge(clsx(inputs));
+}

package/assets/skills/consulting-report/demo/next.config.js

@@ -0,0 +1,9 @@
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+  output: "export",
+  images: { unoptimized: true },
+  trailingSlash: true,
+  turbopack: { root: __dirname },
+};
+
+module.exports = nextConfig;

package/assets/skills/consulting-report/demo/package.json

@@ -0,0 +1,27 @@
+{
+  "name": "consulting-report",
+  "version": "0.0.0",
+  "private": true,
+  "scripts": {
+    "dev": "next dev",
+    "build": "next build",
+    "lint": "next lint"
+  },
+  "dependencies": {
+    "next": "16.2.4",
+    "react": "19.2.5",
+    "react-dom": "19.2.5",
+    "lucide-react": "1.14.0",
+    "clsx": "2.1.1",
+    "tailwind-merge": "3.5.0"
+  },
+  "devDependencies": {
+    "@tailwindcss/postcss": "4.2.4",
+    "@types/node": "25.6.0",
+    "@types/react": "19.2.14",
+    "@types/react-dom": "19.2.3",
+    "postcss": "8.5.13",
+    "tailwindcss": "4.2.4",
+    "typescript": "6.0.3"
+  }
+}

package/assets/skills/consulting-report/demo/postcss.config.mjs

@@ -0,0 +1,5 @@
+export default {
+  plugins: {
+    "@tailwindcss/postcss": {},
+  },
+};

package/assets/skills/consulting-report/demo/tsconfig.json

@@ -0,0 +1,41 @@
+{
+  "compilerOptions": {
+    "lib": [
+      "dom",
+      "dom.iterable",
+      "esnext"
+    ],
+    "allowJs": true,
+    "skipLibCheck": true,
+    "strict": true,
+    "noEmit": true,
+    "esModuleInterop": true,
+    "module": "esnext",
+    "moduleResolution": "bundler",
+    "resolveJsonModule": true,
+    "isolatedModules": true,
+    "jsx": "react-jsx",
+    "incremental": true,
+    "plugins": [
+      {
+        "name": "next"
+      }
+    ],
+    "paths": {
+      "@/*": [
+        "./*"
+      ]
+    },
+    "target": "ES2017"
+  },
+  "include": [
+    "next-env.d.ts",
+    "**/*.ts",
+    "**/*.tsx",
+    ".next/types/**/*.ts",
+    ".next/dev/types/**/*.ts"
+  ],
+  "exclude": [
+    "node_modules"
+  ]
+}