Domain Context and Decision Handoff
Keeps business term definitions in one CONTEXT.md and routes hard decisions to the ADR skill
- Repository
- affaan-m/ECC
- Stars
- 295,127
- Licence
- MIT
- Files
- 4 files
What it does
When a project's business terms keep getting re-explained or one word means different things, this skill has the agent record precise, confirmed definitions in a single domain-language document (CONTEXT.md), reusing an existing glossary if one exists. It marks anything unconfirmed as 'needs confirmation' instead of guessing. When a choice is hard to reverse, it hands that decision to the separate architecture-decision-records skill and links to the result rather than copying it.
Great for
- Developers on projects where domain terms are repeatedly misunderstood
- Teams that want a stable glossary kept separate from status, tasks and architecture decisions
- Maintainers using the ECC skill set who want consistent ADR handling
Skip it if
- Small projects with no ambiguous domain language, since the skill advises against creating empty context files
- Non-technical users looking for a general writing or document tool, because it is a narrow governance workflow
Try asking
- “Our team uses the word 'account' three different ways; define it once in our context doc and flag what needs confirmation.”
- “Record the decision to store events in Postgres as an ADR and link it from our context file.”
- “Check whether our repo already has a glossary before creating a new CONTEXT.md.”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 4 original files, the MIT licence and an attribution note.
context-and-decisions.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip context-and-decisions.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip context-and-decisions.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Point the agent at your existing glossary or domain docs first so it reuses them rather than creating a new file.
- Expect the agent to mark uncertain terms 'needs confirmation'; have a domain owner resolve them.
- Keep schedules and task status in your issue tracker, since the skill keeps them out of context documents.
What's inside
- agents/openai.yaml
- references/source.md
- SKILL.md
- templates/context.example.md
Redistributed unmodified from affaan-m/ECC under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.