mergemat/agent-readiness-skills · Archived

clarify-domain-docs

Clarifies project language and durable decisions, then records them in CONTEXT.md and ADRs. Use when a plan has fuzzy terms, domain concepts are overloaded, user wants shared language, or decisions should be captured before implementation.

First seen Jul 9, 2026

Installation

$ npx skills add mergemat/agent-readiness-skills --skill clarify-domain-docs

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mergemat/agent-readiness-skills.

npx skills add mergemat/agent-readiness-skills

Browse all from mergemat/agent-readiness-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,355 B
  • docs SUMMARY.md 266 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Clarify Domain Docs

Resolve language and decisions before implementation.

Ask one question at a time. If code can answer the question, inspect the code instead of asking.

Process

  1. Read existing CONTEXT.md, CONTEXT-MAP.md, and relevant ADRs.
  2. Identify overloaded, vague, or conflicting terms.
  3. Challenge terms against code and docs.
  4. Propose one canonical term and definition.
  5. Update CONTEXT.md when a term is resolved.
  6. Offer an ADR only for decisions that are hard to reverse, surprising, and trade-off driven.

Use [context-format.md](references/context-format.md) and [adr-format.md](references/adr-format.md) only when writing.

Rules

  • CONTEXT.md is a glossary, not a spec.
  • Keep definitions one or two sentences.
  • Do not include implementation details in glossary entries.
  • Do not create ADRs for obvious or temporary choices.
  • If multiple contexts exist, update the relevant context only.

Output

End with:

  • resolved terms
  • changed docs
  • decisions recorded or deliberately not recorded
  • remaining open questions