/octave:audit - Library Health Check

/octave:audit - 库健康检查

Comprehensive audit of your Octave GTM library to identify gaps, stale content, duplicates, and inconsistencies.

对你的Octave GTM库进行全面审计，识别内容缺口、过时内容、重复项和不一致问题。

Usage

使用方法

/octave:audit [--type <entity-type>] [--fix]

/octave:audit [--type <entity-type>] [--fix]

Options

选项说明

```
--type <type>
```
- Focus on specific entity type (personas, playbooks, products, segments, etc.)
```
--fix
```
- Interactive mode to address issues as they're found
```
--detailed
```
- Show full details for each issue (default: summary view)

```
--type <type>
```
- 聚焦特定实体类型（personas、playbooks、products、segments等）
```
--fix
```
- 交互模式，发现问题时可直接处理
```
--detailed
```
- 展示每个问题的完整详情（默认：摘要视图）

Instructions

使用说明

When the user runs

/octave:audit

:

当用户运行

/octave:audit

时：

Step 1: Gather Library State

步骤1：收集库状态

Resolve Octave MCP server first: The Octave MCP server provides tools like

verify_connection

,

get_entity

,

list_all_entities

. From your tool list, get the server name (e.g.

octave-acme

).

Fetch entities using MCP tools:

1. list_all_entities({ entityType: "persona" })
2. list_all_entities({ entityType: "product" })
3. list_all_entities({ entityType: "playbook" })
4. list_all_entities({ entityType: "segment" })
5. list_all_entities({ entityType: "use_case" })
6. list_all_entities({ entityType: "competitor" })
7. list_all_entities({ entityType: "proof_point" })
8. list_all_entities({ entityType: "reference" })

If

--type

is specified, only fetch that type (but still need related types for relationship checks).

首先确认Octave MCP服务器： Octave MCP服务器提供

verify_connection

、

get_entity

、

list_all_entities

等工具。从你的工具列表中获取服务器名称（例如

octave-acme

）。

使用MCP工具拉取实体：

1. list_all_entities({ entityType: "persona" })
2. list_all_entities({ entityType: "product" })
3. list_all_entities({ entityType: "playbook" })
4. list_all_entities({ entityType: "segment" })
5. list_all_entities({ entityType: "use_case" })
6. list_all_entities({ entityType: "competitor" })
7. list_all_entities({ entityType: "proof_point" })
8. list_all_entities({ entityType: "reference" })

如果指定了

--type

参数，则仅拉取对应类型的实体（但仍需拉取关联类型用于关系校验）。

Step 2: Run Audit Checks

步骤2：执行审计检查

Perform the following checks and categorize issues by severity:

执行以下检查，并按严重程度对问题进行分类：

Coverage Checks (CRITICAL)

覆盖度检查（严重）

Missing Core Entities:

At least 1 product or service defined
At least 1 persona defined
At least 1 playbook defined

Orphaned Playbooks:

Every playbook has at least 1 buyer persona linked
Every playbook has a primary product linked
Playbooks have value props for their linked personas

Broken References:

Personas referenced in playbooks exist
Products referenced in playbooks exist
Use cases referenced exist

缺失核心实体：

至少定义了1个产品或服务
至少定义了1个persona
至少定义了1个playbook

孤立Playbooks：

每个playbook至少关联1个买方persona
每个playbook关联了核心产品
Playbooks包含对应关联persona的价值主张

引用失效：

Playbooks中引用的persona真实存在
Playbooks中引用的产品真实存在
引用的用例真实存在

Completeness Checks (WARNING)

完整性检查（警告）

Freshness Checks (INFO)

新鲜度检查（提示）

Entities updated within last 90 days (flag if older)
Playbooks reviewed within last 60 days
Competitor info updated within last 30 days (competitive intel goes stale fast)

实体在过去90天内有更新（超过则标记）
Playbooks在过去60天内有审核
竞争对手信息在过去30天内有更新（竞争情报时效性很强）

Duplicate Detection (WARNING)

重复项检测（警告）

Name Similarity:

Personas with similar names (>80% similarity)
Products with similar names
Use cases with similar names
Segments with overlapping descriptions

Content Overlap:

Personas with very similar pain points
Use cases with near-identical descriptions
Playbooks targeting same persona+segment combination

名称相似度：

Persona名称相似度>80%
产品名称相似度高
用例名称相似度高
细分群体描述重叠

内容重叠：

Persona痛点高度相似
用例描述几乎完全一致
Playbooks targeting same persona+segment combination

Consistency Checks (WARNING)

一致性检查（警告）

Messaging Alignment:

Product differentiators mentioned in related playbooks
Persona pain points addressed in playbook value props
Proof points support claims made in playbooks

Taxonomy Health:

Segments have associated use cases
Use cases link to products
References link to products and use cases

信息对齐：

产品差异化优势在关联playbook中被提及
Persona痛点在playbook价值主张中得到回应
佐证案例支撑playbook中的宣称

分类体系健康度：

细分群体有关联用例
用例关联到对应产品
参考案例关联到对应产品和用例

