executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
updating-business-lexiconUse when translating French auto insurance business terms to English, editing rejection reasons, or introducing/changing domain vocabulary that must stay aligned with the FR->EN lexicon table.
Independent GitHub snapshot · Automated classification · Original documentation governs
Keep domain language consistent by updating the FR->EN lexicon whenever a French business term is added or changed.
Core principle: a business term change is incomplete until the lexicon table is updated in the same change.
Never finalize a French business-term translation/change without including .github/instructions/business-lexicon.instructions.md in the same change.
If a request says "do not touch instruction files", stop and state the conflict explicitly. Ask for an explicit override before skipping the lexicon update.
Use this skill when:
Do not use this skill for non-business technical wording (framework, infra, tooling terms).
| Situation | Required action |
|---|---|
| New French business term appears | Add one row in .github/instructions/business-lexicon.instructions.md |
| Existing French term meaning changes | Update the existing row and notes |
| Multiple English options exist | Keep one canonical US English term and explain alternatives in Notes |
| Fast translation request under pressure | Provide translation and still include/update lexicon row in the same change |
.github/instructions/business-lexicon.instructions.md.Correspondence Table.Example:
Conducteur trop jeune pour ce véhiculeDriver too young for this vehicledriving licence) instead of US (driver's license).If any red flag appears, enforce the hard gate and surface the conflict.