- US-CONTENT21
- US-MCP-BUILDER23
- US-PAGES2
- US-SKILL-GRAPH-BUILDER14
- US-WEB-RESEARCH6
- Requirementsall slices in all specs66
- Requirements not donenot VERIFIED35
- Specs not donewhole specs only5
Each spec shows its requirement count. Panel J lists every record.
Requirements (66)
Specs (5)
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 |
|---|---|---|---|---|---|
| US-CONTENTUS-CONTENT — The catalog is served by the SDK content convention | 21 | 14/21 | 14 | SPECIFIED | contracts/content-convention.md documentation: file exists; coverage not verified contracts/delivery-skill.md documentation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified ../../pyproject.toml implementation: file exists; coverage not verified ../../scripts/sync_upstream_skills.py implementation: file exists; coverage not verified ../../tests/test_catalog_content.py test: file exists; coverage not verified |
| US-MCP-BUILDERUS-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK components | 23 | 16/23 | 16 | SPECIFIED | spec.md documentation: file exists; coverage not verified tests/test_mcp_builder_connector_scaffold.py test: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified test-spec.md documentation: file exists; coverage not verified |
| US-PAGESUS-PAGES — Consolidate published documentation | 2 | 2/2 | 0 | LANDED | spec.md documentation: file exists; coverage not verified tests/pages_contracts.py test: file exists; coverage not verified .github/workflows/pages.yml implementation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified |
| US-SKILL-GRAPH-BUILDERUS-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graph | 14 | 1/14 | 1 | SPECIFIED | quickstart.md documentation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified research.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified tests/test_skill_graph_builder.py test: file exists; coverage not verified crawl-source documentation: file exists; coverage not verified graph-output documentation: file exists; coverage not verified |
| US-WEB-RESEARCHUS-WEB-RESEARCH — Web research skills call the served operation | 6 | 0/6 | 0 | SPECIFIED | spec.md documentation: file exists; coverage not verified universal_skills/skills/web-crawler/scripts/crawl.py implementation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified test-spec.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/universal-skills / Skill catalog (1)
US-CONTENT: no plan diagram declared.
Knuckles-Team/universal-skills / Unassigned (3)
US-MCP-BUILDER: no plan diagram declared.
US-PAGES: no plan diagram declared.
US-WEB-RESEARCH: no plan diagram declared.
Knuckles-Team/universal-skills / the `skill-graph-builder` skill. (1)
US-SKILL-GRAPH-BUILDER: 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/universal-skills / Skill catalog
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| US-CONTENT | depends on | SCION-CONNECTOR-CONTROL-R071.1 | Unresolved: missing source; source: specs/catalog-content/spec.md |
| US-CONTENT | references | SCION-CONNECTOR-CONTROL | Unresolved: unresolved; source: specs/catalog-content/spec.md |
Knuckles-Team/universal-skills / Unassigned
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| US-MCP-BUILDER | references | SCION-CENTRALIZED-CAPABILITIES | Knuckles-Team/scion-sdk: external declaration; not verified; source: specs/mcp-builder/spec.md |
| US-PAGES | No relationships declared; dependencies unknown | ||
| US-WEB-RESEARCH | references | ARBORA-OPS | Knuckles-Team/arbora: external declaration; not verified; source: specs/web-research/spec.md |
Knuckles-Team/universal-skills / the `skill-graph-builder` skill.
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| US-SKILL-GRAPH-BUILDER | depends on | US-WEB-RESEARCH-R001 | Knuckles-Team/universal-skills: local spec declaration; source: specs/skill-graph-builder/spec.md |
| US-SKILL-GRAPH-BUILDER | depends on | SG-CONTENT-R002`. | Unresolved: missing source; source: specs/skill-graph-builder/spec.md |
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 (71 rows)
| ID / source | Kind | Parent | State | Commit / test evidence |
|---|---|---|---|---|
| US-CONTENT US-CONTENT — The catalog is served by the SDK content convention | spec | None | SPECIFIED | No recorded commit/test evidence |
| US-CONTENT-R001 `universal_skills` is served as a content-only connector Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source**`universal_skills` is served as a content-only connector.** The package declares exactly one entry point, `agent_connector_sdk.connector = "universal_skills"`, and no provider entry-point group. Children `.1` to `.3` deliver it. | See each child. | requirement | US-CONTENT | SPECIFIED | No recorded commit/test evidence |
| US-CONTENT-R001.1 `pyproject.toml` declares `[project.entry-points."agent_connector_sdk.connector"]` with the single value `universal_skills` (bare package, content only), depends on `agent-connector-sdk[mcp]>=0.5.0,<0.6.0`, and declares no `agent_utilities.skill_providers` or other provider group. The SDK pytest plugin supplies the conformance checks, so the repository holds no copy of them. Caller chain: arbora resolves the installed distribution → the `agent_connector_sdk.connector` entry point of `pyproject.toml`. Shape: one entry-point table in `pyproject.toml`; the SDK pytest plugin supplies the checks. Proving test: `tests/test_catalog_content.py::test_declares_one_content_only_entry_point` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source`pyproject.toml` declares `[project.entry-points."agent_connector_sdk.connector"]` with the single value `universal_skills` (bare package, content only), depends on `agent-connector-sdk[mcp]>=0.5.0,<0.6.0`, and declares no `agent_utilities.skill_providers` or other provider group. The SDK pytest plugin supplies the conformance checks, so the repository holds no copy of them. Caller chain: arbora resolves the installed distribution → the `agent_connector_sdk.connector` entry point of `pyproject.toml`. Shape: one entry-point table in `pyproject.toml`; the SDK pytest plugin supplies the checks. Proving test: `tests/test_catalog_content.py::test_declares_one_content_only_entry_point`. | The test reads `pyproject.toml` and finds one entry point of the group, the bare package, the SDK floor and cap, and no provider group. | requirement | US-CONTENT | VERIFIED | b7adccaaf777 d487973cc5cf tests/test_catalog_content.py:22 tests/test_skill_pack_frontmatter.py:65 tests/test_skill_pack_frontmatter.py:70 tests/test_skill_pack_frontmatter.py:76 |
| US-CONTENT-R001.2 Every skill lives at `universal_skills/skills/<name>/SKILL.md`, one level deep, and its frontmatter `name` equals its folder name. Supporting files stay inside the skill folder so they are served with it. Caller chain: the SDK content convention → `universal_skills/skills/<name>/SKILL.md`. Shape: flat skill folders; the test reuses `tests/test_catalog_content.py` helpers. Proving test: `tests/test_catalog_content.py::test_every_skill_is_flat_and_named_by_folder` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceEvery skill lives at `universal_skills/skills/<name>/SKILL.md`, one level deep, and its frontmatter `name` equals its folder name. Supporting files stay inside the skill folder so they are served with it. Caller chain: the SDK content convention → `universal_skills/skills/<name>/SKILL.md`. Shape: flat skill folders; the test reuses `tests/test_catalog_content.py` helpers. Proving test: `tests/test_catalog_content.py::test_every_skill_is_flat_and_named_by_folder`. | The test finds no `SKILL.md` outside `skills/<name>/` (other than bundled assets) and no name that differs from its folder. | requirement | US-CONTENT | SPECIFIED | tests/test_catalog_content.py:33 |
| US-CONTENT-R001.3 The server the SDK builds for `universal_skills` lists one `skill://<name>/SKILL.md` resource for every skill folder. Caller chain: arbora → the SDK server factory → the skills directory provider → each skill folder. Shape: no server code in this package; the test builds the SDK server in process. Proving test: `tests/test_catalog_content.py::test_server_lists_every_skill` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceThe server the SDK builds for `universal_skills` lists one `skill://<name>/SKILL.md` resource for every skill folder. Caller chain: arbora → the SDK server factory → the skills directory provider → each skill folder. Shape: no server code in this package; the test builds the SDK server in process. Proving test: `tests/test_catalog_content.py::test_server_lists_every_skill`. | The test builds the server in process and compares the listed skill names with the folders. | requirement | US-CONTENT | SPECIFIED | tests/test_catalog_content.py:43 |
| US-CONTENT-R002 Skills can be vendored from pinned upstream repositories and kept current Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source**Skills can be vendored from pinned upstream repositories and kept current.** The repository holds `upstream-sources.toml` and `scripts/sync_upstream_skills.py`. Children `.1` to `.10` deliver it. | See each child. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:105 tests/test_upstream_sources.py:115 tests/test_upstream_sources.py:129 tests/test_upstream_sources.py:162 tests/test_upstream_sources.py:236 |
| US-CONTENT-R002.1 `upstream-sources.toml` lists each source with its repository URL, a pinned commit, path globs, the skills it produces, the license and a transform (`skill-md` or `command-md`). The loader rejects a manifest that omits one of them, that names a skill whose path matches no glob, or that has a duplicate source or skill. Caller chain: `scripts/sync_upstream_skills.py` → its manifest loader → `upstream-sources.toml`. Shape: one loader function in `scripts/sync_upstream_skills.py` that validates each source table. Proving test: `tests/test_upstream_sources.py::test_manifest_rejects_incomplete_sources` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source`upstream-sources.toml` lists each source with its repository URL, a pinned commit, path globs, the skills it produces, the license and a transform (`skill-md` or `command-md`). The loader rejects a manifest that omits one of them, that names a skill whose path matches no glob, or that has a duplicate source or skill. Caller chain: `scripts/sync_upstream_skills.py` → its manifest loader → `upstream-sources.toml`. Shape: one loader function in `scripts/sync_upstream_skills.py` that validates each source table. Proving test: `tests/test_upstream_sources.py::test_manifest_rejects_incomplete_sources`. | The test loads the real manifest and a set of broken manifests and finds the loader accepts the first and rejects each of the others. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:86 |
| US-CONTENT-R002.2 A pin is a full 40-character commit SHA. A branch, tag or short SHA is rejected. `--update` is the only way a pin moves. Caller chain: `scripts/sync_upstream_skills.py` → the manifest loader → the pin check. Shape: a pin check in the loader of `scripts/sync_upstream_skills.py`. Proving test: `tests/test_upstream_sources.py::test_pin_must_be_full_commit_sha` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceA pin is a full 40-character commit SHA. A branch, tag or short SHA is rejected. `--update` is the only way a pin moves. Caller chain: `scripts/sync_upstream_skills.py` → the manifest loader → the pin check. Shape: a pin check in the loader of `scripts/sync_upstream_skills.py`. Proving test: `tests/test_upstream_sources.py::test_pin_must_be_full_commit_sha`. | The test loads manifests with a branch name, a tag and a short SHA and finds each rejected. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:105 |
| US-CONTENT-R002.3 Each vendored skill keeps the upstream license text in `LICENSE` and names the license in its provenance file. A source without a license or license path is rejected. Caller chain: `scripts/sync_upstream_skills.py` → the license copy step → the skill folder. Shape: the license copy in `scripts/sync_upstream_skills.py`, reusing the snapshot reader. Proving test: `tests/test_upstream_sources.py::test_license_is_required_and_kept` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceEach vendored skill keeps the upstream license text in `LICENSE` and names the license in its provenance file. A source without a license or license path is rejected. Caller chain: `scripts/sync_upstream_skills.py` → the license copy step → the skill folder. Shape: the license copy in `scripts/sync_upstream_skills.py`, reusing the snapshot reader. Proving test: `tests/test_upstream_sources.py::test_license_is_required_and_kept`. | The test finds the loader rejecting a source with no license and each real vendored skill holding the upstream license text. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:115 |
| US-CONTENT-R002.4 The `skill-md` transform copies a skill folder as it is and sets only `metadata.version` from this package. The `command-md` transform converts a command prompt into a `SKILL.md` with `name`, `description` and the package version, resolves the script and command placeholders, and drops the upstream handoff and script keys. Both produce identical bytes on every run. Caller chain: `scripts/sync_upstream_skills.py` → the transform named by the source → the rendered `SKILL.md`. Shape: two transform functions in `scripts/sync_upstream_skills.py`. Proving test: `tests/test_upstream_sources.py::test_transforms_are_deterministic` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceThe `skill-md` transform copies a skill folder as it is and sets only `metadata.version` from this package. The `command-md` transform converts a command prompt into a `SKILL.md` with `name`, `description` and the package version, resolves the script and command placeholders, and drops the upstream handoff and script keys. Both produce identical bytes on every run. Caller chain: `scripts/sync_upstream_skills.py` → the transform named by the source → the rendered `SKILL.md`. Shape: two transform functions in `scripts/sync_upstream_skills.py`. Proving test: `tests/test_upstream_sources.py::test_transforms_are_deterministic`. | The test renders each transform twice from one input and finds identical bytes and the expected frontmatter. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:129 |
| US-CONTENT-R002.5 Overlays in `universal_skills/overlays/<skill>/*.md` merge into the rendered skill in file-name order with the modes `append`, `prepend`, `replace`, `insert-after` and `file`. A `replace` or `insert-after` whose match does not hit exactly one line fails. Caller chain: `scripts/sync_upstream_skills.py` → the overlay merge after the render → `universal_skills/overlays/<skill>/*.md`. Shape: one merge function in `scripts/sync_upstream_skills.py`. Proving test: `tests/test_upstream_sources.py::test_overlay_merge_is_ordered_and_strict` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceOverlays in `universal_skills/overlays/<skill>/*.md` merge into the rendered skill in file-name order with the modes `append`, `prepend`, `replace`, `insert-after` and `file`. A `replace` or `insert-after` whose match does not hit exactly one line fails. Caller chain: `scripts/sync_upstream_skills.py` → the overlay merge after the render → `universal_skills/overlays/<skill>/*.md`. Shape: one merge function in `scripts/sync_upstream_skills.py`. Proving test: `tests/test_upstream_sources.py::test_overlay_merge_is_ordered_and_strict`. | The test applies each mode, finds the expected text and finds the ambiguous match rejected. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:162 |
| US-CONTENT-R002.6 A sync fetches the pin into a throwaway repository, reads files from the git object store, executes none of them, and writes the snapshot under `universal_skills/upstream/<source>/`, the skill folder, `LICENSE` and `UPSTREAM.md` (source URL, pinned commit, path, license, transform, sync date, source digest, overlay list). Caller chain: `scripts/sync_upstream_skills.py` → the fetch into a throwaway repository → the snapshot writer. Shape: the sync command in `scripts/sync_upstream_skills.py`, reading blobs with `git cat-file`. Proving test: `tests/test_upstream_sources.py::test_sync_writes_provenance_without_running_code` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceA sync fetches the pin into a throwaway repository, reads files from the git object store, executes none of them, and writes the snapshot under `universal_skills/upstream/<source>/`, the skill folder, `LICENSE` and `UPSTREAM.md` (source URL, pinned commit, path, license, transform, sync date, source digest, overlay list). Caller chain: `scripts/sync_upstream_skills.py` → the fetch into a throwaway repository → the snapshot writer. Shape: the sync command in `scripts/sync_upstream_skills.py`, reading blobs with `git cat-file`. Proving test: `tests/test_upstream_sources.py::test_sync_writes_provenance_without_running_code`. | The test syncs from a local repository holding an executable script and finds the provenance fields, the license and no sign the script ran. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:236 |
| US-CONTENT-R002.7 `--check` runs offline and fails when any vendored file differs from the pinned snapshot plus overlays, when a file is missing or extra, or (with `--verify-pin`) when the snapshot differs from upstream. Caller chain: the pre-commit hook → `scripts/sync_upstream_skills.py --check` → the drift comparison. Shape: the check mode of `scripts/sync_upstream_skills.py`, reusing the render and merge functions. Proving test: `tests/test_upstream_sources.py::test_check_detects_hand_edits_and_overlay_drift` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source`--check` runs offline and fails when any vendored file differs from the pinned snapshot plus overlays, when a file is missing or extra, or (with `--verify-pin`) when the snapshot differs from upstream. Caller chain: the pre-commit hook → `scripts/sync_upstream_skills.py --check` → the drift comparison. Shape: the check mode of `scripts/sync_upstream_skills.py`, reusing the render and merge functions. Proving test: `tests/test_upstream_sources.py::test_check_detects_hand_edits_and_overlay_drift`. | The test finds a clean tree passing, then a hand edit, an extra file and an overlay change each reported as drift. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:259 |
| US-CONTENT-R002.8 `--update <source>` moves the pin to the latest commit of the source's tracked branch, keeps the manifest comments, and re-syncs so the change is one reviewable diff. Caller chain: a maintainer → `scripts/sync_upstream_skills.py --update <source>` → the pin rewrite and the re-sync. Shape: the update mode of `scripts/sync_upstream_skills.py`, reusing the sync command. Proving test: `tests/test_upstream_sources.py::test_update_moves_the_pin_and_resyncs` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source`--update <source>` moves the pin to the latest commit of the source's tracked branch, keeps the manifest comments, and re-syncs so the change is one reviewable diff. Caller chain: a maintainer → `scripts/sync_upstream_skills.py --update <source>` → the pin rewrite and the re-sync. Shape: the update mode of `scripts/sync_upstream_skills.py`, reusing the sync command. Proving test: `tests/test_upstream_sources.py::test_update_moves_the_pin_and_resyncs`. | The test updates a local source after a new upstream commit and finds the new pin, the kept comment and the new skill text. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:288 |
| US-CONTENT-R002.9 The spec-kit source vendors `speckit-constitution`, `speckit-specify`, `speckit-clarify`, `speckit-plan`, `speckit-tasks`, `speckit-analyze`, `speckit-checklist` and `speckit-implement`, each with an overlay that carries the repository extensions. The skills `spec-generator`, `task-planner`, `spec-verifier`, `spec-intake-wizard` and `feature-development-pipeline` are removed and no file in the repository refers to them. Caller chain: `scripts/sync_upstream_skills.py` → the spec-kit source of `upstream-sources.toml` → eight skill folders. Shape: one source table in `upstream-sources.toml` and one overlay folder per skill. Proving test: `tests/test_upstream_sources.py::test_spec_kit_skills_replace_the_retired_skills` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceThe spec-kit source vendors `speckit-constitution`, `speckit-specify`, `speckit-clarify`, `speckit-plan`, `speckit-tasks`, `speckit-analyze`, `speckit-checklist` and `speckit-implement`, each with an overlay that carries the repository extensions. The skills `spec-generator`, `task-planner`, `spec-verifier`, `spec-intake-wizard` and `feature-development-pipeline` are removed and no file in the repository refers to them. Caller chain: `scripts/sync_upstream_skills.py` → the spec-kit source of `upstream-sources.toml` → eight skill folders. Shape: one source table in `upstream-sources.toml` and one overlay folder per skill. Proving test: `tests/test_upstream_sources.py::test_spec_kit_skills_replace_the_retired_skills`. | The test finds the eight skills in sync with their pins, the five retired folders absent and no reference left. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:311 |
| US-CONTENT-R002.10 The pre-commit configuration runs `scripts/sync_upstream_skills.py --check`, and the `universal-installer` skill describes the update procedure: `--update` per source, `--check --verify-pin`, the tests, then a pull request and never a push to the default branch. Caller chain: the pre-commit configuration → `scripts/sync_upstream_skills.py --check`. Shape: one hook entry in the pre-commit configuration and one procedure section in the `universal-installer` skill. Proving test: `tests/test_upstream_sources.py::test_hook_and_installer_are_wired` Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification sourceThe pre-commit configuration runs `scripts/sync_upstream_skills.py --check`, and the `universal-installer` skill describes the update procedure: `--update` per source, `--check --verify-pin`, the tests, then a pull request and never a push to the default branch. Caller chain: the pre-commit configuration → `scripts/sync_upstream_skills.py --check`. Shape: one hook entry in the pre-commit configuration and one procedure section in the `universal-installer` skill. Proving test: `tests/test_upstream_sources.py::test_hook_and_installer_are_wired`. | The test finds the hook entry and the procedure in the installer skill. | requirement | US-CONTENT | VERIFIED | 87b5fd589e52 tests/test_upstream_sources.py:338 |
| US-CONTENT-R003 The `code-enhancer` skill follows the organization constitution Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source**The `code-enhancer` skill follows the organization constitution.** Its scripts take size, complexity and clone limits from one module that mirrors the constitution thresholds table. It has no baseline or ratchet mode. It writes specs to `specs/<feature>/`. It names only current intent tools of the graph door. It carries no legacy concept IDs in its examples. Its dependency guidance points at article XXVII. Caller chain: a maintainer runs the `code-enhancer` skill scripts → its limits module. Shape: one limits module under `universal_skills/skills/code-enhancer/` that mirrors the constitution table. Proving test: `tests/test_code_enhancer.py::test_code_enhancer_follows_the_organization_constitution`. | The test finds the limits module holding the table values, no baseline script or flag, no `.specify` output path, no retired tool or package name, no legacy concept ID, and the article reference in the skill. | requirement | US-CONTENT | VERIFIED | e0d20c6366d6 tests/test_code_enhancer.py:867 |
| US-CONTENT-R004 The `spec-row-delivery` skill guides one delivery assignment run (rollup) Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source**The `spec-row-delivery` skill guides one delivery assignment run (rollup).** The catalog holds one skill that states the procedure for delivering one spec row as one change proposal. A delivery assignment run of meristem loads it (`MERISTEM-SCM-R012`). The run reports to the engine delivery records (`MEDULLA-SDLC-R019.7`). The skill holds procedure only; it decides nothing and calls no tool by itself. Children `.1` to `.3` deliver it. Depends on: US-CONTENT-R001.2. | Satisfied only when every child is satisfied. Root test: `tests/test_spec_row_delivery_skill.py::test_skill_states_the_full_delivery_procedure`. | requirement | US-CONTENT | SPECIFIED | No recorded commit/test evidence |
| US-CONTENT-R004.1 Content: the delivery procedure Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source**Content: the delivery procedure.** `universal_skills/skills/spec-row-delivery/SKILL.md` must state these steps in order. Read the row, its plan section and its contracts. Search the existing code before writing new code. Implement the row with a test bound to its ID. Commit with the `Spec:` trailer directly above the co-author line. Run the gates the change touches. End with one report state: `progress`, `waiting`, `ready`, `blocked`, `failed` or `dropped`. Resolve a review thread when its finding is fixed. Post one reply with a reason when a suggestion is declined. Stop work on an automated reviewer after a received `stop_addressing` verdict. The skill must forbid a merge, an auto-merge arming, a spec edit and a skipped gate. Caller chain: meristem delivery assignment run (`MERISTEM-SCM-R012.2`) → skill resource `skill://spec-row-delivery/SKILL.md` served by the SDK content convention (US-CONTENT-R001.3). Shape: one new `SKILL.md` in the flat layout of US-CONTENT-R001.2; no script and no server code. Refusal: the validation test fails and names the missing step or the missing prohibition. Knob: none. Depends on: US-CONTENT-R001.2, MERISTEM-SCM-R012. | Test: `tests/test_spec_row_delivery_skill.py::test_skill_states_the_full_delivery_procedure`. | requirement | US-CONTENT | SPECIFIED | No recorded commit/test evidence |
| US-CONTENT-R004.2 Frontmatter and catalog registration Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source**Frontmatter and catalog registration.** The skill frontmatter must carry `name: spec-row-delivery`, a one-sentence `description` with its trigger, `domain: development` and `skill_type: skill`. Its `metadata.version` must equal the package version. The served catalog must list `skill://spec-row-delivery/SKILL.md`. The skill must pass the hooks `check-atomicity`, `check-frontmatter-portability` and `skill-catalog-structure`. Caller chain: arbora serves the catalog → the SDK content convention (US-CONTENT-R001.3) → the skill folder. Shape: frontmatter keys in the style of `universal_skills/skills/sdd-implementer/SKILL.md`; reuse `tests/test_catalog_content.py::test_server_lists_every_skill` for the listing. Refusal: a portability or atomicity hook failure blocks the commit. Knob: none. Depends on: US-CONTENT-R004.1, US-CONTENT-R001.3. | Test: `tests/test_spec_row_delivery_skill.py::test_frontmatter_is_portable_and_the_catalog_lists_the_skill`. | requirement | US-CONTENT | SPECIFIED | No recorded commit/test evidence |
| US-CONTENT-R004.3 Validation test: procedure, prohibitions and neutral text Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source**Validation test: procedure, prohibitions and neutral text.** New `tests/test_spec_row_delivery_skill.py` must read the skill text. It asserts each step of US-CONTENT-R004.1 in order and each of the four prohibitions. It also asserts that the text names no host, private domain or local path. Caller chain: `pytest` → `tests/test_spec_row_delivery_skill.py` → `universal_skills/skills/spec-row-delivery/SKILL.md`. Shape: one test module that reuses the skill-path helpers of `tests/test_catalog_content.py`. Refusal: a missing step, a missing prohibition or a private name fails the test. Knob: none. Depends on: US-CONTENT-R004.1, US-CONTENT-R004.2. | Test: `tests/test_spec_row_delivery_skill.py::test_skill_text_is_neutral_and_forbids_merge_and_skips`. | requirement | US-CONTENT | SPECIFIED | No recorded commit/test evidence |
| US-CONTENT-R005 Delivery skills point to the delivery practice reference and the constitution articles Definition — US-CONTENT / US-CONTENT — The catalog is served by the SDK content conventionCanonical requirement and verification source**Delivery skills point to the delivery practice reference and the constitution articles.** The skills `sdd-full-lifecycle`, `sdd-implementer`, `arbora-development` and `medulla-development`, and the overlay of `speckit-implement`, must link the delivery practice reference and name articles XVIII, XXV, XXVIII and XXIX of the constitution. They must not copy the rules of the reference. Caller chain: an agent loads a delivery skill → its Delivery practice section → the linked reference. Shape: one added section in each of four `SKILL.md` files and in `universal_skills/overlays/speckit-implement/10-workspace.md`, then `scripts/sync_upstream_skills.py` regenerates the vendored skill. Refusal: the test names the skill that lacks the link or the article. Knob: none. Proving test: `tests/test_delivery_practice_links.py::test_delivery_skills_link_the_reference_and_the_articles`. | The test finds the link and the four article numbers in each skill, and finds none of the reference's section titles copied. | requirement | US-CONTENT | VERIFIED | c8f6927cd743 tests/test_delivery_practice_links.py:16 |
| US-MCP-BUILDER US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK components | spec | None | SPECIFIED | No recorded commit/test evidence |
| US-MCP-BUILDER-R011 Connector scaffold on SDK components Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Connector scaffold on SDK components.** `scripts/scaffold_connector.py` must be the only connector generator. It must emit only connector-specific files and build the connector on SDK components. Parent of R011.1 to R011.13. SDK owners: `SCION-CONNECTOR-CONTROL-R019.1`, `SCION-QUALITY-RELEASE-R005.1`. | Every child row passes. | requirement | US-MCP-BUILDER | VERIFIED | 194946ca6443 6b640594c734 768aefce0622 9a21e191c8b6 ab2071875a33 tests/test_mcp_builder_connector_scaffold.py:118 tests/test_mcp_builder_connector_scaffold.py:126 tests/test_mcp_builder_connector_scaffold.py:132 tests/test_mcp_builder_connector_scaffold.py:149 tests/test_mcp_builder_connector_scaffold.py:231 |
| US-MCP-BUILDER-R011.1 Exact connector-owned tree Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Exact connector-owned tree.** The generator must write exactly the 28 files of the minimal connector tree: the package/API/content/spec files plus the aggregate hook reference, dashboard config, release/PR/Pages callers, `pages/index.md`, and the repository development skill. It must write none of the files the SDK or pipelines own: no `mcp_server.py`, `tools.py`, `_version.py`, `.bumpversion.cfg`, `docker/` files, `certification.json`, shapes file, `mcp_config.json`, `conftest.py`, `kg_ingest.py`, or shared-theme assets. The Pages caller leaves `shared_theme_enabled` false until a pinned pipelines checkout generates canonical theme outputs with `scripts/sync_mkdocs_theme.py`. Caller chain: an operator or agent follows universal_skills/skills/mcp-builder/SKILL.md:32 and runs `scaffold_connector.py <fleet>`; `main` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:659) → `scaffold` (:645) → `tree` (:605), whose `files` mapping is the whole connector-owned tree. Shape: file scaffold_connector.py, the `files` dict in `tree` and the Pages caller template `PAGES` (:454); reuse `tree` as the only list of generated paths. | `tests/test_mcp_builder_connector_scaffold.py::test_scaffold_emits_exactly_the_minimal_tree` and `tests/test_mcp_builder_connector_scaffold.py::test_generated_pages_caller_has_a_safe_shared_theme_preflight` pass. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 9a21e191c8b6 b7adccaaf777 tests/test_mcp_builder_connector_scaffold.py:118 tests/test_mcp_builder_connector_scaffold.py:231 |
| US-MCP-BUILDER-R011.2 Deterministic output Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Deterministic output.** The generator must write byte-identical files for the same fleet name. It must write no date, user or host name. Caller chain: `main` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:659) → `scaffold` (:645) → `tree` (:605), which returns `dict(sorted(out.items()))` from `fmt` over fleet-derived names only. Shape: file scaffold_connector.py (`_names` at :37, `tree`); the templates hold no clock, user or host call. | `tests/test_mcp_builder_connector_scaffold.py::test_generation_is_deterministic` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 b7adccaaf777 cf9c2f83be62 tests/test_mcp_builder_connector_scaffold.py:126 |
| US-MCP-BUILDER-R011.3 Identity and version in pyproject only Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Identity and version in pyproject only.** The generated `pyproject.toml` must hold the version, the one `agent_connector_sdk.connector` entry point `<fleet> = "<pkg>:connector"`, the `agent_connector_sdk.cli:serve` console script and the floor `scion-sdk[mcp]>=0.5.1,<0.6`. No Python file may spell the version or the fleet name. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) formats the `PYPROJECT` template (:53) with `SDK_FLOOR` (:27); the package modules (`INIT` at :84, `MAIN` at :98) carry no version or fleet literal. Shape: file scaffold_connector.py; the dependency is `scion-sdk[mcp]>={sdk},<0.6` and the console script and entry point sit in the PYPROJECT template. | `tests/test_mcp_builder_connector_scaffold.py::test_identity_and_version_live_in_pyproject_only` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:132 |
| US-MCP-BUILDER-R011.4 Shared workflows for release and PR Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Shared workflows for release and PR.** The release workflow must call the shared `python_pipeline.yml` with `connector: true` and `container_pipeline.yml` with `render_connector: true`, publishing to PyPI and Docker Hub. The PR workflow must call `connector_pr_pipeline.yml`. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) writes `.github/workflows/pipeline.yml` from `PIPELINE` (:394) and `.github/workflows/connector-pr.yml` from `CONNECTOR_PR` (:427). Shape: file scaffold_connector.py; both workflows are callers of the shared pipelines workflows and hold no step of their own. | `tests/test_mcp_builder_connector_scaffold.py::test_workflows_call_the_shared_pipelines_for_pypi_and_docker` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:149 |
| US-MCP-BUILDER-R011.5 One tool per operation with risk classes Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**One tool per operation with risk classes.** The generated `Api` class must hold one public method per API operation, and the SDK must serve one tool per method. Read, write and destructive annotations must follow the verb. No tool may take an `action` or `params_json` argument. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) writes `{pkg}/api_client.py` from `API_CLIENT` (:126), whose `Api` class (:135) the SDK serves one tool per public method; `VERBS` (:29) maps the verb to the risk class. Shape: file scaffold_connector.py; the class holds named operation methods and no `action` or `params_json` argument. | `tests/test_mcp_builder_connector_scaffold.py::test_one_tool_per_operation_with_risk_annotations` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:317 |
| US-MCP-BUILDER-R011.6 Sources declared as data Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Sources declared as data.** `connector_sources.py` must declare each source with `source_meta(tool=...)`. The SDK must load it with `load_declaration` and serve it as `connector://resources`. The scaffold must write no manifest file and no `declaration()` function. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) writes `{pkg}/connector_sources.py` from `SOURCES` (:158); the SDK reads it with `load_declaration`. Shape: file scaffold_connector.py; `SOURCES` declares each source with `source_meta` and `tree` writes no manifest file. | `tests/test_mcp_builder_connector_scaffold.py::test_sources_load_as_typed_declaration_with_no_manifest_file` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:328 |
| US-MCP-BUILDER-R011.7 Content served over MCP Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Content served over MCP.** The generated prompt must be a fastmcp prompt with a title and metadata. The generated skill and ontology must be served as resources. The scaffold must write no file that is served separately. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) writes the prompt from `PROMPT` (:176), the skill from `SKILL` (:187) and the ontology from `ONTOLOGY` (:287); the SDK serves them as MCP prompt and resources. Shape: file scaffold_connector.py; the three live under `{pkg}/prompts`, `{pkg}/skills` and `{pkg}/ontology` and `tree` writes no separately served copy. | `tests/test_mcp_builder_connector_scaffold.py::test_prompt_skill_and_ontology_are_served_over_mcp` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:338 |
| US-MCP-BUILDER-R011.8 Ontology rolls up to a core class Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Ontology rolls up to a core class.** Every generated class must extend a core class of the parent ontology with `rdfs:subClassOf`. The pack must not use `owl:imports` for the parent ontology. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) formats `ONTOLOGY` (:287) with `CORE_CLASS` (:28). Shape: file scaffold_connector.py; every generated class carries `rdfs:subClassOf` the core class and the template holds no `owl:imports`. | `tests/test_mcp_builder_connector_scaffold.py::test_ontology_rolls_up_to_a_core_class_and_never_imports_the_parent` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:349 |
| US-MCP-BUILDER-R011.9 Pipelines connector gates pass Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Pipelines connector gates pass.** The generated repository must pass the pipelines `connector-name` gate in strict mode and the `connector-standard` file and spelling checks. Caller chain: `main` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:659) tells the operator to run `pipelines-hook connector-name --strict` before the first push; the gate reads the tree `tree` (:605) wrote. Shape: file scaffold_connector.py (`_names` at :37 builds the fleet, package and display names that the gate checks). | `tests/test_mcp_builder_connector_scaffold.py::test_pipelines_connector_gates_pass` passes. | requirement | US-MCP-BUILDER | VERIFIED | 194946ca6443 tests/test_mcp_builder_connector_scaffold.py:387 |
| US-MCP-BUILDER-R011.10 Ontology graph check passes Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Ontology graph check passes.** The generated pack must raise no `connector-ontology-map graph-check` finding against the core ontology at the revision pinned in the test. The test fetches that revision; it needs no local checkout. Caller chain: `main` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:659) tells the operator to run `pipelines-hook connector-ontology-map graph-check`; the gate reads `ONTOLOGY` (:287) as written by `tree` (:605). Shape: file scaffold_connector.py; the test fetches the core ontology at a pinned revision. | `tests/test_mcp_builder_connector_scaffold.py::test_ontology_graph_check_passes_against_the_core_ontology` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:443 |
| US-MCP-BUILDER-R011.11 SDK conformance plugin passes Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**SDK conformance plugin passes.** The generated package must pass the SDK pytest conformance plugin and hold no copy of its tests. Caller chain: the generated tests/test_api_client.py (`TEST` at universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:492) runs beside the SDK pytest plugin `agent_connector_sdk.testing.plugin`. Shape: file scaffold_connector.py; `TEST` holds only client-logic tests and copies none of the plugin tests. | `tests/test_mcp_builder_connector_scaffold.py::test_generated_package_passes_the_sdk_conformance_plugin` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:461 |
| US-MCP-BUILDER-R011.12 Client from one SDK auth declaration Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Client from one SDK auth declaration.** `auth.py` must build the client with `client_factory` and one auth declaration, a TLS profile name and delegation. No generated module may import `requests` or `httpx`, disable TLS verification, build an SSL context or hold a thread-local token. SDK owner: `SCION-CONNECTOR-CONTROL-R028.4`. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) writes `{pkg}/auth.py` from `AUTH` (:104), whose `get_client` (:121) returns the client built by the SDK `client_factory`. Shape: file scaffold_connector.py; `AUTH` declares one auth, one TLS profile name and delegation, and imports no `requests` or `httpx`. | `tests/test_mcp_builder_connector_scaffold.py::test_client_is_one_sdk_auth_declaration_with_no_own_transport` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:474 |
| US-MCP-BUILDER-R011.13 Dependencies through SDK extras Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Dependencies through SDK extras.** The generated `pyproject.toml` must depend on the SDK only, declare no optional dependency and declare no entry point other than the connector identity. A connector adds optional dependencies as SDK extras. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) formats the `PYPROJECT` template (:53), whose `dependencies` list holds only `scion-sdk[mcp]`. Shape: file scaffold_connector.py; the template has no optional-dependencies table and one entry point, the connector identity. | `tests/test_mcp_builder_connector_scaffold.py::test_optional_dependencies_are_sdk_extras_only` passes. | requirement | US-MCP-BUILDER | VERIFIED | 6b640594c734 tests/test_mcp_builder_connector_scaffold.py:486 |
| US-MCP-BUILDER-R011.14 The connector inherits the organization constitution Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**The connector inherits the organization constitution.** The scaffold must write `.specify/memory/constitution.md`. The file must link the organization constitution by public URL, state the inherited version, and hold the connector articles: one external system, one tool per API operation, and the SDK as the only dependency. Caller chain: `tree` (universal_skills/skills/mcp-builder/scripts/scaffold_connector.py:605) writes `.specify/memory/constitution.md` from `CONSTITUTION` (:559). Shape: file scaffold_connector.py; the template links the organization constitution by public URL, names the inherited version and lists the three connector articles. | `tests/test_mcp_builder_connector_scaffold.py::test_connector_inherits_the_organization_constitution` passes. | requirement | US-MCP-BUILDER | VERIFIED | f34012aa6532 tests/test_mcp_builder_connector_scaffold.py:501 |
| US-MCP-BUILDER-R012 Wrap an existing MCP server Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Wrap an existing MCP server.** `scaffold_connector.py <fleet> --wrap-mcp <url-or-command>` must generate a connector that serves an existing MCP server through the SDK upstream registry (`SCION-CONNECTOR-CONTROL-R914`). It must write no REST client. Parent of R012.1 to R012.3. | Every child row passes. | requirement | US-MCP-BUILDER | SPECIFIED | 3681cc1b8464 |
| US-MCP-BUILDER-R012.1 Deterministic whole project Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Deterministic whole project.** The same arguments must give byte-identical output for the repository and the deployment bundle. No date, user or host name may be written. | `tests/test_mcp_builder_connector_scaffold.py::test_wrap_project_is_deterministic` passes. | requirement | US-MCP-BUILDER | SPECIFIED | tests/test_mcp_builder_connector_scaffold.py:529 |
| US-MCP-BUILDER-R012.2 Namespaced upstream with governance Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Namespaced upstream with governance.** The generated `upstreams.py` must declare one upstream with a credential reference, a TLS profile setting and a drift fingerprint setting, and no host. The generated `governance.py` must ask for approval on every write through the SDK confirmation, refuse a scope outside the allow list before any request, return a typed refusal code for each failure and audit each write without the credential. No tool may take an `action` argument. | `tests/test_mcp_builder_connector_scaffold.py::test_wrap_mounts_the_upstream_with_governance_and_no_rest_client` passes. | requirement | US-MCP-BUILDER | VERIFIED | 3681cc1b8464 tests/test_mcp_builder_connector_scaffold.py:535 |
| US-MCP-BUILDER-R012.3 The generated repository passes its own gates Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**The generated repository passes its own gates.** The generated repository must pass its own tests with nothing skipped, including a coverage test: the served tool count must be at least the upstream count, and every served schema must be typed. It must pass `connector-name --strict` and the `connector-standard` checks. | `tests/test_mcp_builder_connector_scaffold.py::test_wrapped_repo_passes_its_own_gates` passes. | requirement | US-MCP-BUILDER | SPECIFIED | tests/test_mcp_builder_connector_scaffold.py:552 |
| US-MCP-BUILDER-R013 Deployment bundle from the same command Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Deployment bundle from the same command.** Beside the repository the scaffold must write the private-registry image build, the service manifests, the workspace manifest entry and the arbora onboarding entry. Parent of R013.1 to R013.3. | Every child row passes. | requirement | US-MCP-BUILDER | SPECIFIED | 3681cc1b8464 |
| US-MCP-BUILDER-R013.1 Bundle layout Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Bundle layout.** The scaffold must write `images/<fleet>/`, `services/<fleet>/k8s/manifests.yaml`, `onboarding/<fleet>/workspace-entry.yml` and `onboarding/<fleet>/arbora-connector.yml`. | `tests/test_mcp_builder_connector_scaffold.py::test_deploy_bundle_is_emitted_beside_the_repo` passes. | requirement | US-MCP-BUILDER | SPECIFIED | tests/test_mcp_builder_connector_scaffold.py:578 |
| US-MCP-BUILDER-R013.2 No secret value and release-only image Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**No secret value and release-only image.** The manifests must reference secrets through an ExternalSecret store key only and must mount no source. The image must install the published release and copy no source. | `tests/test_mcp_builder_connector_scaffold.py::test_deploy_bundle_holds_no_secret_value_and_installs_the_release` passes. | requirement | US-MCP-BUILDER | SPECIFIED | tests/test_mcp_builder_connector_scaffold.py:591 |
| US-MCP-BUILDER-R013.3 Site values from a deploy profile Definition — US-MCP-BUILDER / US-MCP-BUILDER — The mcp-builder scaffold builds connectors on SDK componentsCanonical requirement and verification source**Site values from a deploy profile.** Registry, domain, namespace, secret store and CI include must come from a deploy profile. The neutral default names no real host. An unknown profile key must refuse. | `tests/test_mcp_builder_connector_scaffold.py::test_deploy_profile_supplies_site_values` passes. | requirement | US-MCP-BUILDER | SPECIFIED | tests/test_mcp_builder_connector_scaffold.py:611 |
| US-PAGES US-PAGES — Consolidate published documentation | spec | None | LANDED | No recorded commit/test evidence |
| US-PAGES-R002 Consolidate published documentation Definition — US-PAGES / US-PAGES — Consolidate published documentationCanonical requirement and verification source**Consolidate published documentation.** GitHub Pages serves as the readable view of this repository's skill catalog, contribution workflow, and relevant specifications, while every page's content stays sourced from one canonical tracked file in Git rather than a duplicated copy. Caller chain: .github/workflows/pages.yml:13 calls the shared `pages_pipeline.yml`, which builds MkDocs with the hook `on_files` (scripts/pages_sources.py:118); the hook publishes root guides and the spec package from their tracked files through `public_links` (scripts/pages_sources.py:16) and `status_markdown` (:41). Shape: files scripts/pages_sources.py, mkdocs.yml (`hooks` at :55) and CONTRIBUTING.md; the build holds generated pages in memory only, so no second copy exists; reuse `File.generated` of MkDocs. | A Pages build check confirms the navigation's internal links resolve and that editing the canonical tracked document updates the published view without a manual copy. Test: `tests/pages_contracts.py::test_canonical_sources_and_existing_urls` and `tests/pages_contracts.py::test_invalid_sources_fail_closed`. | requirement | US-PAGES | LANDED | 0813f09b14a4 a32ae4574cbf d754f30cdf82 |
| US-PAGES-R001 Shared documentation hierarchy across the fleet's sites Definition — US-PAGES / US-PAGES — Consolidate published documentationCanonical requirement and verification source**Shared documentation hierarchy across the fleet's sites.** universal-skills' published skill catalog and specifications follow the same reusable navigation and content hierarchy, assembled from the shared Pages template and workflow, used by the documentation sites of the other core ecosystem repositories, so a reader moving between them finds the same structure. Caller chain: a push of a `v*` tag or a manual dispatch starts .github/workflows/pages.yml:13, which calls the shared `pages_pipeline.yml`; MkDocs then reads the navigation in mkdocs.yml and the hook `on_files` (scripts/pages_sources.py:118). Shape: add a navigation and link-structure check as a new test in tests/pages_contracts.py that compares the nav tree of mkdocs.yml with the shared template; align the nav entries in mkdocs.yml to that template; reuse the `checkout` and `build` fixtures (tests/pages_contracts.py:16, :48). | A cross-site navigation and link-structure check confirms this repository's published hierarchy matches the shared template used across the fleet's documentation sites. Test: planned `tests/pages_contracts.py::test_navigation_matches_shared_template` (see test-spec.md). | requirement | US-PAGES | LANDED | 0dae5c7db0f2 |
| US-SKILL-GRAPH-BUILDER US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graph | spec | None | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R001 The builder turns any source into a standard skill graph (rollup) Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**The builder turns any source into a standard skill graph (rollup).** The `skill-graph-builder` skill is the only producer of the graphs in `skill-graphs`. Its CLI `scripts/generate_skill.py` classifies the sources, hands them to the pipeline and flattens the result. Children `.1` to `.4` deliver it. | See each child. | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R001.1 Graph name Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Graph name.** Caller chain: `main` → `generate_skill`. Shape: a name that does not end in `-docs` gets the suffix, then `_portable_name` limits each path component to 80 characters with a digest. | `tests/test_skill_graph_builder.py::test_graph_name_gets_docs_suffix_and_is_portable` (bound). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | tests/test_skill_graph_builder.py:71 |
| US-SKILL-GRAPH-BUILDER-R001.2 Source kinds Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Source kinds.** Caller chain: `generate_skill` → `_classify_sources`. Shape: a comma-separated source list maps each item to a `SourceSpec`. An http(s) URL is `web`, a `.pdf` is `pdf`, other office extensions (`.docx`, `.pptx`, `.xlsx`, `.csv`) are `office`, anything else is `dir`. | `tests/test_skill_graph_builder.py::test_sources_are_classified_by_kind` (bound). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | tests/test_skill_graph_builder.py:90 |
| US-SKILL-GRAPH-BUILDER-R001.3 Flat portable corpus Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Flat portable corpus.** Caller chain: `generate_skill` → `_flatten_reference_tree`. Shape: every `reference/**/*.md` moves to `reference/<sha256(url or title)[:8]>.md` (12 then 16 characters on a collision). `index.json` sections, `sources.json` files and the `SKILL.md` links follow the move. | `tests/test_skill_graph_builder.py::test_flatten_hashes_names_and_repoints_the_manifests` (bound). | requirement | US-SKILL-GRAPH-BUILDER | VERIFIED | 49883800ee93 tests/test_skill_graph_builder.py:110 |
| US-SKILL-GRAPH-BUILDER-R001.4 Output target Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Output target.** Caller chain: `generate_skill` → `_resolve_out_dir`. Shape: `--output-dir` wins. Otherwise the target is `skill_graphs/skills` of the sibling `skill-graphs` checkout, so the graph is served by `SG-CONTENT-R001.2`. Without that checkout the target is `~/.cache/universal-skills/skill-graphs`. | `tests/test_skill_graph_builder.py::test_output_goes_to_the_graph_collection_or_the_cache` (bound). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | tests/test_skill_graph_builder.py:142 |
| US-SKILL-GRAPH-BUILDER-R002 Web sources come from the web-crawler skill (rollup) Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Web sources come from the web-crawler skill (rollup).** The `web-crawler` skill is the one page scraper of this repository; no `web-scraper` skill exists (`US-WEB-RESEARCH-R001`). The builder fetches a `web` source only through it. Children `.1` and `.2` deliver it. | See each child. | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R002.1 Crawl through the skill script Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Crawl through the skill script.** Caller chain: `generate_skill` (`universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:296`) → `SkillGraphPipeline(crawler_fn=_make_crawler_fn(...))` (`universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:338`) → `crawler_fn` (`universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:214`). Shape: the function runs `universal_skills/skills/web-crawler/scripts/crawl.py` (resolved by `_crawl_script`, `universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:203`; run at `universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:239`) with `--urls`, `--strategy recursive`, `--output-dir`, `--max-depth` and `--max-pages`. It forwards `--disable-magic-js`, `--no-sitemap` and `--wait-for`. It returns one `AcquiredDoc` per written markdown file. | `tests/test_skill_graph_builder.py::test_web_sources_are_fetched_by_the_web_crawler_skill` (bound). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | tests/test_skill_graph_builder.py:156 |
| US-SKILL-GRAPH-BUILDER-R002.2 Follow the served web operation Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Follow the served web operation.** Caller chain: as `R002.1`. Shape: once `crawl.py` calls `research.web` (`US-WEB-RESEARCH-R001.1`), `crawler_fn` passes `--output-dir` and the skill writes one `<sha256(url)[:8]>.md` per cited page. The page text is the stored chunk text of each cited Document (`ARBORA-OPS-R067.1`). The builder keeps no HTTP client. Depends on: `US-WEB-RESEARCH-R001.1`. | `tests/test_skill_graph_builder_served.py::test_web_source_is_built_from_research_web_documents` (planned, see test-spec). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R003 A graph records its provenance and its ontology layer (rollup) Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**A graph records its provenance and its ontology layer (rollup).** The builder writes the records that `SG-CONTENT-R002` checks and the concept layer that `SG-CONTENT-R003` stores. Children `.1` and `.2` deliver it. | See each child. | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R003.1 Provenance record Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Provenance record.** Caller chain: `generate_skill` (`universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:296`) → `pipe.build` (`universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:343`) → `write_sources_manifest` (planned, new file `universal_skills/skill_graph_pipeline/manifest.py`; the package does not exist until `US-SKILL-GRAPH-BUILDER-R004.1` lands). Shape: `sources.json` holds schema `skill-graph-sources/v1`, `builder_version`, `built_at`, per-source `{kind, uri, options, extractor, fetched_at, content_hash, doc_count}` and per-file `{path, sha256, bytes}`. `SKILL.md` declares `skill_type: graph`. Depends on: `US-SKILL-GRAPH-BUILDER-R004.1`. | `tests/test_skill_graph_builder_pipeline.py::test_build_writes_manifest_and_graph_type` (planned, see test-spec). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R003.2 Ontology layer emission Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Ontology layer emission.** Caller chain: `generate_skill` (`universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:296`) → `pipe.build` (`universal_skills/skills/skill-graph-builder/scripts/generate_skill.py:343`) → `write_ontology_module` (planned, new file `universal_skills/skill_graph_pipeline/ontology.py`; the package does not exist until `US-SKILL-GRAPH-BUILDER-R004.1` lands). Shape: when the build extracts concepts, it writes `skill_graphs/ontology/<graph>.ttl` with ontology IRI `http://knuckles.team/kg/skillgraph/<graph>`. Each class is `rdfs:subClassOf` a class of `http://knuckles.team/kg`. The file has no `owl:imports`. It sets `kg_ontology` to the file stem and lists the class IRIs in `concepts`. Without concepts both stay `null` and empty. Depends on: `SG-CONTENT-R003.1`, `SG-CONTENT-R003.2`, `US-SKILL-GRAPH-BUILDER-R004.1`. | `tests/test_skill_graph_builder_pipeline.py::test_build_writes_core_rooted_ontology_module` (planned, see test-spec). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R004 The builder runs on current owners only (rollup) Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**The builder runs on current owners only (rollup).** `generate_skill.py` imports the retired `agent_utilities` package, so the builder cannot run in a clean environment. The pipeline moves into this repository, and graph ingestion becomes the engine pack import. Children `.1` and `.2` deliver it. | See each child. | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R004.1 Own the pipeline Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Own the pipeline.** Caller chain: `generate_skill` → `SkillGraphPipeline.build`. Shape: new package `universal_skills/skill_graph_pipeline/` holds `SourceSpec`, `AcquiredDoc` and `SkillGraphPipeline` with the verbs `build`, `distill`, `restyle`, `status`, `refresh`, `rebuild`. The script imports it from there. No module of the repository imports `agent_utilities`. Refusal: the test fails on any `agent_utilities` import under `universal_skills/skills/skill-graph-builder`. | `tests/test_skill_graph_builder_pipeline.py::test_builder_imports_no_retired_package` (planned, see test-spec). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-SKILL-GRAPH-BUILDER-R004.2 Delete the daemon enrichment and the retired flags Definition — US-SKILL-GRAPH-BUILDER / US-SKILL-GRAPH-BUILDER — The builder distills any source into a skill graphCanonical requirement and verification source**Delete the daemon enrichment and the retired flags.** Caller chain: `main` → `generate_skill`. Shape: the flags `--no-kg`, `--ingest-kg`, `--append` and the `kg_enrich` argument are deleted. The builder writes the offline corpus only. The engine ingests it as a pack (`MEDULLA-TYPED-PACKS-R701`). `sources.json` keeps `kg_ingested` out. Depends on: `MEDULLA-TYPED-PACKS-R701`. | `tests/test_skill_graph_builder_pipeline.py::test_retired_flags_are_refused` (planned, see test-spec). | requirement | US-SKILL-GRAPH-BUILDER | SPECIFIED | No recorded commit/test evidence |
| US-WEB-RESEARCH US-WEB-RESEARCH — Web research skills call the served operation | spec | None | SPECIFIED | No recorded commit/test evidence |
| US-WEB-RESEARCH-R001 The web-crawler skill is a thin skill over `research.web` (rollup) Definition — US-WEB-RESEARCH / US-WEB-RESEARCH — Web research skills call the served operationCanonical requirement and verification source**The web-crawler skill is a thin skill over `research.web` (rollup).** No skill named `web-scraper` exists. The `web-crawler` skill is the page scraper of this repository. It must call the arbora operation `research.web` (`ARBORA-OPS-R067`). It must hold no page fetch, render, crawl or extraction code. Children `.1` to `.5` deliver it. | See each child. | requirement | US-WEB-RESEARCH | SPECIFIED | No recorded commit/test evidence |
| US-WEB-RESEARCH-R001.1 Call the operation Definition — US-WEB-RESEARCH / US-WEB-RESEARCH — Web research skills call the served operationCanonical requirement and verification source**Call the operation.** `universal_skills/skills/web-crawler/scripts/crawl.py` must call `research.web` through `arbora.client`. A `--query` argument maps to `query`. A `--urls` argument maps to `urls`. `--backend` maps to `backend`. The script prints the Document IDs with their citations. Proving test: `tests/test_web_research_skill.py::test_crawl_calls_research_web`. Caller chain: an agent follows universal_skills/skills/web-crawler/SKILL.md and runs `crawl.py`; `main` (universal_skills/skills/web-crawler/scripts/crawl.py:946) parses `--urls` and today drives the local crawler (:1241 builds `KGIngestor`). The target chain is `main` → `invoke` (arbora/client/invoke.py:17 in the arbora package) with the operation `research.web`. Shape: replace `main` in crawl.py with an argparse shell of about 40 lines that maps `--query`, `--urls` and `--backend` to the operation arguments and prints each Document ID with its citation; reuse `invoke` and `OperationError` (arbora/client/http.py:21) and add no HTTP client. | One script run sends one `research.web` call with the mapped arguments. Test: planned `tests/test_web_research_skill.py::test_crawl_calls_research_web` (see test-spec.md). | requirement | US-WEB-RESEARCH | SPECIFIED | No recorded commit/test evidence |
| US-WEB-RESEARCH-R001.2 Delete local scraping Definition — US-WEB-RESEARCH / US-WEB-RESEARCH — Web research skills call the served operationCanonical requirement and verification source**Delete local scraping.** The skill must delete the HTTP, browser, `robots.txt`, sitemap and markdown code in `crawl.py` and `scripts/security_runtime.py`. `SKILL.md` must describe only the operation call. Proving test: `tests/test_web_research_skill.py::test_skill_has_no_http_client`. Caller chain: the same `main` (universal_skills/skills/web-crawler/scripts/crawl.py:946) today reaches `SafeHttpCrawler`, the sitemap and markdown helpers and `security_runtime.py` (universal_skills/skills/web-crawler/scripts/security_runtime.py:117 `CrawlerSecurityPolicy`). Shape: delete those definitions from crawl.py (1,360 lines) and delete security_runtime.py (478 lines); rewrite SKILL.md to describe only the `research.web` call; delete tests/test_web_crawler_security.py with the code it covers. | The test finds no HTTP client, browser driver or HTML parser import in the skill scripts. Test: planned `tests/test_web_research_skill.py::test_skill_has_no_http_client` (see test-spec.md). | requirement | US-WEB-RESEARCH | SPECIFIED | No recorded commit/test evidence |
| US-WEB-RESEARCH-R001.3 Alias Definition — US-WEB-RESEARCH / US-WEB-RESEARCH — Web research skills call the served operationCanonical requirement and verification source**Alias.** The `web-fetch` skill must forward to `web-crawler` with one URL and `max_pages` 1. It must hold no code of its own beyond the forward. Proving test: `tests/test_web_research_skill.py::test_web_fetch_forwards`. Caller chain: an agent runs `fetch.py` of the `web-fetch` skill; `main` (universal_skills/skills/web-fetch/scripts/fetch.py:48) calls `fetch_page` (:34), which loads the crawler runtime through `_crawler_runtime` (:19). Shape: replace `fetch_page` with a call to the new `crawl.py` entry using one URL and `max_pages` 1, and delete `_crawler_runtime`; the file holds no other code. | A `web-fetch` run sends one `research.web` call with one URL. Test: planned `tests/test_web_research_skill.py::test_web_fetch_forwards` (see test-spec.md). | requirement | US-WEB-RESEARCH | SPECIFIED | No recorded commit/test evidence |
| US-WEB-RESEARCH-R001.4 Refusal Definition — US-WEB-RESEARCH / US-WEB-RESEARCH — Web research skills call the served operationCanonical requirement and verification source**Refusal.** The skill must print the refusal code of the operation and exit with status 2. It must not fall back to a local fetch. Proving test: `tests/test_web_research_skill.py::test_refusal_exits_without_fallback`. Caller chain: `main` of the new crawl.py (universal_skills/skills/web-crawler/scripts/crawl.py:946) awaits `invoke` and catches `OperationError` (arbora/client/http.py:21). Shape: print the refusal code, return exit status 2 and catch nothing else; no branch calls a local fetch. | A refused call exits 2 and makes no other network call. Test: planned `tests/test_web_research_skill.py::test_refusal_exits_without_fallback` (see test-spec.md). | requirement | US-WEB-RESEARCH | SPECIFIED | No recorded commit/test evidence |
| US-WEB-RESEARCH-R001.5 Hot-path proof Definition — US-WEB-RESEARCH / US-WEB-RESEARCH — Web research skills call the served operationCanonical requirement and verification source**Hot-path proof.** The test runs `crawl.py` against a fixture arbora server that serves `research.web`. It denies every other network destination. Proving test: `tests/test_web_research_skill_served.py::test_skill_reaches_research_web_only`. Caller chain: the test starts a fixture arbora server on loopback, sets the arbora base URL, runs `main` (universal_skills/skills/web-crawler/scripts/crawl.py:946) as a subprocess and denies every other destination. Shape: new tests/test_web_research_skill_served.py with the fixture server in the same file; the served operation is `research.web` of `ARBORA-OPS-R067`. | The fixture receives one call, and the skill makes no other network request. Test: planned `tests/test_web_research_skill_served.py::test_skill_reaches_research_web_only` (see test-spec.md). | requirement | US-WEB-RESEARCH | SPECIFIED | No recorded commit/test evidence |