Step 3: Generate Report

步骤3：生成报告

Present findings organized by severity:

Library Audit Report
====================
Generated: <timestamp>
MCP Server: <mcpServerName>

Summary
-------
Total Entities: <count>
  - Personas: X
  - Products: X
  - Playbooks: X
  - Segments: X
  - Use Cases: X
  - Competitors: X
  - Proof Points: X
  - References: X

Health Score: X/100

Issues Found: X total
  - Critical: X
  - Warning: X
  - Info: X

---

CRITICAL ISSUES (X)
===================

1. [ORPHAN] Playbook "Enterprise Sales" has no linked personas
   oId: pb_abc123
   Impact: Cannot generate persona-specific messaging
   Fix: Link buyer personas to this playbook

2. [MISSING] No proof points defined
   Impact: Cannot support claims with evidence
   Fix: Add at least 3-5 proof points with metrics

---

WARNINGS (X)
============

1. [INCOMPLETE] Persona "CTO" missing pain points
   oId: pe_def456
   Fields missing: painPoints, keyObjectives
   Fix: Add pain points and objectives

2. [DUPLICATE] Similar personas detected
   - "VP of Sales" (pe_111)
   - "Vice President of Sales" (pe_222)
   Similarity: 92%
   Fix: Consider merging these personas

3. [STALE] Competitor "Acme Corp" not updated in 120 days
   oId: cp_xyz789
   Last updated: 2025-10-01
   Fix: Review and refresh competitive intelligence

---

INFO (X)
========

1. [FRESHNESS] 5 entities not updated in 90+ days
   - Persona "CFO" (95 days)
   - Use Case "Compliance" (102 days)
   - ...

---

Recommendations
===============

1. IMMEDIATE: Link personas to orphaned playbooks
2. HIGH: Add pain points to incomplete personas
3. MEDIUM: Review and merge duplicate entities
4. LOW: Refresh stale content

Run /octave:audit --fix to address issues interactively.

按严重程度整理展示审计结果：

Library Audit Report
====================
Generated: <timestamp>
MCP Server: <mcpServerName>

Summary
-------
Total Entities: <count>
  - Personas: X
  - Products: X
  - Playbooks: X
  - Segments: X
  - Use Cases: X
  - Competitors: X
  - Proof Points: X
  - References: X

Health Score: X/100

Issues Found: X total
  - Critical: X
  - Warning: X
  - Info: X

---

CRITICAL ISSUES (X)
===================

1. [ORPHAN] Playbook "Enterprise Sales" has no linked personas
   oId: pb_abc123
   Impact: Cannot generate persona-specific messaging
   Fix: Link buyer personas to this playbook

2. [MISSING] No proof points defined
   Impact: Cannot support claims with evidence
   Fix: Add at least 3-5 proof points with metrics

---

WARNINGS (X)
============

1. [INCOMPLETE] Persona "CTO" missing pain points
   oId: pe_def456
   Fields missing: painPoints, keyObjectives
   Fix: Add pain points and objectives

2. [DUPLICATE] Similar personas detected
   - "VP of Sales" (pe_111)
   - "Vice President of Sales" (pe_222)
   Similarity: 92%
   Fix: Consider merging these personas

3. [STALE] Competitor "Acme Corp" not updated in 120 days
   oId: cp_xyz789
   Last updated: 2025-10-01
   Fix: Review and refresh competitive intelligence

---

INFO (X)
========

1. [FRESHNESS] 5 entities not updated in 90+ days
   - Persona "CFO" (95 days)
   - Use Case "Compliance" (102 days)
   - ...

---

Recommendations
===============

1. IMMEDIATE: Link personas to orphaned playbooks
2. HIGH: Add pain points to incomplete personas
3. MEDIUM: Review and merge duplicate entities
4. LOW: Refresh stale content

Run /octave:audit --fix to address issues interactively.

Step 4: Interactive Fix Mode (--fix)

步骤4：交互修复模式（--fix）

If

--fix

flag is provided, walk through each issue:

Issue 1 of 12: [INCOMPLETE] Persona "CTO" missing pain points
oId: pe_def456

Current state:
- Pain Points: (empty)
- Objectives: (empty)
- Description: "Chief Technology Officer..."

