- 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>
1.0 KiB
1.0 KiB
name, description
| name | description |
|---|---|
| repository-bootstrap | 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
- Collect the missing decisions from the user: repository type
(
infrastructure-config|service-config|software|project),metadata.name,title,owners,lifecycle. - Run
repoctl init --repo <path> --answers <answers-file> --output jsonto obtain aBootstrapPlan(this performs no writes). - Show the user the planned files and the
planHash. - Only after explicit approval, run
repoctl init --repo <path> --apply --plan <plan-file> --approve <planHash>. - Report the resulting
repoctl validate --repo <path>findings.
Never invent files outside the plan and never skip the approval step.