Skip to content
v1.0.0

Adopt Arcantry

Skill 1.0.0 · primaryadopt-arcantry

Adopt the smallest useful Arcantry boundary while preserving repository-owned tooling, knowledge sources, and private state.

Use when: Inspect, adopt, validate, or remove Arcantry at shared, private, or configuration-free project scope while preserving repository-owned files.

Install only this skill

Section titled “Install only this skill”
Terminal window
arcantry skills link adopt-arcantry --scope user

This links only adopt-arcantry to the standard user location, ~/.agents/skills. Use --scope repo for one repository, or add --compat claude when that optional alias is needed.

Compatibility

Section titled “Compatibility”

Source kinds: openspec, changelog, todo-txt.

Adapters:

  • openspec: >=1 <2
  • keep-a-changelog: >=1 <3
  • todo-txt: >=1 <2

What it helps with

Section titled “What it helps with”
  • Distinguish discovery, footprint, and management for each project source.
  • Choose an explicit preservation or source transition boundary without automatic conversion.
  • Keep local state private unless the default remote branch establishes a different repository policy.
  • Prefer user-wide skills and make repository-private packages an explicit fallback.

History

Section titled “History”
  • 2026-08-18 - Coordinate project knowledge and agent workflows with Arcantry: Arcantry provides local-first project configuration, safe repository adoption, a portable catalog of focused agent skills, and one documented workflow for maintaining project intent, release meaning, task intake, verification, and audience-safe content.
  • 2026-08-17 - Unified Arcantry capabilities: Arcantry now combines its OpenSpec lifecycle with reusable skills, a complete Codex plugin, a versioned catalog, and one CLI for safe repository adoption and skill management.

Examples

Section titled “Examples”

Adopt Arcantry in a mature repository

Section titled “Adopt Arcantry in a mature repository”

Prompt

Use the adopt-arcantry skill to inspect a mature repository and plan selective adoption while preserving existing tooling and knowledge sources.

Expected outcome

A source-by-source adoption plan that leaves project-owned files unchanged until explicitly applied.

Diagnose an existing adoption

Section titled “Diagnose an existing adoption”

Prompt

Use the adopt-arcantry skill to inspect and validate this repository without removing unknown files or changing external systems.

Expected outcome

A repository health report backed by Arcantry validation and doctor checks, with private state kept local.