原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

SpecMgr

作者:dfch版本 0.38.0i★ 2 (整个仓库的星标)i在你的电脑上运行
注册名称io.github.dfch/biz-dfch-specmgr

安装方法

What it does

An artifact manager for system specifications.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 其他

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

  1. 安装 Python (uv)

    只需一次,所有需要 Python (uv) 的服务器都能用

    打开 Python (uv) 下载页 ↗

  2. 打开电脑版 Claude 应用的设置文件

    SettingsDeveloperEdit Config

  3. 粘贴这些设置并保存文件

    {
      "mcpServers": {
        "biz-dfch-specmgr": {
          "command": "uvx",
          "args": [
            "biz-dfch-specmgr",
            "-m",
            "biz.dfch.specmgr",
            "mcp"
          ]
        }
      }
    }
  4. 退出 Claude 再重新打开

  5. 试一试

    用 SpecMgr 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 SpecMgr,或回答中出现 SpecMgr 的工具名称,就表示连接成功

14 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • SPECMGR_MCP_TRANSPORT MCP 服务器的传输模式。
    查看英文原文Transport mode for the MCP server.
    · 默认值 stdio
  • SPECMGR_MCP_HOST Bind address, SSE/streamable-http mode only. · 默认值 localhost
  • SPECMGR_MCP_PORT TCP port, SSE/streamable-http mode only. · 默认值 8000
  • SPECMGR_ADR_DIR Base directory scanned for Architecture Decision Record (.md) files. · 默认值 docs/adr
  • SPECMGR_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'… · 默认值 docs
  • SPECMGR_FEAT_DIR Base directory scanned for Feature folders ( / /README.md). · 默认值 .specmgr/feat
  • SPECMGR_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… · 默认值 40
  • SPECMGR_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 的应用

  • 需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
  • 需要先在电脑上安装 Python (uv)(只需一次)
  • 需要先在电脑上安装 Python (uv)(只需一次)
  • 需要先在电脑上安装 Python (uv)(只需一次)

B · 其他 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code,但需要先准备

需要先在电脑上安装 Python (uv)(只需一次)

  1. 安装 Python (uv)

    只需一次,所有需要 Python (uv) 的服务器都能用

    打开 Python (uv) 下载页 ↗

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --scope user biz-dfch-specmgr -- uvx biz-dfch-specmgr -m biz.dfch.specmgr mcp
  4. 在 Claude Code 中输入 /mcp

    应能看到 SpecMgr 在列表中并显示已连接

  5. 试一试

    用 SpecMgr 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 SpecMgr,或回答中出现 SpecMgr 的工具名称,就表示连接成功

14 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • SPECMGR_MCP_TRANSPORT MCP 服务器的传输模式。
    查看英文原文Transport mode for the MCP server.
    · 默认值 stdio
  • SPECMGR_MCP_HOST Bind address, SSE/streamable-http mode only. · 默认值 localhost
  • SPECMGR_MCP_PORT TCP port, SSE/streamable-http mode only. · 默认值 8000
  • SPECMGR_ADR_DIR Base directory scanned for Architecture Decision Record (.md) files. · 默认值 docs/adr
  • SPECMGR_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'… · 默认值 docs
  • SPECMGR_FEAT_DIR Base directory scanned for Feature folders ( / /README.md). · 默认值 .specmgr/feat
  • SPECMGR_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… · 默认值 40
  • SPECMGR_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)(只需一次)

  1. 安装 Python (uv)

    只需一次,所有需要 Python (uv) 的服务器都能用

    打开 Python (uv) 下载页 ↗

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 在 Cursor 中以 Agent 模式打开 AI 聊天

  4. 试一试

    用 SpecMgr 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 SpecMgr,或回答中出现 SpecMgr 的工具名称,就表示连接成功

14 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • SPECMGR_MCP_TRANSPORT MCP 服务器的传输模式。
    查看英文原文Transport mode for the MCP server.
    · 默认值 stdio
  • SPECMGR_MCP_HOST Bind address, SSE/streamable-http mode only. · 默认值 localhost
  • SPECMGR_MCP_PORT TCP port, SSE/streamable-http mode only. · 默认值 8000
  • SPECMGR_ADR_DIR Base directory scanned for Architecture Decision Record (.md) files. · 默认值 docs/adr
  • SPECMGR_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'… · 默认值 docs
  • SPECMGR_FEAT_DIR Base directory scanned for Feature folders ( / /README.md). · 默认值 .specmgr/feat
  • SPECMGR_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… · 默认值 40
  • SPECMGR_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)(只需一次)

  1. 安装 Python (uv)

    只需一次,所有需要 Python (uv) 的服务器都能用

    打开 Python (uv) 下载页 ↗

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 在 VS Code 中以 Agent 模式打开 AI 聊天

  4. 试一试

    用 SpecMgr 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 SpecMgr,或回答中出现 SpecMgr 的工具名称,就表示连接成功

