stabilize-initiative-language

Populate UBIQUITOUS_LANGUAGE.md with canonical terms, aliases, and flagged ambiguities for an initiative packet.

2|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/siarhei-belavus/agent-public --skill stabilize-initiative-language-siarhei-belavus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stabilize-initiative-language
Source: https://github.com/siarhei-belavus/agent-public/tree/main/skills/atelier-workflow/stabilize-initiative-language
Command: npx skills add https://github.com/siarhei-belavus/agent-public --skill stabilize-initiative-language-siarhei-belavus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Initiative work breaks down when tasks, contracts, and reviews depend on unstable or competing terminology. This Skill locks in a single canonical vocabulary before decomposition hardens, so downstream artifacts all speak the same language. ## Core Features & Use Cases - Canonical Glossary Authoring: Writes canonical terms, aliases to avoid, and short term relationships into UBIQUITOUS_LANGUAGE.md. - Ambiguity Flagging: Surfaces unresolved terminology conflicts explicitly instead of burying them in prose. - Workflow Integration: Runs after frame-initiative and exits with initiative status language_stabilized, gating later split work. - Use Case: After framing a new product initiative, run this Skill to consolidate discovery-phase vocabulary into one glossary so task breakdowns and contract definitions reference consistent names. ## Quick Start Stabilize the language for my current initiative packet by writing its canonical glossary into UBIQUITOUS_LANGUAGE.md.

Frequently Asked Questions about stabilize-initiative-language

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

FAQPage Schema
How do I stabilize terminology for an initiative before decomposition?▼

Run this Skill after frame-initiative to write canonical terms, aliases to avoid, and term relationships into UBIQUITOUS_LANGUAGE.md. It reads the initiative's BRIEF, DECISIONS, INVARIANTS, and related artifacts, then exits with status language_stabilized.

What is a ubiquitous language file in an initiative packet?▼

UBIQUITOUS_LANGUAGE.md is the glossary artifact inside an initiative packet that records canonical terms, aliases to avoid, flagged ambiguities, and short term relationships. It gives tasks, contracts, and reviews one shared vocabulary to depend on.

When should I run language stabilization in the initiative workflow?▼

Run it after frame-initiative and before any split work that depends on stable names. Running it too late means tasks and contracts may already reference competing terminology that is costly to reconcile.

How are unresolved terminology ambiguities handled?▼

Ambiguities that still need a decision are flagged explicitly in the glossary rather than buried in prose. The Skill writes one canonical vocabulary and does not preserve competing term sets just because they appeared during discovery.

Can the glossary be updated after the initiative progresses?▼

Yes, the Skill writes rerun guidance for later vocabulary updates into UBIQUITOUS_LANGUAGE.md. Subsequent runs can revise terms as the initiative evolves while keeping a single canonical set.