Menu
Choose between Shell and Python for generated automation code based on task traits. Use when automation language selection guidance is required.
识别业务能力并分类子域（Core/Supporting/Generic），产出核心域声明与所有权建议。
从不变量出发设计聚合边界：聚合根、实体、值对象、事务边界与跨聚合一致性策略。
映射限界上下文间的关系与集成策略：模式选择、契约所有权、失败模式与版本策略。
设计限界上下文及其通用语言：边界、职责、词汇表、团队所有权与边界 ADR。
协作式领域发现：通过事件风暴或领域故事讲述，产出事件流、命令/事件候选、热点与歧义清单。
设计构造块间的协作机制：领域事件、领域服务、仓储接口与工厂。
| name | automation-language-selection |
| description | Choose between Shell and Python for generated automation code based on task traits. Use when automation language selection guidance is required. |
Given a task description and basic characteristics (complexity, data handling, orchestration requirements), suggest Shell vs Python (or hybrid) in a way that is consistent with the governance rule-block and easy for agents to act on.
Input: Task description, automation requirements, and high-level complexity indicators.
Output: Language selection decision plus a short rationale suitable for logging or plan text.
Side Effects: May cause agents to load skill:language-python or skill:language-shell according to the decision.