14 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • SPECMGR_MCP_TRANSPORT MCP 服务器的传输模式。
    查看英文原文Transport mode for the MCP server.
    · 默认值 stdio
  • SPECMGR_MCP_HOST Bind address, SSE/streamable-http mode only. · 默认值 localhost
  • SPECMGR_MCP_PORT TCP port, SSE/streamable-http mode only. · 默认值 8000
  • SPECMGR_ADR_DIR Base directory scanned for Architecture Decision Record (.md) files. · 默认值 docs/adr
  • SPECMGR_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'… · 默认值 docs
  • SPECMGR_FEAT_DIR Base directory scanned for Feature folders ( / /README.md). · 默认值 .specmgr/feat
  • SPECMGR_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… · 默认值 40
  • SPECMGR_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 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 SpecMgr 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

安装在电脑上

Claude Code

claude mcp add --scope user biz-dfch-specmgr -- uvx biz-dfch-specmgr -m biz.dfch.specmgr mcp

Claude 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 env
    MCP 服务器的传输模式。
    查看英文原文Transport mode for the MCP server.
  • SPECMGR_MCP_HOST env
    Bind address, SSE/streamable-http mode only.
  • SPECMGR_MCP_PORT env
    TCP port, SSE/streamable-http mode only.
  • SPECMGR_ADR_DIR env
    Base directory scanned for Architecture Decision Record (.md) files.
  • SPECMGR_DOCS_DIR env
    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'…
  • SPECMGR_FEAT_DIR env
    Base directory scanned for Feature folders ( / /README.md).
  • SPECMGR_SIMILARITY_DISABLED env
    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 env
    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 env
    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 env
    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 env
    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 env
    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…
  • SPECMGR_TESTS_NO_DOTENV env
    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 env
    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…

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

GitHub 星标i
2 (整个仓库的星标)
该仓库包含多个 MCP 条目,星标在排名中只计算一次
每周下载量i
249/周
许可证i
AGPL-3.0
连接方式
在你的电脑上运行
最新版本i
0.38.0
分类i
其他
发布到注册中心i
2026年11月1日
代码最后更新i
2026年11月14日
作者
dfch
软件包
pypi: biz-dfch-specmgr
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月14日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 dfch 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • ✓ 通过

    有许可证

    使用 AGPL-3.0

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

使用 Google 登录后发帖

用户评价

还没有评价

用 Google 登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 19780 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 19780 个服务器的 75% 更新
  • 基础检查结果等于或优于此分类中其他 19780 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

SpecMgr 安全吗?

它在 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

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

作者:koala73广泛使用★ 9.1万今天更新

在云端运行✓ 服务方 · worldmonitor.app

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

作者:ruvnet广泛使用↓ 1.4万/周★ 8.2万14个月前更新

在你的电脑上运行

Windmill

Run Windmill scripts and flows and manage jobs, schedules, resources and variables.

作者:windmill-labs广泛使用★ 1.9万前天更新

在云端运行

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

biz.dfch.SpecMgr

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).

Table of Contents

  • Concepts
  • Installation
  • CLI Usage
  • UC → PlantUML Diagrams
  • Reference Graph Diagrams
  • MCP Server
  • Installing the specmgr Harness Files
  • Usage
  • Referencing Artifacts
  • Multi-Language Artifacts
  • Development
  • Testing
  • Make a Release
  • License

Concepts

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).

TypePurpose
QA — Question and AnswerStructured elicitation interview (organized by ISO/IEC 25010 characteristic) capturing stakeholder Q&A; usually where a new spec effort *starts*
GOL — GoalHigh-level business goal — what the organization wants to achieve, above individual requirements
PRB — Problem StatementSix-Sigma-style problem statement describing the problem a goal/requirement addresses
REQ — RequirementA single system requirement (EARS-style phrasing), classified by ISO/IEC 25010 characteristic
UC — Use CaseActor/system interaction describing a specific usage scenario
RSK — RiskRisk-register entry: cause/trigger/consequence, 5x5 probability/impact assessment (initial + residual), TARA response strategy
DEC — DecisionGeneral-purpose decision record (MADR-style), not limited to architecture
ADR — Architecture Decision RecordArchitecture-specific decision record; deprecated, use DEC instead
TSK — Task ListChecklist of implementation tasks, e.g. for a requirement or feature
VCR — Verification Case RecordVerifies 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 ProcedureStep-by-step operational procedure with RASCI responsibility assignment and approval lifecycle
FEAT — FeatureDevelopment work-unit plan/progress tracking (.specmgr/feat/ /README.md)
SYSRS — System Requirements SpecAggregates 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 TextGeneric, 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)

Installation

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]"

CLI Usage

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).

UC → PlantUML Diagrams

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.

Reference Graph Diagrams

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

只显示了开头部分;其余内容请在仓库中阅读