Adopt Arcantry

Arcantry 1.0.0adopt-arcantry

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

When to use

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

Link this skill

arcantry skills link adopt-arcantry --scope user

The standard destination is ~/.agents/skills. Codex reads this universal Agent Skills location directly.

Claude compatibility

arcantry skills link adopt-arcantry --scope user --compat claude

This keeps the universal link and adds a Claude alias to the same canonical package.

Compatibility

Source kinds: openspec, changelog, todo-txt.

Adapters:

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

Learning outcomes

• 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.

Examples

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

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.