World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
An artifact manager for system specifications.
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
SettingsDeveloperEdit Config
{
"mcpServers": {
"biz-dfch-specmgr": {
"command": "uvx",
"args": [
"biz-dfch-specmgr",
"-m",
"biz.dfch.specmgr",
"mcp"
]
}
}
}用 SpecMgr 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 SpecMgr,或回答中出现 SpecMgr 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SPECMGR_MCP_TRANSPORT MCP 服务器的传输模式。 SPECMGR_MCP_HOST Bind address, SSE/streamable-http mode only. · 默认值 localhostSPECMGR_MCP_PORT TCP port, SSE/streamable-http mode only. · 默认值 8000SPECMGR_ADR_DIR Base directory scanned for Architecture Decision Record (.md) files. · 默认值 docs/adrSPECMGR_DOCS_DIR Shared base directory root for the document-type domains that do not have their own dedicated directory environment variable (req, uc, tsk, qa, prb, gol, rsk, dec, sop, vcr, sysrs, txt). Each domain'… · 默认值 docsSPECMGR_FEAT_DIR Base directory scanned for Feature folders ( / /README.md). · 默认值 .specmgr/featSPECMGR_SIMILARITY_DISABLED Presence-based opt-out for the semantic-similarity search feature (the find_related and find_similar_text tools): set to any value to disable the feature, so that every call returns a structured unav…SPECMGR_FEAT_WARMUP_DISABLED Presence-based opt-out for the feat domain's two background cache-warming phases (frontmatter and full-parse) of the unified server-startup warmup thread: set to any value to skip both phases; when s…SPECMGR_PLANTUML_JAR Path to a plantuml.jar, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fall-through, no PATH discovery, no p…SPECMGR_PLANTUML_BIN Path to an executable speaking the PlantUML CLI contract, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fal…SPECMGR_PLANTUML_URL PlantUML server base URL, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fall-through, no PATH discovery, no…SPECMGR_DIAGRAM_MAX_TITLE Maximum length (in characters) of a resolved node's title label in the reference-graph diagrams (the get_reference_diagram / get_reference_diagram_all MCP tools and the specmgr diagram refs CLI): lab… · 默认值 40SPECMGR_TESTS_NO_DOTENV Presence-based test/CI sentinel: set to any value to skip the CLI's module-level default .env load entirely, so the process runs under the CI (source-less) condition whatever the local (gitignored) .…FASTEMBED_CACHE_PATH Cache directory for the semantic-similarity feature's embedding model (the third-party fastembed backend's own variable, not a SPECMGR_* one): set to a directory to cache the model there; an unset or… · 默认值 /fastembed_cache说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 SpecMgr
SpecMgr 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 SpecMgr 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user biz-dfch-specmgr -- uvx biz-dfch-specmgr -m biz.dfch.specmgr mcp应能看到 SpecMgr 在列表中并显示已连接
用 SpecMgr 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 SpecMgr,或回答中出现 SpecMgr 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SPECMGR_MCP_TRANSPORT MCP 服务器的传输模式。 SPECMGR_MCP_HOST Bind address, SSE/streamable-http mode only. · 默认值 localhostSPECMGR_MCP_PORT TCP port, SSE/streamable-http mode only. · 默认值 8000SPECMGR_ADR_DIR Base directory scanned for Architecture Decision Record (.md) files. · 默认值 docs/adrSPECMGR_DOCS_DIR Shared base directory root for the document-type domains that do not have their own dedicated directory environment variable (req, uc, tsk, qa, prb, gol, rsk, dec, sop, vcr, sysrs, txt). Each domain'… · 默认值 docsSPECMGR_FEAT_DIR Base directory scanned for Feature folders ( / /README.md). · 默认值 .specmgr/featSPECMGR_SIMILARITY_DISABLED Presence-based opt-out for the semantic-similarity search feature (the find_related and find_similar_text tools): set to any value to disable the feature, so that every call returns a structured unav…SPECMGR_FEAT_WARMUP_DISABLED Presence-based opt-out for the feat domain's two background cache-warming phases (frontmatter and full-parse) of the unified server-startup warmup thread: set to any value to skip both phases; when s…SPECMGR_PLANTUML_JAR Path to a plantuml.jar, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fall-through, no PATH discovery, no p…SPECMGR_PLANTUML_BIN Path to an executable speaking the PlantUML CLI contract, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fal…SPECMGR_PLANTUML_URL PlantUML server base URL, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fall-through, no PATH discovery, no…SPECMGR_DIAGRAM_MAX_TITLE Maximum length (in characters) of a resolved node's title label in the reference-graph diagrams (the get_reference_diagram / get_reference_diagram_all MCP tools and the specmgr diagram refs CLI): lab… · 默认值 40SPECMGR_TESTS_NO_DOTENV Presence-based test/CI sentinel: set to any value to skip the CLI's module-level default .env load entirely, so the process runs under the CI (source-less) condition whatever the local (gitignored) .…FASTEMBED_CACHE_PATH Cache directory for the semantic-similarity feature's embedding model (the third-party fastembed backend's own variable, not a SPECMGR_* one): set to a directory to cache the model there; an unset or… · 默认值 /fastembed_cache说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
用 SpecMgr 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 SpecMgr,或回答中出现 SpecMgr 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SPECMGR_MCP_TRANSPORT MCP 服务器的传输模式。 SPECMGR_MCP_HOST Bind address, SSE/streamable-http mode only. · 默认值 localhostSPECMGR_MCP_PORT TCP port, SSE/streamable-http mode only. · 默认值 8000SPECMGR_ADR_DIR Base directory scanned for Architecture Decision Record (.md) files. · 默认值 docs/adrSPECMGR_DOCS_DIR Shared base directory root for the document-type domains that do not have their own dedicated directory environment variable (req, uc, tsk, qa, prb, gol, rsk, dec, sop, vcr, sysrs, txt). Each domain'… · 默认值 docsSPECMGR_FEAT_DIR Base directory scanned for Feature folders ( / /README.md). · 默认值 .specmgr/featSPECMGR_SIMILARITY_DISABLED Presence-based opt-out for the semantic-similarity search feature (the find_related and find_similar_text tools): set to any value to disable the feature, so that every call returns a structured unav…SPECMGR_FEAT_WARMUP_DISABLED Presence-based opt-out for the feat domain's two background cache-warming phases (frontmatter and full-parse) of the unified server-startup warmup thread: set to any value to skip both phases; when s…SPECMGR_PLANTUML_JAR Path to a plantuml.jar, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fall-through, no PATH discovery, no p…SPECMGR_PLANTUML_BIN Path to an executable speaking the PlantUML CLI contract, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fal…SPECMGR_PLANTUML_URL PlantUML server base URL, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fall-through, no PATH discovery, no…SPECMGR_DIAGRAM_MAX_TITLE Maximum length (in characters) of a resolved node's title label in the reference-graph diagrams (the get_reference_diagram / get_reference_diagram_all MCP tools and the specmgr diagram refs CLI): lab… · 默认值 40SPECMGR_TESTS_NO_DOTENV Presence-based test/CI sentinel: set to any value to skip the CLI's module-level default .env load entirely, so the process runs under the CI (source-less) condition whatever the local (gitignored) .…FASTEMBED_CACHE_PATH Cache directory for the semantic-similarity feature's embedding model (the third-party fastembed backend's own variable, not a SPECMGR_* one): set to a directory to cache the model there; an unset or… · 默认值 /fastembed_cache说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
用 SpecMgr 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 SpecMgr,或回答中出现 SpecMgr 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SPECMGR_MCP_TRANSPORT MCP 服务器的传输模式。 SPECMGR_MCP_HOST Bind address, SSE/streamable-http mode only. · 默认值 localhostSPECMGR_MCP_PORT TCP port, SSE/streamable-http mode only. · 默认值 8000SPECMGR_ADR_DIR Base directory scanned for Architecture Decision Record (.md) files. · 默认值 docs/adrSPECMGR_DOCS_DIR Shared base directory root for the document-type domains that do not have their own dedicated directory environment variable (req, uc, tsk, qa, prb, gol, rsk, dec, sop, vcr, sysrs, txt). Each domain'… · 默认值 docsSPECMGR_FEAT_DIR Base directory scanned for Feature folders ( / /README.md). · 默认值 .specmgr/featSPECMGR_SIMILARITY_DISABLED Presence-based opt-out for the semantic-similarity search feature (the find_related and find_similar_text tools): set to any value to disable the feature, so that every call returns a structured unav…SPECMGR_FEAT_WARMUP_DISABLED Presence-based opt-out for the feat domain's two background cache-warming phases (frontmatter and full-parse) of the unified server-startup warmup thread: set to any value to skip both phases; when s…SPECMGR_PLANTUML_JAR Path to a plantuml.jar, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fall-through, no PATH discovery, no p…SPECMGR_PLANTUML_BIN Path to an executable speaking the PlantUML CLI contract, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fal…SPECMGR_PLANTUML_URL PlantUML server base URL, one of exactly three PlantUML validation-source selectors (the first one set, in JAR then BIN then URL order, is the only source used; no fall-through, no PATH discovery, no…SPECMGR_DIAGRAM_MAX_TITLE Maximum length (in characters) of a resolved node's title label in the reference-graph diagrams (the get_reference_diagram / get_reference_diagram_all MCP tools and the specmgr diagram refs CLI): lab… · 默认值 40SPECMGR_TESTS_NO_DOTENV Presence-based test/CI sentinel: set to any value to skip the CLI's module-level default .env load entirely, so the process runs under the CI (source-less) condition whatever the local (gitignored) .…FASTEMBED_CACHE_PATH Cache directory for the semantic-similarity feature's embedding model (the third-party fastembed backend's own variable, not a SPECMGR_* one): set to a directory to cache the model there; an unset or… · 默认值 /fastembed_cache说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user biz-dfch-specmgr -- uvx biz-dfch-specmgr -m biz.dfch.specmgr mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"biz-dfch-specmgr": {
"command": "uvx",
"args": [
"biz-dfch-specmgr",
"-m",
"biz.dfch.specmgr",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"biz-dfch-specmgr": {
"command": "uvx",
"args": [
"biz-dfch-specmgr",
"-m",
"biz.dfch.specmgr",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"biz-dfch-specmgr": {
"type": "stdio",
"command": "uvx",
"args": [
"biz-dfch-specmgr",
"-m",
"biz.dfch.specmgr",
"mcp"
]
}
}
}SPECMGR_MCP_TRANSPORT envSPECMGR_MCP_HOST envSPECMGR_MCP_PORT envSPECMGR_ADR_DIR envSPECMGR_DOCS_DIR envSPECMGR_FEAT_DIR envSPECMGR_SIMILARITY_DISABLED envSPECMGR_FEAT_WARMUP_DISABLED envSPECMGR_PLANTUML_JAR envSPECMGR_PLANTUML_BIN envSPECMGR_PLANTUML_URL envSPECMGR_DIAGRAM_MAX_TITLE envSPECMGR_TESTS_NO_DOTENV envFASTEMBED_CACHE_PATH env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月14日
注册名称已通过 GitHub 账户 dfch 验证,该账户拥有此仓库
代码最后更新于今天
使用 AGPL-3.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于今天,最新版本(0.38.0)于13天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:World Monitor, Claude Flow, Windmill
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An artifact manager for system specifications.
This project is an MCP server that you can use to manage different specification artifacts — see Concepts for the full list of artifact types and how they relate, and MCP Server / docs/MCP.md for the tool/resource/prompt reference.
The MCP server (and the management CLI) are optional. You install them as "extras" (see Installation).
Every artifact is a plain markdown file with a YAML frontmatter block on disk — git-friendly, diffable, and readable/editable by hand. The filesystem is always the source of truth; the MCP server wraps it with structured, validated read/write/list/status tools (see Usage).
| Type | Purpose |
|---|---|
| QA — Question and Answer | Structured elicitation interview (organized by ISO/IEC 25010 characteristic) capturing stakeholder Q&A; usually where a new spec effort *starts* |
| GOL — Goal | High-level business goal — what the organization wants to achieve, above individual requirements |
| PRB — Problem Statement | Six-Sigma-style problem statement describing the problem a goal/requirement addresses |
| REQ — Requirement | A single system requirement (EARS-style phrasing), classified by ISO/IEC 25010 characteristic |
| UC — Use Case | Actor/system interaction describing a specific usage scenario |
| RSK — Risk | Risk-register entry: cause/trigger/consequence, 5x5 probability/impact assessment (initial + residual), TARA response strategy |
| DEC — Decision | General-purpose decision record (MADR-style), not limited to architecture |
| ADR — Architecture Decision Record | Architecture-specific decision record; deprecated, use DEC instead |
| TSK — Task List | Checklist of implementation tasks, e.g. for a requirement or feature |
| VCR — Verification Case Record | Verifies exactly one REQ or UC; holds a collection of AC-NNN acceptance criteria (each with a DTAIS verification method) plus one overall coverage outcome (full/partial/none) |
| SOP — Standard Operating Procedure | Step-by-step operational procedure with RASCI responsibility assignment and approval lifecycle |
| FEAT — Feature | Development work-unit plan/progress tracking (.specmgr/feat/ /README.md) |
| SYSRS — System Requirements Spec | Aggregates GOL/PRB/QA/UC/REQ/RSK/DEC-ADR/VCR via cross-reference lists into one navigable spec; its structure follows ISO/IEC/IEEE 29148:2018 (Systems and software engineering — Life cycle processes — Requirements engineering), with a few specmgr-only additions (e.g. ## Decisions, ## Risks) |
| TXT — Free-Form Text | Generic, minimally structured catch-all for unstructured markdown that does not warrant a dedicated domain (ad hoc notes, meeting minutes, review/audit write-ups, scratch analysis); free body (any markdown, incl. H2..H6) plus a mandatory newest-first ## Updates log |
A typical spec effort starts with a QA elicitation interview, which surfaces GOLs (goals) and PRBs (problems). Those inform REQs and UCs, which get risk-assessed (RSK) and backed by DECisions, verified via one VCR per REQ/UC (each collecting its acceptance criteria), and tracked via TSK task lists. A SYSRS ties all of it together into one ISO/IEC/IEEE 29148-structured specification. SOP and FEAT support the process itself rather than sitting in this chain, and TXT is the free-form catch-all that likewise sits outside it (any markdown that does not warrant a dedicated artifact type).
QA -> GOL / PRB -> REQ / UC -> RSK / DEC -> TSK, VCR -> SYSRS (aggregates all)
As a library only (no CLI, no MCP server):
pip install biz-dfch-specmgr
With the CLI:
pip install "biz-dfch-specmgr[cli]"
With the MCP server:
pip install "biz-dfch-specmgr[mcp]"
With semantic-similarity search (find_related/find_similar_text, see Semantic Similarity Search below), add the similarity extra on top of mcp:
pip install "biz-dfch-specmgr[mcp,similarity]"
Or with uv:
uv add "biz-dfch-specmgr[cli,mcp,similarity]"
With the CLI you can generate schema and documentation. We use these commands in pre-commit hooks and ci.yml.
_No domain document-management commands (create/update/status/etc.) exist in the CLI yet — those are currently MCP-only, see MCP Server. The CLI covers version, mcp (below), a handful of cross-cutting/doc-generation commands, and the diagram commands — UC → PlantUML (see UC → PlantUML Diagrams) and reference-graph (see Reference Graph Diagrams) (specmgr --help for the full list)._
specmgr version
specmgr lint [paths]... [--type T [--dir D]] [--all] [--skip-unrecognized] # in-tree spec artifact parseability gate: full model-level parse of the paths (type inferred from the layout, --type overrides) or a --type/--all sweep (exit 0 parsed / 1 parse failure or missing mcp extra / 2 usage-or-resolution)
specmgr lint requires the mcp extra, like specmgr diagram (the decoupling is tracked as issue #238).
Specmgr can turn UC artifacts into PlantUML diagrams — deterministic use-case and package diagrams, plus sequence diagrams attributed by the agent flow.
Sequence diagrams (agent path). The generate_uc_sequence_diagram MCP prompt (in OpenCode: the self-triggering uc-diagram skill or the /uc-diagram command) runs the frozen rulebook flow: the agent attributes every UNATTRIBUTED message (asking via the question tool when not confident), validates with validate_plantuml, and writes diagrams/uc/ .sequence.puml host-natively — no specmgr tool writes .puml files.
**Deterministic diagrams + tooling (CLI, deterministic-only — the CLI never creates, overwrites, or diffs the agent-owned *.sequence.puml files):**
specmgr diagram uc <id>|all --out <dir> [--check] # per-UC <id>.usecase.puml + package.puml; --check byte-diffs without writing (exit 0 ok / 1 diff / 2 usage-or-render error)
specmgr plantuml-check # validates any .puml through the chain (exit 0 valid / 1 invalid / 2 source misconfigured-or-unavailable / 3 inconclusive) specmgr plantuml-encode # offline classic SoWkI… encoding
Validation source. Exactly three env vars, the first one set is the only source used (no fall-through, no PATH discovery, no public default): SPECMGR_PLANTUML_JAR (a plantuml.jar path), SPECMGR_PLANTUML_BIN (an executable speaking the PlantUML CLI contract), SPECMGR_PLANTUML_URL (a PlantUML server base URL). All unset ⇒ offline structure-only validation. Diagram content is never sent to plantuml.com unless you set that URL.
The normative rulebook ships as the specmgr://uc/plantuml resource; the full MCP surface is in docs/MCP.md.
Specmgr can render the deterministic cross-reference network between its artifacts (the tag vocabulary behind the list_references tool) as a PlantUML component diagram — one node per artifact (label = the document title, truncated to the SPECMGR_DIAGRAM_MAX_TITLE limit, default 40), a stereotype + colour per artifact type (a frozen 15-entry palette), nodes grouped into per-domain curly component "TYPE" { … } domain groups, one label-free edge per unique reference ({src} --> {dst}), every edge that lies on a cycle (self-loops and same-SCC ≥ 2) drawn with a red label-free -[#red]-> arrow, and every reference whose target cannot be resolved on disk drawn as a top-level < > node. Fully deterministic: the same registry and the same arguments always emit byte-identical source.
MCP tools. get_reference_diagram(type, id, depth=1, reverse=False, include_feat=True, title=None) renders one source document's reference neighbourhood (the forward walk to depth, 1..5; reverse=True adds the direct incoming references, additive and direct-only); get_reference_diagram_all(include_feat=True, title=None) renders the registry-wide graph. Both return the PlantUML source directly (no file writes); the scoped tool accepts all 14 domains (adr included) and returns the non-raising ParseFailureResult for an existing-but-broken source; the registry-wide tool never raises for content.
CLI (writes the artifact, deterministic-only):
specmgr diagram refs <type> <id> [--depth N] [--reverse] [--no-feat] [--title T] [--out diagrams/refs] [--check] # scoped → <id>.refs.puml
specmgr diagram refs all [--no-feat] [--title T] [--out diagrams/refs] [--check] # registry-wide → reference-graph.puml
--no-feat drops every FEAT node except the explicitly requested source (then every edge touching a dropped node). Exit codes: 0 written / no diff, 1 a --check diff (a missing file counts as differing) or the missing mcp extra, 2 a usage-or-resolution error (wrong-format type/id/depth — a bare feat-NNN is rejected, use list_feat to discover the exact id — a missing source, an existing-but-broken source, all combined with a source). Written artifacts carry no structure-only header (checker-clean by construction).
Validation. specmgr plantuml-check (or the validate_plantuml MCP tool over the source) validates the diagram through the same strict chain as the UC diagrams (the three SPECMGR_PLANTUML_* source env vars, see UC → PlantUML Diagrams; all unset is the offline structure-only floor).
Label limit. SPECMGR_DIAGRAM_MAX_TITLE (an int, default 40) bounds the resolved-node H1 labels (word-boundary cut + …; a set-but-invalid value falls back to 40); the @startuml diagram title is sanitized but never truncated. Its set/valid/default/resolved status is reported by the diagram section of the specmgr://config resource (the raw value is never disclosed).
The normative rulebook ships as the specmgr://reference-graph resource; the full MCP surface is in [docs/MCP.md](doc