Options:
1. Add content now (I'll help you write it)
2. Generate with AI (uses your library context)
3. Skip for now
4. Mark as intentional (won't flag in future)

Your choice:

If user chooses "Generate with AI":

update_entity({
  entityType: "persona",
  oId: "pe_def456",
  instructions: "Add typical CTO pain points and objectives based on the existing library context. Focus on technology leadership challenges, budget management, and digital transformation."
})

If user chooses "Add content now": Prompt for the specific content and use

update_entity

to apply.

如果提供了

--fix

参数，将逐个引导处理问题：

Issue 1 of 12: [INCOMPLETE] Persona "CTO" missing pain points
oId: pe_def456

Current state:
- Pain Points: (empty)
- Objectives: (empty)
- Description: "Chief Technology Officer..."

Options:
1. Add content now (I'll help you write it)
2. Generate with AI (uses your library context)
3. Skip for now
4. Mark as intentional (won't flag in future)

Your choice:

如果用户选择「Generate with AI」：

update_entity({
  entityType: "persona",
  oId: "pe_def456",
  instructions: "Add typical CTO pain points and objectives based on the existing library context. Focus on technology leadership challenges, budget management, and digital transformation."
})

如果用户选择「Add content now」： 提示用户输入具体内容，使用

update_entity

接口提交更新。

Step 5: Duplicate Resolution Flow

步骤5：重复项处理流程

When duplicates are detected:

Potential Duplicates Detected
=============================

Group 1: Sales Leadership Personas
----------------------------------
A) "VP of Sales" (pe_111)
   Created: 2025-06-01
   Pain Points: 5 defined
   Used in: 3 playbooks

B) "Vice President of Sales" (pe_222)
   Created: 2025-08-15
   Pain Points: 2 defined
   Used in: 1 playbook

Similarity: 92% (based on name and content)

Options:
1. Merge B into A (keep A, archive B, update references)
2. Merge A into B (keep B, archive A, update references)
3. Keep both (they represent different personas)
4. Review side-by-side before deciding

Your choice:

Note: Actual merging requires manual updates in Octave UI or multiple API calls. The skill should:

Recommend which to keep
List what needs to be updated
Offer to archive the duplicate

检测到重复项时：

Potential Duplicates Detected
=============================

Group 1: Sales Leadership Personas
----------------------------------
A) "VP of Sales" (pe_111)
   Created: 2025-06-01
   Pain Points: 5 defined
   Used in: 3 playbooks

B) "Vice President of Sales" (pe_222)
   Created: 2025-08-15
   Pain Points: 2 defined
   Used in: 1 playbook

Similarity: 92% (based on name and content)

Options:
1. Merge B into A (keep A, archive B, update references)
2. Merge A into B (keep B, archive A, update references)
3. Keep both (they represent different personas)
4. Review side-by-side before deciding

Your choice:

注意： 实际合并需要在Octave UI中手动更新或调用多次API。该功能会：

推荐保留哪一个实体
列出需要更新的内容
提供归档重复项的选项

Health Score Calculation

健康得分计算规则

Base Score: 100

Deductions:
- Critical issue: -15 points each (max -45)
- Warning: -5 points each (max -30)
- Info: -1 point each (max -10)

Bonuses:
- All entity types have content: +5
- No stale content (>90 days): +5
- All playbooks fully linked: +5

Minimum score: 0
Maximum score: 100

Score Interpretation:

90-100: Excellent - Library is well-maintained
70-89: Good - Minor issues to address
50-69: Fair - Several gaps need attention
Below 50: Needs Work - Significant gaps affecting effectiveness

Base Score: 100

Deductions:
- Critical issue: -15 points each (max -45)
- Warning: -5 points each (max -30)
- Info: -1 point each (max -10)

Bonuses:
- All entity types have content: +5
- No stale content (>90 days): +5
- All playbooks fully linked: +5

Minimum score: 0
Maximum score: 100

得分说明：

90-100：优秀 - 库维护状态良好
70-89：良好 - 存在少量需要处理的问题
50-69：一般 - 存在多个需要关注的缺口
低于50：需要优化 - 存在大量影响有效性的缺口

MCP Tools Used

使用的MCP工具

Read Operations

读操作

```
list_all_entities
```
- Get all entities of each type
```
get_entity
```
- Get full details for specific entities
```
get_playbook
```
- Get playbook with linked personas and value props
```
list_value_props
```
- Check value prop coverage

```
list_all_entities
```
- 获取每个类型的所有实体
```
get_entity
```
- 获取特定实体的完整详情
```
get_playbook
```
- 获取playbook以及关联的persona和价值主张
```
list_value_props
```
- 检查价值主张覆盖度

Write Operations (--fix mode only)

写操作（仅--fix模式下使用）

```
update_entity
```
- Fix incomplete entities
```
add_value_props
```
- Add missing value props

```
update_entity
```
- 修复不完整的实体
```
add_value_props
```
- 补充缺失的价值主张

Examples

示例

Basic Audit

基础审计

/octave:audit

Runs full audit and displays report.

/octave:audit

执行全量审计并展示报告。

Focused Audit

定向审计

/octave:audit --type personas

Audits only personas (completeness, duplicates, staleness).

/octave:audit --type personas

仅审计persona（完整性、重复项、新鲜度）。

Interactive Fix

交互修复

/octave:audit --fix

Runs audit then walks through each issue for resolution.

/octave:audit --fix

执行审计后逐个引导处理发现的问题。

Error Handling

错误处理

Empty Library:

Your library is empty. Start creating entities with /octave:library create.

API Error:

Could not fetch library data. Check your connection and try again. If the issue persists, verify your workspace with /octave:workspace.

空库：

你的库为空。可以使用
/octave:library create
开始创建实体。

API错误：

无法拉取库数据。请检查你的连接并重试。如果问题持续存在，可以使用
/octave:workspace
校验你的工作区配置。

audit

Original

Translation