- CONN-CAMUNDA-MCP3
- CONN-CAMUNDA-MCP-CONNECTOR-CONTENT1
- Requirementsall slices in all specs4
- Requirements not donenot VERIFIED4
- Specs not donewhole specs only2
Each spec shows its requirement count. Panel J lists every record.
Requirements (4)
Specs (2)
Each bar shows one state against all records of the same kind.
Percentages count current rows. Done means VERIFIED.
| State | Definition |
|---|---|
| SPECIFIED | The requirement is written. No code for it is on the default branch. |
| LANDED | A commit that carries its ID in a Spec trailer is on the default branch. |
| VERIFIED | It is LANDED and a test bound to its ID exists. |
A spec state is the lowest state of its rows. Done means VERIFIED.
Invalid state: 0
| Spec / title | Req. | Landed | Done | Spec state | Code references |
|---|---|---|---|---|---|
| CONN-CAMUNDA-MCPCONN-CAMUNDA-MCP — Connector identity and release metadata | 3 | 0/3 | 0 | SPECIFIED | camunda_mcp/__init__.py implementation: file exists; coverage not verified camunda_mcp/mcp/mcp_camunda.py implementation: file exists; coverage not verified `requirements.md` documentation: file exists; coverage not verified `status.json` implementation: file exists; coverage not verified tests/test_tool_surface.py test: file exists; coverage not verified |
| CONN-CAMUNDA-MCP-CONNECTOR-CONTENTCONN-CAMUNDA-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | 1 | 1/1 | 0 | LANDED | spec.md documentation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified |
Landed counts LANDED and VERIFIED requirements. Done counts VERIFIED requirements only.
The spec state comes from the spec status file only.
Packages group specs by repository and declared component. Unassigned means no component was declared. Code links do not prove coverage. Mermaid source.
Knuckles-Team/camunda-mcp / Unassigned (2)
CONN-CAMUNDA-MCP: no plan diagram declared.
CONN-CAMUNDA-MCP-CONNECTOR-CONTENT: no plan diagram declared.
Depends on means a declared prerequisite. Extends and references do not imply prerequisite order. Shared code never creates dependencies. External targets are source declarations, not verified delivery.
Knuckles-Team/camunda-mcp / Unassigned
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-CAMUNDA-MCP | No relationships declared; dependencies unknown | ||
| CONN-CAMUNDA-MCP-CONNECTOR-CONTENT | No relationships declared; dependencies unknown | ||
Issues
0 open at capture.
Pull Requests
0 open at capture.
The build reads GitHub one time. This page makes no live API requests.
Each status file gives one spec row. Each requirement gives one more row. A record without a valid state shows INVALID. Expand a Definition to read the canonical requirement and verification text.
All documented records (6 rows)
| ID / source | Kind | Parent | State | Commit / test evidence |
|---|---|---|---|---|
| CONN-CAMUNDA-MCP CONN-CAMUNDA-MCP — Connector identity and release metadata | spec | None | SPECIFIED | No recorded commit/test evidence |
| CONN-CAMUNDA-MCP-R001 Connector reports its released version Definition — CONN-CAMUNDA-MCP / CONN-CAMUNDA-MCP — Connector identity and release metadataCanonical requirement and verification source**Connector reports its released version.** `camunda_mcp.__version__` equals the released `pyproject.toml` version and the bump configuration updates both. | `tests/test_version.py::test_reported_version_matches_the_released_package` | requirement | CONN-CAMUNDA-MCP | SPECIFIED | No recorded commit/test evidence |
| CONN-CAMUNDA-MCP-R002 One tool per API operation Definition — CONN-CAMUNDA-MCP / CONN-CAMUNDA-MCP — Connector identity and release metadataCanonical requirement and verification source**One tool per API operation.** The server lists 65 tools: one `camunda7_<operation>` per Camunda 7 client method (39), one `camunda8_<operation>` per Camunda 8 client method (24), plus `camunda_deploy` and `camunda_ingest_processes`. | `tests/test_tool_surface.py::test_surface_is_one_tool_per_operation_plus_two` | requirement | CONN-CAMUNDA-MCP | SPECIFIED | No recorded commit/test evidence |
| CONN-CAMUNDA-MCP-R003 No condensed action facades Definition — CONN-CAMUNDA-MCP / CONN-CAMUNDA-MCP — Connector identity and release metadataCanonical requirement and verification source**No condensed action facades.** No tool is tagged `split-action`, and no `camunda_*` tool routes an `action` string to an operation a `camunda7_*` or `camunda8_*` tool already serves. | `tests/test_tool_surface.py::test_no_split_action_facade_tools` | requirement | CONN-CAMUNDA-MCP | SPECIFIED | No recorded commit/test evidence |
| CONN-CAMUNDA-MCP-CONNECTOR-CONTENT CONN-CAMUNDA-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | spec | None | LANDED | No recorded commit/test evidence |
| CONN-CAMUNDA-MCP-CONNECTOR-CONTENT-R001 Default content Definition — CONN-CAMUNDA-MCP-CONNECTOR-CONTENT / CONN-CAMUNDA-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Default content.** `pyproject.toml` declares `camunda-mcp` as the single `scion_sdk.connector` entry point. The server lists the packaged `skill://` and `ontology://` resources and the packaged prompts with no `content=` argument. Proving test: `tests/test_default_content_surfaces.py`. | `resources/list` includes `skill://` and `ontology://`; `prompts/list` includes each packaged prompt. | requirement | CONN-CAMUNDA-MCP-CONNECTOR-CONTENT | LANDED | e0e43f00a74b |