The change introduces a shared language policy so AI-DLC-generated question files, plans, and design artifacts now follow the user’s conversation language instead of always being emitted in English.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Added a Language section to question-format conventions and Rule 7 (Language) to the builder protocol so question files, plans, and design artifacts inherit the same locale behavior from shared config, instead of requiring separate language handling per skill.
Non-English AI-DLC users and operators now get generated requirement, planning, and design documents in their conversation language, reducing manual translation steps and making downstream design/review work faster and more usable, so teams should keep monitoring outputs for language drift in newly added skills or template paths. This is implemented through shared convention/protocol updates to keep the policy centralized across all current and future generators.
Non-English AI-DLC users and operators now get generated requirement, planning, and design documents in their conversation language, reducing manual translation steps and making downstream design/review work faster and more usable, so teams should keep monitoring outputs for language drift in newly added skills or template paths. This is implemented through shared convention/protocol updates to keep the policy centralized across all current and future generators.