docs: self-host at L1 and ship the three Claude skill adapters

- Move ops/contract.yaml annotation from specification-only to l1-implemented and
  declare real content roots for repoctl source, schemas, tests and Claude adapters.
- Add repoctl-cli capability to provides[].
- Route repository.tooling.use and repository.handoff intents to the existing
  tooling-implementation KDB topic.
- Update README, AGENTS.md and CLAUDE.md to describe the implemented repoctl surface
  instead of a planned one, without claiming L2/L3/MCP capabilities that don't exist.
- Add .claude/skills/{repository-bootstrap,repository-adoption,repo-handoff}/SKILL.md,
  generated from the same stewardship.skills_content strings that ship inside every
  repoctl init bootstrap (no duplicated logic).

`repoctl validate --repo .` passes with zero findings after this change.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Alexander Baranov
2026-08-24 15:00:34 +03:00
co-authored by Claude Sonnet 5
parent 96d4d08230
commit 7286322c83
8 changed files with 141 additions and 12 deletions
+19
View File
@@ -0,0 +1,19 @@
---
name: repo-handoff
description: Produce a minimal, intent-scoped context handoff for a repository using repoctl context. Use when another agent, session or teammate needs just enough context to work on one task in a repository.
---
# repo-handoff
Thin wrapper around `repoctl context`. Do not read the full repository or the full KDB
by hand when this skill applies — let `repoctl` perform the selection.
## Procedure
1. Turn the user's request into an `intent` id (e.g. `container.deploy`,
`repository.adopt`), not a literal command.
2. Run `repoctl context --repo <name-or-path> --intent <intent> --output json`.
3. If the bundle looks incomplete, retry with `--include-related` or `--materialize`
and an explicit `--budget-bytes`.
4. Hand the resulting `ContextBundle` (and any `warnings`) to the requester instead of
pasting raw repository files.
@@ -0,0 +1,27 @@
---
name: repository-adoption
description: Assess and adopt an existing repository into Repository Stewardship using repoctl adopt. Use when connecting an existing, non-templated repository without moving its domain content.
---
# repository-adoption
Thin wrapper around `repoctl adopt`. The canonical procedure is
`docs/adoption-runbook.md`; this skill only collects missing decisions, calls the CLI
with machine output, and explains findings. It must not duplicate the runbook logic.
## Procedure
1. Run `repoctl adopt --repo <path> --mode assess --output json` (read-only).
2. Present the classification, detected content roots, and any `questions` that need
owner confirmation.
3. Run `repoctl adopt --repo <path> --mode plan --output json` once open questions are
resolved. This is still read-only and returns an `AdoptionPlan` with a `planHash`.
4. Show the full plan (files created, patched managed blocks, preserved paths,
forbidden changes) before asking for approval.
5. Only after explicit approval, run
`repoctl adopt --repo <path> --mode apply --plan <plan-file> --approve <planHash>`.
6. Run `repoctl adopt --repo <path> --mode verify --output json` and report the
`AdoptionReport`, including any `unresolvedFindings`.
Default strategy is `overlay`. Only use `--strategy normalize --recipe
documents-to-content-root` when the owner explicitly asks to reorganize root documents.
@@ -0,0 +1,23 @@
---
name: repository-bootstrap
description: Bootstrap a new repository into Repository Stewardship using repoctl init. Use when creating a new repository or scaffolding ops/contract.yaml, kdb/kdb.yaml and agent entrypoints from scratch.
---
# repository-bootstrap
Thin wrapper around `repoctl init`. Do not reimplement classification, template
rendering or validation here — call the CLI and explain its output.
## Procedure
1. Collect the missing decisions from the user: repository type
(`infrastructure-config` | `service-config` | `software` | `project`), `metadata.name`,
`title`, `owners`, `lifecycle`.
2. Run `repoctl init --repo <path> --answers <answers-file> --output json` to obtain a
`BootstrapPlan` (this performs no writes).
3. Show the user the planned files and the `planHash`.
4. Only after explicit approval, run
`repoctl init --repo <path> --apply --plan <plan-file> --approve <planHash>`.
5. Report the resulting `repoctl validate --repo <path>` findings.
Never invent files outside the plan and never skip the approval step.