@jaggerxtrm/specialists 3.2.0 → 3.3.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@jaggerxtrm/specialists",
-  "version": "3.2.0",
-  "description": "OmniSpecialist \u2014 7-tool MCP orchestration layer powered by the Specialist System. Discover and execute .specialist.yaml files across project/user/system scopes via pi.",
+  "version": "3.3.0",
+  "description": "OmniSpecialist — 7-tool MCP orchestration layer powered by the Specialist System. Discover and execute .specialist.yaml files across project/user/system scopes via pi.",
   "main": "dist/index.js",
   "type": "module",
   "files": [
@@ -12,6 +12,7 @@
   ],
   "bin": {
     "specialists": "dist/index.js",
+    "sp": "dist/index.js",
     "install": "bin/install.js"
   },
   "scripts": {

package/hooks/beads-close-memory-prompt.mjs

@@ -1,47 +0,0 @@
-#!/usr/bin/env node
-// beads-close-memory-prompt — Claude Code PostToolUse hook
-// After `bd close`: injects a short reminder into Claude's context to capture
-// knowledge and consider underused beads features.
-// Output to stdout is shown to Claude as additional context.
-//
-// Installed by: specialists install
-
-import { readFileSync, existsSync } from 'node:fs';
-import { join } from 'node:path';
-
-let input;
-try {
-  input = JSON.parse(readFileSync(0, 'utf8'));
-} catch {
-  process.exit(0);
-}
-
-// Only fire on Bash tool
-if (input.tool_name !== 'Bash') process.exit(0);
-
-const cmd = (input.tool_input?.command ?? '').trim();
-
-// Only fire when the command is `bd close ...`
-if (!/\bbd\s+close\b/.test(cmd)) process.exit(0);
-
-// Only fire in projects that use beads
-const cwd = input.cwd ?? process.env.CLAUDE_PROJECT_DIR ?? process.cwd();
-if (!existsSync(join(cwd, '.beads'))) process.exit(0);
-
-// Inject reminder into Claude's context
-process.stdout.write(
-  '\n[beads] Issue(s) closed. Before moving on:\n\n' +
-  '  Knowledge worth keeping?\n' +
-  '    bd remember "key insight from this work"\n' +
-  '    bd memories <keyword>   -- search what is already stored\n\n' +
-  '  Discovered related work while implementing?\n' +
-  '    bd create --title="..." --deps=discovered-from:<id>\n\n' +
-  '  Underused features to consider:\n' +
-  '    bd dep add <a> <b>   -- link blocking relationships between issues\n' +
-  '    bd graph             -- visualize issue dependency graph\n' +
-  '    bd orphans           -- issues referenced in commits but still open\n' +
-  '    bd preflight         -- PR readiness checklist before gh pr create\n' +
-  '    bd stale             -- issues not touched recently\n'
-);
-
-process.exit(0);

package/hooks/beads-commit-gate.mjs

@@ -1,58 +0,0 @@
-#!/usr/bin/env node
-// beads-commit-gate — Claude Code PreToolUse hook
-// Blocks `git commit` when in_progress beads issues still exist.
-// Forces: close issues first, THEN commit.
-// Exit 0: allow  |  Exit 2: block (stderr shown to Claude)
-//
-// Installed by: specialists install
-
-import { execSync } from 'node:child_process';
-import { readFileSync, existsSync } from 'node:fs';
-import { join } from 'node:path';
-
-let input;
-try {
-  input = JSON.parse(readFileSync(0, 'utf8'));
-} catch {
-  process.exit(0);
-}
-
-const tool = input.tool_name ?? '';
-if (tool !== 'Bash') process.exit(0);
-
-const cmd = input.tool_input?.command ?? '';
-if (!/\bgit\s+commit\b/.test(cmd)) process.exit(0);
-
-const cwd = input.cwd ?? process.env.CLAUDE_PROJECT_DIR ?? process.cwd();
-if (!existsSync(join(cwd, '.beads'))) process.exit(0);
-
-let inProgress = 0;
-let summary = '';
-try {
-  const output = execSync('bd list --status=in_progress', {
-    encoding: 'utf8',
-    cwd,
-    stdio: ['pipe', 'pipe', 'pipe'],
-    timeout: 8000,
-  });
-  inProgress = (output.match(/in_progress/g) ?? []).length;
-  summary = output.trim();
-} catch {
-  process.exit(0);
-}
-
-if (inProgress > 0) {
-  process.stderr.write(
-    '🚫 BEADS GATE: Close open issues before committing.\n\n' +
-    `Open issues:\n${summary}\n\n` +
-    'Next steps:\n' +
-    '  3. bd close <id1> <id2> ...             ← you are here\n' +
-    '  4. git add <files> && git commit -m "..."\n' +
-    '  5. git push -u origin <feature-branch>\n' +
-    '  6. gh pr create --fill && gh pr merge --squash\n' +
-    '  7. git checkout master && git reset --hard origin/master\n'
-  );
-  process.exit(2);
-}
-
-process.exit(0);

package/hooks/beads-edit-gate.mjs

@@ -1,53 +0,0 @@
-#!/usr/bin/env node
-// beads-edit-gate — Claude Code PreToolUse hook
-// Blocks file edits when no beads issue is in_progress.
-// Only active in projects with a .beads/ directory.
-// Exit 0: allow  |  Exit 2: block (stderr shown to Claude)
-//
-// Installed by: specialists install
-
-import { execSync } from 'node:child_process';
-import { readFileSync, existsSync } from 'node:fs';
-import { join } from 'node:path';
-
-let input;
-try {
-  input = JSON.parse(readFileSync(0, 'utf8'));
-} catch {
-  process.exit(0);
-}
-
-const cwd = input.cwd ?? process.env.CLAUDE_PROJECT_DIR ?? process.cwd();
-if (!existsSync(join(cwd, '.beads'))) process.exit(0);
-
-let inProgress = 0;
-try {
-  const output = execSync('bd list --status=in_progress', {
-    encoding: 'utf8',
-    cwd,
-    stdio: ['pipe', 'pipe', 'pipe'],
-    timeout: 8000,
-  });
-  inProgress = (output.match(/in_progress/g) ?? []).length;
-} catch {
-  process.exit(0);
-}
-
-if (inProgress === 0) {
-  process.stderr.write(
-    '🚫 BEADS GATE: No active issue — create one before editing files.\n\n' +
-    '  bd create --title="<what you\'re doing>" --type=task --priority=2\n' +
-    '  bd update <id> --status=in_progress\n\n' +
-    'Full workflow (do this every session):\n' +
-    '  1. bd create + bd update in_progress   ← you are here\n' +
-    '  2. Edit files / write code\n' +
-    '  3. bd close <id>                        close when done\n' +
-    '  4. git add <files> && git commit\n' +
-    '  5. git push -u origin <feature-branch>\n' +
-    '  6. gh pr create --fill && gh pr merge --squash\n' +
-    '  7. git checkout master && git reset --hard origin/master\n'
-  );
-  process.exit(2);
-}
-
-process.exit(0);

package/hooks/beads-stop-gate.mjs

@@ -1,52 +0,0 @@
-#!/usr/bin/env node
-// beads-stop-gate — Claude Code Stop hook
-// Blocks the agent from stopping when in_progress beads issues remain.
-// Exit 0: allow stop  |  Exit 2: block stop (stderr shown to Claude)
-//
-// Installed by: specialists install
-
-import { execSync } from 'node:child_process';
-import { readFileSync, existsSync } from 'node:fs';
-import { join } from 'node:path';
-
-let input;
-try {
-  input = JSON.parse(readFileSync(0, 'utf8'));
-} catch {
-  process.exit(0);
-}
-
-const cwd = input.cwd ?? process.env.CLAUDE_PROJECT_DIR ?? process.cwd();
-if (!existsSync(join(cwd, '.beads'))) process.exit(0);
-
-let inProgress = 0;
-let summary = '';
-try {
-  const output = execSync('bd list --status=in_progress', {
-    encoding: 'utf8',
-    cwd,
-    stdio: ['pipe', 'pipe', 'pipe'],
-    timeout: 8000,
-  });
-  inProgress = (output.match(/in_progress/g) ?? []).length;
-  summary = output.trim();
-} catch {
-  process.exit(0);
-}
-
-if (inProgress > 0) {
-  process.stderr.write(
-    '🚫 BEADS STOP GATE: Unresolved issues — complete the session close protocol.\n\n' +
-    `Open issues:\n${summary}\n\n` +
-    'Session close protocol:\n' +
-    '  3. bd close <id1> <id2> ...               close all in_progress issues\n' +
-    '  4. git add <files> && git commit -m "..."  commit your changes\n' +
-    '  5. git push -u origin <feature-branch>     push feature branch\n' +
-    '  6. gh pr create --fill                     create PR\n' +
-    '  7. gh pr merge --squash                    merge PR\n' +
-    '  8. git checkout master && git reset --hard origin/master\n'
-  );
-  process.exit(2);
-}
-
-process.exit(0);

package/hooks/specialists-complete.mjs

@@ -1,60 +0,0 @@
-#!/usr/bin/env node
-// specialists-complete — Claude Code UserPromptSubmit hook
-// Checks .specialists/ready/ for completed background job markers and injects
-// completion banners into Claude's context.
-//
-// Installed by: specialists install
-
-import { existsSync, readdirSync, readFileSync, unlinkSync } from 'node:fs';
-import { join } from 'node:path';
-
-const cwd = process.env.CLAUDE_PROJECT_DIR ?? process.cwd();
-const readyDir = join(cwd, '.specialists', 'ready');
-
-// Exit silently if no ready dir or nothing to report
-if (!existsSync(readyDir)) process.exit(0);
-
-let markers;
-try {
-  markers = readdirSync(readyDir).filter(f => !f.startsWith('.'));
-} catch {
-  process.exit(0);
-}
-
-if (markers.length === 0) process.exit(0);
-
-const banners = [];
-
-for (const jobId of markers) {
-  const markerPath = join(readyDir, jobId);
-  const statusPath = join(cwd, '.specialists', 'jobs', jobId, 'status.json');
-
-  try {
-    let specialist = jobId;
-    let elapsed = '';
-
-    if (existsSync(statusPath)) {
-      const status = JSON.parse(readFileSync(statusPath, 'utf-8'));
-      specialist = status.specialist ?? jobId;
-      elapsed = status.elapsed_s !== undefined ? `, ${status.elapsed_s}s` : '';
-    }
-
-    banners.push(
-      `[Specialist '${specialist}' completed (job ${jobId}${elapsed}). Run: specialists result ${jobId}]`
-    );
-
-    // Delete marker so it only fires once
-    unlinkSync(markerPath);
-  } catch {
-    // Ignore malformed entries
-    try { unlinkSync(markerPath); } catch { /* ignore */ }
-  }
-}
-
-if (banners.length === 0) process.exit(0);
-
-// UserPromptSubmit hooks inject content via JSON
-process.stdout.write(JSON.stringify({
-  type: 'inject',
-  content: banners.join('\n'),
-}) + '\n');

package/hooks/specialists-main-guard.mjs

@@ -1,90 +0,0 @@
-#!/usr/bin/env node
-// Claude Code PreToolUse hook — block writes and direct master pushes
-// Exit 0: allow  |  Exit 2: block (message shown to user)
-//
-// Installed by: specialists install
-
-import { execSync } from 'node:child_process';
-import { readFileSync } from 'node:fs';
-
-let branch = '';
-try {
-  branch = execSync('git branch --show-current', {
-    encoding: 'utf8',
-    stdio: ['pipe', 'pipe', 'pipe'],
-  }).trim();
-} catch {}
-
-// Not in a git repo or not on a protected branch — allow
-if (!branch || (branch !== 'main' && branch !== 'master')) {
-  process.exit(0);
-}
-
-let input;
-try {
-  input = JSON.parse(readFileSync(0, 'utf8'));
-} catch {
-  process.exit(0);
-}
-
-const tool = input.tool_name ?? '';
-
-const WRITE_TOOLS = new Set(['Edit', 'Write', 'MultiEdit', 'NotebookEdit']);
-
-if (WRITE_TOOLS.has(tool)) {
-  process.stderr.write(
-    `⛔ You are on '${branch}' — never edit files directly on master.\n\n` +
-    'Full workflow:\n' +
-    '  1. git checkout -b feature/<name>         ← start here\n' +
-    '  2. bd create + bd update in_progress      track your work\n' +
-    '  3. Edit files / write code\n' +
-    '  4. bd close <id> && git add && git commit\n' +
-    '  5. git push -u origin feature/<name>\n' +
-    '  6. gh pr create --fill && gh pr merge --squash\n' +
-    '  7. git checkout master && git reset --hard origin/master\n'
-  );
-  process.exit(2);
-}
-
-// Block direct commits and pushes to master — use feature branches + gh pr create/merge
-if (tool === 'Bash') {
-  const cmd = (input.tool_input?.command ?? '').trim().replace(/\s+/g, ' ');
-
-  if (/^git commit/.test(cmd)) {
-    process.stderr.write(
-      `⛔ Don't commit directly to '${branch}' — use a feature branch.\n\n` +
-      'Full workflow:\n' +
-      '  1. git checkout -b feature/<name>         ← start here\n' +
-      '  2. bd create + bd update in_progress      track your work\n' +
-      '  3. Edit files / write code\n' +
-      '  4. bd close <id> && git add && git commit\n' +
-      '  5. git push -u origin feature/<name>\n' +
-      '  6. gh pr create --fill && gh pr merge --squash\n' +
-      '  7. git checkout master && git reset --hard origin/master\n'
-    );
-    process.exit(2);
-  }
-
-  if (/^git push/.test(cmd)) {
-    const tokens = cmd.split(' ');
-    const lastToken = tokens[tokens.length - 1];
-    const explicitMaster = /^(master|main)$/.test(lastToken) || /:(master|main)$/.test(lastToken);
-    const impliedMaster = tokens.length <= 3 && (branch === 'main' || branch === 'master');
-    if (explicitMaster || impliedMaster) {
-      process.stderr.write(
-        `⛔ Don't push directly to '${branch}' — use the PR workflow.\n\n` +
-        'Next steps:\n' +
-        '  5. git push -u origin <feature-branch>     ← push your branch\n' +
-        '  6. gh pr create --fill                      create PR\n' +
-        '     gh pr merge --squash                     merge it\n' +
-        '  7. git checkout master                      sync master\n' +
-        '     git reset --hard origin/master\n\n' +
-        'If you\'re not on a feature branch yet:\n' +
-        '  git checkout -b feature/<name>    (then re-commit and push)\n'
-      );
-      process.exit(2);
-    }
-  }
-}
-
-process.exit(0);

package/hooks/specialists-session-start.mjs

@@ -1,105 +0,0 @@
-#!/usr/bin/env node
-// specialists-session-start — Claude Code SessionStart hook
-// Injects specialists context at the start of every session:
-//   • Active background jobs (if any)
-//   • Available specialists list
-//   • Key CLI commands reminder
-//
-// Installed by: specialists install
-// Hook type: SessionStart
-
-import { existsSync, readdirSync, readFileSync } from 'node:fs';
-import { join } from 'node:path';
-import { homedir } from 'node:os';
-
-const cwd     = process.env.CLAUDE_PROJECT_DIR ?? process.cwd();
-const HOME    = homedir();
-const jobsDir = join(cwd, '.specialists', 'jobs');
-const lines   = [];
-
-// ── 1. Active background jobs ──────────────────────────────────────────────
-if (existsSync(jobsDir)) {
-  let entries = [];
-  try { entries = readdirSync(jobsDir); } catch { /* ignore */ }
-
-  const activeJobs = [];
-  for (const jobId of entries) {
-    const statusPath = join(jobsDir, jobId, 'status.json');
-    if (!existsSync(statusPath)) continue;
-    try {
-      const s = JSON.parse(readFileSync(statusPath, 'utf-8'));
-      if (s.status === 'running' || s.status === 'starting') {
-        const elapsed = s.elapsed_s !== undefined ? ` (${s.elapsed_s}s)` : '';
-        activeJobs.push(
-          `  • ${s.specialist ?? jobId}  [${s.status}]${elapsed}  →  specialists result ${jobId}`
-        );
-      }
-    } catch { /* malformed status.json */ }
-  }
-
-  if (activeJobs.length > 0) {
-    lines.push('## Specialists — Active Background Jobs');
-    lines.push('');
-    lines.push(...activeJobs);
-    lines.push('');
-    lines.push('Use `specialists feed <job-id> --follow` to stream events, or `specialists result <job-id>` when done.');
-    lines.push('');
-  }
-}
-
-// ── 2. Available specialists (read YAML dirs directly) ────────────────────
-function readSpecialistNames(dir) {
-  if (!existsSync(dir)) return [];
-  try {
-    return readdirSync(dir)
-      .filter(f => f.endsWith('.specialist.yaml'))
-      .map(f => f.replace('.specialist.yaml', ''));
-  } catch {
-    return [];
-  }
-}
-
-const projectNames = readSpecialistNames(join(cwd, 'specialists'));
-const userNames    = readSpecialistNames(join(HOME, '.agents', 'specialists'));
-
-// Merge, deduplicate, sort
-const allNames = [...new Set([...projectNames, ...userNames])].sort();
-
-if (allNames.length > 0) {
-  lines.push('## Specialists — Available');
-  lines.push('');
-  if (projectNames.length > 0) {
-    lines.push(`project (${projectNames.length}): ${projectNames.join(', ')}`);
-  }
-  if (userNames.length > 0) {
-    // Only show user-scope names not already in project
-    const extraUser = userNames.filter(n => !projectNames.includes(n));
-    if (extraUser.length > 0) {
-      lines.push(`user    (${extraUser.length}): ${extraUser.join(', ')}`);
-    }
-  }
-  lines.push('');
-}
-
-// ── 3. Key commands reminder ───────────────────────────────────────────────
-lines.push('## Specialists — Session Quick Reference');
-lines.push('');
-lines.push('```');
-lines.push('specialists list                                   # discover available specialists');
-lines.push('specialists run <name> --prompt "..."              # run foreground (streams output)');
-lines.push('specialists run <name> --prompt "..." --background # run async → returns job ID');
-lines.push('specialists feed <job-id> --follow                 # tail live events');
-lines.push('specialists result <job-id>                        # read final output');
-lines.push('specialists status                                 # system health');
-lines.push('specialists doctor                                 # troubleshoot issues');
-lines.push('```');
-lines.push('');
-lines.push('MCP tools: specialist_init · use_specialist · start_specialist · poll_specialist · run_parallel');
-
-// ── Output ─────────────────────────────────────────────────────────────────
-if (lines.length === 0) process.exit(0);
-
-process.stdout.write(JSON.stringify({
-  type: 'inject',
-  content: lines.join('\n'),
-}) + '\n');

package/specialists/auto-remediation.specialist.yaml

@@ -1,70 +0,0 @@
-specialist:
-  metadata:
-    name: auto-remediation
-    version: 1.0.0
-    description: "Autonomous self-healing workflow: detect issue, diagnose root cause, implement fix, and verify resolution."
-    category: workflow
-    tags: [remediation, self-healing, debugging, autonomous, operations]
-    updated: "2026-03-07"
-
-  execution:
-    mode: tool
-    model: google-gemini-cli/gemini-3-flash-preview
-    fallback_model: anthropic/claude-sonnet-4-6
-    timeout_ms: 600000
-    response_format: markdown
-    permission_required: HIGH
-
-  prompt:
-    system: |
-      You are the Auto-Remediation specialist — an autonomous self-healing operations engine.
-      You investigate symptoms, diagnose root causes, implement fixes, and verify resolution
-      through four structured phases:
-
-      Phase 1 - Issue Detection:
-        Analyze reported symptoms in detail. Identify affected systems, components, or files.
-        Classify the issue type (bug, config, dependency, performance, etc.).
-        Gather relevant context using available tools.
-
-      Phase 2 - Root Cause Diagnosis:
-        Trace the issue to its root cause. Distinguish symptoms from causes.
-        Identify contributing factors and the failure chain.
-        Assess severity and blast radius.
-
-      Phase 3 - Fix Implementation:
-        Propose a concrete remediation plan with up to $max_actions steps.
-        For each step provide:
-          - Proposed action
-          - Expected output
-          - Verification checks
-          - Residual risks
-        Execute the fix if autonomy level permits.
-
-      Phase 4 - Verification:
-        Confirm the fix resolves the original symptoms.
-        Check for regressions or side effects.
-        Document what was changed and why.
-
-      Rules:
-      - Always diagnose before acting. Do not skip to Phase 3 without completing Phase 2.
-      - Respect the autonomy level: HIGH permits file writes and command execution.
-      - Be explicit about uncertainty. If unsure, propose options rather than guessing.
-      - Output a clear remediation report suitable for incident documentation.
-      EFFICIENCY RULE: Produce your answer as soon as you have enough information.
-      Do NOT exhaustively explore every file. Gather minimal context, then write your response.
-      Stop using tools and write your final answer after at most 10 tool calls.
-
-    task_template: |
-      Perform autonomous remediation for the following issue:
-
-      Symptoms: $prompt
-
-      Maximum remediation steps: $max_actions
-      Autonomy level: $autonomy_level
-      Attachments/logs: $attachments
-
-      Work through all four phases: Detection, Diagnosis, Fix Implementation, Verification.
-      Produce a complete remediation report with a "## Resolution Summary" at the end.
-
-  communication:
-    publishes: [remediation_plan, incident_report, fix_summary]

package/specialists/bug-hunt.specialist.yaml

@@ -1,94 +0,0 @@
-specialist:
-  metadata:
-    name: bug-hunt
-    version: 1.1.0
-    description: "Autonomously investigates bug symptoms using GitNexus call-chain tracing: finds execution flows, traces callers/callees, identifies root cause, and produces an actionable remediation plan."
-    category: workflow
-    tags: [debugging, bug-hunt, root-cause, investigation, remediation, gitnexus]
-    updated: "2026-03-11"
-
-  execution:
-    mode: tool
-    model: anthropic/claude-sonnet-4-6
-    fallback_model: google-gemini-cli/gemini-3.1-pro-preview
-    timeout_ms: 300000
-    response_format: markdown
-    permission_required: LOW
-
-  prompt:
-    system: |
-      You are an autonomous bug hunting specialist. Given reported symptoms, you conduct a
-      systematic investigation to identify the root cause and produce an actionable fix plan.
-
-      ## Investigation Phases
-
-      ### Phase 0 — GitNexus Triage (if available)
-
-      Before reading any files, use the knowledge graph to orient yourself:
-
-      1. `gitnexus_query({query: "<error text or symptom>"})`
-         → Surfaces execution flows and symbols related to the symptom.
-         → Immediately reveals which processes and functions are involved.
-
-      2. For each suspect symbol: `gitnexus_context({name: "<symbol>"})`
-         → Callers (who triggers it), callees (what it depends on), processes it belongs to.
-         → Pinpoints where in the call chain the failure likely occurs.
-
-      3. Read `gitnexus://repo/{name}/process/{name}` for the most relevant execution flow.
-         → Trace the full sequence of steps to find where the chain breaks.
-
-      4. If needed: `gitnexus_cypher({query: "MATCH path = ..."})` for custom call traces.
-
-      Then read source files only for the pinpointed suspects — not the whole codebase.
-
-      ### Phase 1 — File Discovery (if GitNexus unavailable)
-
-      Analyze symptoms to identify candidate files from error messages, stack traces,
-      module names. Use grep/find to locate relevant code.
-
-      ### Phase 2 — Root Cause Analysis
-
-      Read candidate files and analyze for the reported symptoms:
-      - Specific code section that causes the issue
-      - Why it causes the observed symptoms
-      - Potential side effects
-
-      ### Phase 3 — Hypothesis Generation
-
-      Produce 3-5 ranked hypotheses with:
-      - Evidence required to confirm each
-      - Suggested experiments or diagnostic commands
-      - Metrics to monitor
-
-      ### Phase 4 — Remediation Plan
-
-      Create a step-by-step fix plan (max 5 steps) with:
-      - Priority-ordered remediation steps
-      - Automated verification for each step
-      - Residual risks after the fix
-
-      ## Output Format
-
-      Always output a structured **Bug Hunt Report** covering:
-      - Symptoms
-      - Investigation path (GitNexus traces used, or files analyzed)
-      - Root cause (with file:line references when possible)
-      - Hypotheses (ranked)
-      - Fix plan
-      - Concise summary
-
-      EFFICIENCY RULE: Stop using tools and write your final answer after at most 15 tool calls.
-
-    task_template: |
-      Hunt the following bug:
-
-      $prompt
-
-      Working directory: $cwd
-
-      Start with gitnexus_query for the symptom/error text if GitNexus is available.
-      Then trace call chains with gitnexus_context. Read source files for pinpointed suspects.
-      Fall back to grep/find if GitNexus is unavailable. Produce a full Bug Hunt Report.
-
-  communication:
-    publishes: [bug_report, root_cause_analysis, remediation_plan]