domain-adopt

Seeds a project's DOMAIN.md and decision records from vocabulary scattered across existing documentation.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/skkap/claude-skills --skill domain-adopt-skkap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-adopt
Source: https://github.com/skkap/claude-skills/tree/main/plugins/shape-it/skills/domain-adopt
Command: npx skills add https://github.com/skkap/claude-skills --skill domain-adopt-skkap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mature projects accumulate settled vocabulary and decisions scattered across CLAUDE.md, README files, decision logs, and transcripts, with no single authoritative glossary. This Skill performs a one-off adoption pass that harvests that existing knowledge into a structured DOMAIN.md and docs/decisions/ records without inventing new terminology. ## Core Features & Use Cases - Guided five-step pass: Explore sources, propose a candidate model for review, ask one batched round of questions about conflicts, write the files, and report findings — nothing is written before operator review. - Multi-source harvesting: Mines orientation files, decision logs, folder names, live registries, prior session transcripts, and an operator narration to derive terms rather than invent them. - Decision log conversion: Sorts existing decision tables through a gate (hard to reverse, real alternatives), dates records from git history, and renumbers them chronologically. - Use Case: A two-year-old project with a stale CLAUDE.md and a DECISIONS.md table gets a reviewed DOMAIN.md of 14 terms, six numbered decision records dated from git history, and a report flagging where documentation disagrees with what actually ships. ## Quick Start Ask the AI to adopt or seed a domain model for this project using the domain-adopt skill.

Frequently Asked Questions about domain-adopt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a domain model for an existing project?

Run an adoption pass that harvests vocabulary already present in your CLAUDE.md, README, decision logs, and transcripts, then proposes a candidate DOMAIN.md for review before writing anything. Terms are derived from existing sources, never invented.

How do I convert a DECISIONS.md table into decision records?

Each row is tested against a gate: hard to reverse with genuine alternatives. Passing rows become numbered records in docs/decisions/, dated from git history when the source lacks dates. Rows that state facts move to DOMAIN.md; open to-dos stay put.

When should I use domain-adopt instead of the domain skill?

Use domain-adopt only as an explicit one-off bootstrap for a project with accumulated but undocumented vocabulary. For ongoing term-by-term maintenance during normal work, use the domain skill instead — adoption never starts as a side-effect of other tasks.

Does domain-adopt work on non-code projects like records or archives?

Yes. The harvest sources are prose documents, decision logs, folder names, and operator narration, none of which require source code. Records projects often benefit more because prose tolerates duplicate terminology longer than compilers do.

What are the limitations of a domain adoption pass?

It deliberately does not resolve every ambiguity — unresolved questions go to an Open questions list rather than triggering endless interviews. It also rewrites CLAUDE.md and creates files across the project, so it must run as a dedicated session, not a detour.