cc-devflow 4.4.1 → 4.5.0

package/.claude/skills/cc-act/CHANGELOG.md

@@ -1,5 +1,11 @@
 # CC-Act Skill Changelog
 
+## v1.6.2 - 2026-04-27
+
+- require closeout handoff documents to resolve the runtime output policy before writing PR briefs, release notes, resume indexes, or status handoffs
+- record `Output language` as the machine-enforced language contract while treating `agent_preferences` as advisory style input
+- render `Output language` metadata in generated PR briefs, release notes, resume indexes, and doc sync reports
+
 ## v1.6.1 - 2026-04-25
 
 - remove external tool provenance from the public skill contract so ship and documentation release rules read as native `cc-act` behavior

package/.claude/skills/cc-act/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-act
-version: 1.6.1
+version: 1.6.2
 description: 'Use when verified work must be shipped or handed off with a clear landing path: run simplify and required tests, create or update a PR, prepare a local handoff, close out merged work, sync docs, write release notes, and fold follow-ups back into backlog or roadmap.'
 triggers:
   - 准备提 PR
@@ -73,6 +73,14 @@ tool_budget:
 
 一句话：`cc-check` 证明“东西已经好”，`cc-act` 负责把“已经好”变成“已经落地”。
 
+## Runtime Output Policy
+
+写入任何 durable Markdown 或 JSON metadata 前，先运行 `cc-devflow config resolve --format policy`。
+
+- `Output language` 是机器约束，PR brief、resume index、release note 和 status handoff 必须记录并遵守它。
+- `agent_preferences` 是用户偏好建议，只影响表达方式和结构选择，不覆盖本 Skill 的工作流边界。
+- 如果配置解析失败，先修配置或向用户说明阻塞，不要用默认语言继续生成正式文档。
+
 ## Read First
 
 1. `PLAYBOOK.md`

package/.claude/skills/cc-act/assets/PR_BRIEF_TEMPLATE.md

@@ -1,5 +1,9 @@
 # PR Brief
 
+## Document Meta
+
+- Output language:
+
 ## Decision
 
 - Recommended mode:

package/.claude/skills/cc-act/assets/RELEASE_NOTE_TEMPLATE.md

@@ -1,5 +1,9 @@
 # Release Note
 
+## Document Meta
+
+- Output language:
+
 ## Release Scope
 
 - Why a release note is needed now:

package/.claude/skills/cc-act/scripts/cc-act-common.sh

@@ -103,6 +103,11 @@ req_act_spec_sync_ready() {
   jq -r '.specSyncReady // false' "$report_card" 2>/dev/null || echo false
 }
 
+req_act_output_language() {
+  local report_card="$1"
+  jq -r '.outputPolicy.documentLanguage // "en"' "$report_card" 2>/dev/null || echo en
+}
+
 req_act_design_goal() {
   local design_file="$1"
   awk -F': ' '/^- Deliver:/{print $2; exit} /^- Change:/{print $2; exit}' "$design_file" 2>/dev/null || true

package/.claude/skills/cc-act/scripts/render-pr-brief.sh

@@ -62,6 +62,7 @@ pr_url="$(req_act_ship_field "$ship_context" "PR_URL")"
 requirement_id="$(req_act_requirement_id "$manifest" "$CHANGE_DIR")"
 report_summary="$(req_act_report_summary "$report_card")"
 report_verdict="$(req_act_report_verdict "$report_card")"
+output_language="$(req_act_output_language "$report_card")"
 design_goal="$(req_act_design_goal "$design_file")"
 main_risk="$(req_act_main_risk "$design_file")"
 
@@ -97,6 +98,10 @@ fi
 {
   echo "# PR Brief"
   echo
+  echo "## Document Meta"
+  echo
+  echo "- Output language: $output_language"
+  echo
   echo "## Requirement"
   echo
   echo "- $requirement_id"

package/.claude/skills/cc-act/scripts/sync-act-docs.sh

@@ -59,6 +59,7 @@ requirement_id="$(req_act_requirement_id "$manifest" "$CHANGE_DIR")"
 report_summary="$(req_act_report_summary "$report_card")"
 report_verdict="$(req_act_report_verdict "$report_card")"
 spec_sync_ready="$(req_act_spec_sync_ready "$report_card")"
+output_language="$(req_act_output_language "$report_card")"
 design_goal="$(req_act_design_goal "$design_file")"
 main_risk="$(req_act_main_risk "$design_file")"
 
@@ -128,6 +129,10 @@ find "$REPO_ROOT" -maxdepth 2 -type f \( -iname 'README.md' -o -iname 'README*.m
 {
   echo "# Release Note"
   echo
+  echo "## Document Meta"
+  echo
+  echo "- Output language: $output_language"
+  echo
   echo "## User Impact"
   if [[ -n "$report_summary" ]]; then
     echo
@@ -198,6 +203,10 @@ esac
 {
   echo "# Resume Index"
   echo
+  echo "## Document Meta"
+  echo
+  echo "- Output language: $output_language"
+  echo
   echo "- Requirement: $requirement_id"
   echo "- Current stage: cc-act"
   echo "- Current task: ship:$ship_mode"
@@ -218,7 +227,7 @@ esac
   echo "- Ship mode decided as \`$ship_mode\`."
   [[ -n "$pr_url" ]] && echo "- Active PR / MR: $pr_url"
   echo
-  echo "## Blockers"
+  echo "## Follow-Ups"
   echo
   if [[ -s "$tmp_followups" ]]; then
     while IFS= read -r line; do
@@ -245,6 +254,10 @@ esac
 {
   echo "# Doc Sync Report"
   echo
+  echo "## Document Meta"
+  echo
+  echo "- Output language: $output_language"
+  echo
   echo "- Requirement: $requirement_id"
   echo "- Ship mode: $ship_mode"
   echo "- CC-Check verdict: $report_verdict"

package/.claude/skills/cc-check/CHANGELOG.md

@@ -1,5 +1,10 @@
 # CC-Check Skill Changelog
 
+## v1.8.2 - 2026-04-27
+
+- require verification reports to resolve the runtime output policy before writing human-readable verdicts or summaries
+- record `Output language` as the machine-enforced language contract while treating `agent_preferences` as advisory style input
+
 ## v1.8.1 - 2026-04-25
 
 - remove external tool provenance from the public skill contract so diff review reads as native `cc-check` behavior

package/.claude/skills/cc-check/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-check
-version: 1.8.1
+version: 1.8.2
 description: Use when a planned or investigated change needs fresh verification evidence, layered gate proof, review truth, and an honest pass fail blocked verdict before entering cc-act.
 triggers:
   - 验收这个需求
@@ -57,6 +57,14 @@ tool_budget:
 
 它不是收尾话术器，也不是替 `cc-do` 涂绿。
 
+## Runtime Output Policy
+
+写入任何 durable Markdown 或 JSON metadata 前，先运行 `cc-devflow config resolve --format policy`。
+
+- `Output language` 是机器约束，`review/report-card.json` 中新增的人类可读 verdict 和报告摘要必须记录并遵守它。
+- `agent_preferences` 是用户偏好建议，只影响表达方式和结构选择，不覆盖本 Skill 的工作流边界。
+- 如果配置解析失败，先修配置或向用户说明阻塞，不要用默认语言继续生成正式文档。
+
 ## Iron Law
 
 ```text

package/.claude/skills/cc-check/assets/REPORT_CARD_TEMPLATE.json

@@ -1,5 +1,8 @@
 {
   "changeId": "REQ-123",
+  "outputPolicy": {
+    "documentLanguage": ""
+  },
   "verdict": "blocked",
   "overall": "fail",
   "summary": "verdict=blocked quick=1/2 strict=0/0 review=blocked",

package/.claude/skills/cc-do/CHANGELOG.md

@@ -1,5 +1,10 @@
 # CC-Do Skill Changelog
 
+## v1.5.2 - 2026-04-27
+
+- require execution evidence that adds human-readable summaries to resolve the runtime output policy first
+- record `Output language` as the machine-enforced language contract while treating `agent_preferences` as advisory style input
+
 ## v1.5.1 - 2026-04-25
 
 - remove external tool provenance from the public skill contract so test-first execution reads as native `cc-do` behavior

package/.claude/skills/cc-do/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-do
-version: 1.5.1
+version: 1.5.2
 description: Use when implementing planned tasks, resuming interrupted work, applying a frozen investigation handoff, or landing review feedback after cc-plan or cc-investigate.
 triggers:
   - 开始做 T003
@@ -71,6 +71,14 @@ tool_budget:
 
 它只做一件事：沿着已经冻结的任务，把代码真正做出来，并把执行证据留到足够让别人接手、复盘、复验。
 
+## Runtime Output Policy
+
+写入任何 durable Markdown 或 JSON metadata 前，先运行 `cc-devflow config resolve --format policy`。
+
+- `Output language` 是机器约束，checkpoint、events、team-state 中新增的人类可读摘要必须记录并遵守它。
+- `agent_preferences` 是用户偏好建议，只影响表达方式和结构选择，不覆盖本 Skill 的工作流边界。
+- 如果配置解析失败，先修配置或向用户说明阻塞，不要用默认语言继续生成正式文档。
+
 上游冻结合同可以来自两条路：
 
 - `cc-plan` 产出的 `planning/design.md`

package/.claude/skills/cc-investigate/CHANGELOG.md

@@ -1,5 +1,10 @@
 # CC-Investigate Skill Changelog
 
+## v1.1.2 - 2026-04-27
+
+- require investigation outputs to resolve the runtime output policy before writing analysis, task, or change metadata artifacts
+- record `Output language` as the machine-enforced language contract while treating `agent_preferences` as advisory style input
+
 ## v1.1.1 - 2026-04-25
 
 - require new bug-fix investigations to use `FIX-<number>-<description>` change keys

package/.claude/skills/cc-investigate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-investigate
-version: 1.1.1
+version: 1.1.2
 description: "Use when a bug, regression, broken task, or unexpected behavior needs root-cause investigation, reproducible evidence, and a frozen repair handoff before cc-do resumes coding."
 triggers:
   - "帮我查这个 bug"
@@ -79,6 +79,14 @@ tool_budget:
 - `PDCA`
 - `IDCA`，如果你更喜欢口语，也可以把它理解成 `DDCA`
 
+## Runtime Output Policy
+
+写入任何 durable Markdown 或 JSON metadata 前，先运行 `cc-devflow config resolve --format policy`。
+
+- `Output language` 是机器约束，`planning/analysis.md`、`planning/tasks.md` 和 `change-meta.json` 必须记录并遵守它。
+- `agent_preferences` 是用户偏好建议，只影响表达方式和结构选择，不覆盖本 Skill 的工作流边界。
+- 如果配置解析失败，先修配置或向用户说明阻塞，不要用默认语言继续生成正式文档。
+
 ## Read First
 
 1. `PLAYBOOK.md`

package/.claude/skills/cc-investigate/assets/ANALYSIS_TEMPLATE.md

@@ -5,6 +5,7 @@
 - Requirement version:
 - Analysis version:
 - Investigate skill version:
+- Output language:
 - Source roadmap item:
 - Source roadmap version:
 - Incident / bug ID:

package/.claude/skills/cc-investigate/assets/TASKS_TEMPLATE.md

@@ -5,6 +5,7 @@
 - Requirement version:
 - Analysis version:
 - Investigate skill version:
+- Output language:
 - Source bug / incident:
 - Change meta: `change-meta.json`
 

package/.claude/skills/cc-investigate/assets/TASK_MANIFEST_TEMPLATE.json

@@ -2,6 +2,9 @@
   "changeId": "FIX-XXX",
   "requirementId": "FIX-XXX",
   "requirementVersion": "FIX-XXX.v1",
+  "outputPolicy": {
+    "documentLanguage": ""
+  },
   "sourceRoadmap": {
     "itemId": "RM-001",
     "roadmapVersion": "1.0",

package/.claude/skills/cc-plan/CHANGELOG.md

@@ -1,5 +1,10 @@
 # CC-Plan Skill Changelog
 
+## v3.5.4 - 2026-04-27
+
+- require planning outputs to resolve the runtime output policy before writing `planning/design.md`, `planning/tasks.md`, or `change-meta.json`
+- record `Output language` as the machine-enforced language contract while treating `agent_preferences` as advisory style input
+
 ## v3.5.3 - 2026-04-25
 
 - require new planning change directories to use `REQ-<number>-<description>` for requirements and `FIX-<number>-<description>` for fixes

package/.claude/skills/cc-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-plan
-version: 3.5.3
+version: 3.5.4
 description: Use when a requirement, roadmap item, or bug needs scope clarification, design decisions, and executable task breakdown before coding starts.
 triggers:
   - 帮我规划这个需求
@@ -67,6 +67,14 @@ tool_budget:
 
 它的目标不是制造一串 planning 文档，而是把 requirement 压成最少但足够强的交付物，让 `cc-do` 不需要临场补脑。
 
+## Runtime Output Policy
+
+写入任何 durable Markdown 或 JSON metadata 前，先运行 `cc-devflow config resolve --format policy`。
+
+- `Output language` 是机器约束，`planning/design.md`、`planning/tasks.md` 和 `change-meta.json` 必须记录并遵守它。
+- `agent_preferences` 是用户偏好建议，只影响表达方式和结构选择，不覆盖本 Skill 的工作流边界。
+- 如果配置解析失败，先修配置或向用户说明阻塞，不要用默认语言继续生成正式文档。
+
 ## Read First
 
 1. `PLAYBOOK.md`

package/.claude/skills/cc-plan/assets/DESIGN_TEMPLATE.md

@@ -5,6 +5,7 @@
 - Requirement version:
 - Design version:
 - CC-Plan skill version:
+- Output language:
 - Requirement ID:
 - Design mode: `full-design`
 - Why not `tiny-design`:

package/.claude/skills/cc-plan/assets/TASKS_TEMPLATE.md

@@ -5,6 +5,7 @@
 - Requirement version:
 - Design version:
 - CC-Plan skill version:
+- Output language:
 - Source roadmap item:
 - Source roadmap version:
 - Change meta: `change-meta.json`

package/.claude/skills/cc-plan/assets/TASK_MANIFEST_TEMPLATE.json

@@ -2,6 +2,9 @@
   "changeId": "REQ-XXX",
   "requirementId": "REQ-XXX",
   "requirementVersion": "REQ-XXX.v1",
+  "outputPolicy": {
+    "documentLanguage": ""
+  },
   "sourceRoadmap": {
     "itemId": "RM-001",
     "roadmapVersion": "1.0",

package/.claude/skills/cc-plan/assets/TINY_DESIGN_TEMPLATE.md

@@ -5,6 +5,7 @@
 - Requirement version:
 - Design version:
 - CC-Plan skill version:
+- Output language:
 - Requirement ID:
 - Design mode: `tiny-design`
 - Why this stays `tiny-design`:

package/.claude/skills/cc-roadmap/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Roadmap Skill Changelog
 
+## v4.3.2 - 2026-04-27
+
+- require roadmap outputs to resolve the runtime output policy before writing durable roadmap/backlog documents
+- record `Output language` as the machine-enforced language contract while treating `agent_preferences` as advisory style input
+
 ## v4.3.1 - 2026-04-19
 
 - refactor `scripts/roadmap-tracking.js` into focused schema / markdown / store helpers so the CLI stops carrying parsing, rendering, upgrade, and persistence in one 1000-line file

package/.claude/skills/cc-roadmap/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-roadmap
-version: 4.3.1
+version: 4.3.2
 description: "Use when defining, resetting, or narrowing project direction, stage order, or backlog priority before a concrete requirement enters the PDCA loop."
 triggers:
   - "帮我定路线图"
@@ -61,6 +61,14 @@ tool_budget:
 
 它先尽可能收集真实上下文，再逼出真实用户、真实痛点、真实紧迫性，最后把这些现实压成一条能落地、能进入 `cc-plan` 的主线。
 
+## Runtime Output Policy
+
+写入任何 durable Markdown 或 JSON metadata 前，先运行 `cc-devflow config resolve --format policy`。
+
+- `Output language` 是机器约束，`devflow/ROADMAP.md`、`devflow/BACKLOG.md` 和 tracking metadata 必须记录并遵守它。
+- `agent_preferences` 是用户偏好建议，只影响表达方式和结构选择，不覆盖本 Skill 的工作流边界。
+- 如果配置解析失败，先修配置或向用户说明阻塞，不要用默认语言继续生成正式文档。
+
 ## Read First
 
 1. `PLAYBOOK.md`

package/.claude/skills/cc-roadmap/assets/BACKLOG_TEMPLATE.md

@@ -4,6 +4,7 @@
 
 - Roadmap version:
 - Skill version:
+- Output language:
 - Last synced:
 - Current focus stage:
 - Tracking source: `devflow/roadmap-tracking.json`

package/.claude/skills/cc-roadmap/assets/ROADMAP_TEMPLATE.md

@@ -4,6 +4,7 @@
 
 - Roadmap version:
 - Skill version:
+- Output language:
 - Status:
 - Last updated:
 - Owner / decider:

package/.claude/skills/cc-roadmap/assets/TRACKING_TEMPLATE.json

@@ -1,9 +1,12 @@
 {
   "version": 2,
+  "outputPolicy": {
+    "documentLanguage": ""
+  },
   "lastSyncedAt": "2026-04-19",
   "backlogMeta": {
     "roadmapVersion": "roadmap.v1",
-    "skillVersion": "4.3.1",
+    "skillVersion": "4.3.2",
     "currentFocusStage": "Stage 1"
   },
   "dependencyHandoff": {

package/.claude/skills/cc-spec-init/CHANGELOG.md

@@ -1,5 +1,10 @@
 # CC-Spec-Init Skill Changelog
 
+## v1.0.1 - 2026-04-27
+
+- require capability specs, spec indexes, and change metadata to resolve the runtime output policy before writing durable artifacts
+- record `Output language` as the machine-enforced language contract while treating `agent_preferences` as advisory style input
+
 ## v1.0.0 - 2026-04-19
 
 - 初始版 `cc-spec-init`，用于 capability-centered spec 初始化、能力真相源维护和 `change-meta.json` 链路收口。

package/.claude/skills/cc-spec-init/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cc-spec-init
-version: 1.0.0
+version: 1.0.1
 description: Use when you need to initialize capability specs under `devflow/specs/`, create or evolve capability truth sources, generate `change-meta.json`, or validate roadmap/change/spec links before roadmap, planning, or closeout work continues.
 ---
 
@@ -33,6 +33,14 @@ description: Use when you need to initialize capability specs under `devflow/spe
 - 重建 `devflow/specs/INDEX.md`
 - 校验 capability、roadmap item、change 之间的链接完整性
 
+## Runtime Output Policy
+
+写入任何 durable Markdown 或 JSON metadata 前，先运行 `cc-devflow config resolve --format policy`。
+
+- `Output language` 是机器约束，capability spec、`devflow/specs/INDEX.md` 和 `change-meta.json` 必须记录并遵守它。
+- `agent_preferences` 是用户偏好建议，只影响表达方式和结构选择，不覆盖本 Skill 的工作流边界。
+- 如果配置解析失败，先修配置或向用户说明阻塞，不要用默认语言继续生成正式文档。
+
 ## Read First
 
 1. `PLAYBOOK.md`

package/.claude/skills/cc-spec-init/assets/CAPABILITY_TEMPLATE.md

@@ -4,6 +4,7 @@ title: Example Capability
 type: user-visible
 status: partial
 primary_owner: ""
+output_language: ""
 last_verified_at: 2026-04-19
 roadmap_links:
   - RM-001

package/.claude/skills/cc-spec-init/assets/CHANGE_META_TEMPLATE.json

@@ -1,6 +1,9 @@
 {
   "changeId": "REQ-001",
   "requirementId": "REQ-001",
+  "outputPolicy": {
+    "documentLanguage": ""
+  },
   "sourceRoadmap": {
     "itemId": "RM-001",
     "roadmapVersion": "roadmap.v1",

package/.claude/skills/cc-spec-init/assets/INDEX_TEMPLATE.md

@@ -3,6 +3,7 @@
 ## Index Meta
 
 - Spec system version: `spec.v1`
+- Output language:
 - Last updated:
 - Maintainer:
 - Notes:

package/CHANGELOG.md

@@ -9,6 +9,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [4.5.0] - 2026-04-27
+
+### ✨ Runtime YAML Config
+
+v4.5.0 adds a personal/project YAML config mechanism that resolves output policy
+at runtime before durable workflow documents are written.
+
+### Added
+
+- Added `~/.cc-devflow/config.yml`, `<repo>/.cc-devflow/config.yml`, and `<repo>/.cc-devflow/config.local.yml` resolution with deterministic defaults < user < project < local < env < CLI precedence.
+- Added strict `output.document_language` validation for `en` and `zh-CN`, with non-standard preferences preserved under advisory `agent_preferences`.
+- Added `cc-devflow config init|get|set|resolve|doctor` so users can create, inspect, update, trace, and diagnose the effective output contract.
+- Added `config/user-config.template.yml` and `config/schema/cc-devflow-config.schema.json`.
+
+### Changed
+
+- Public workflow skills now resolve config at runtime with `cc-devflow config resolve --format policy` before writing durable Markdown or human-readable metadata.
+- `cc-devflow init` and `cc-devflow adapt --platform codex` no longer bake resolved user policy into managed Skill files.
+
 ## [4.4.1] - 2026-04-25
 
 ### 🔧 Canonical Change Keys + Planning Contract Hardening

package/README.md

@@ -76,6 +76,49 @@ Whole-pack installation ships the six visible workflow skills plus the maintenan
 
 If you are running from a source checkout instead of an installed package, use `node bin/cc-devflow-cli.js ...` or `npm exec -- cc-devflow ...`.
 
+## ⚙️ Personal YAML Config
+
+CC-DevFlow reads personal/project YAML config at runtime before durable workflow documents are written. Create one or more config files:
+
+```text
+~/.cc-devflow/config.yml
+<repo>/.cc-devflow/config.yml
+<repo>/.cc-devflow/config.local.yml
+```
+
+Precedence is deterministic: defaults < user < project < local < env < CLI. `output.document_language` is machine-enforced and currently supports only `en` and `zh-CN`. Non-standard user preferences belong under `agent_preferences`; they are advisory and never override workflow contracts.
+
+Example:
+
+```yaml
+version: 1
+output:
+  document_language: zh-CN
+agent_preferences:
+  general:
+    - Start with the conclusion.
+  documentation:
+    - Keep headings short and avoid marketing language.
+```
+
+Create or edit config with:
+
+```bash
+npx cc-devflow config init --cwd /path/to/your/project --project
+npx cc-devflow config set output.document_language zh-CN --cwd /path/to/your/project --project
+npx cc-devflow config set output.document_language zh-CN --user
+```
+
+Inspect and diagnose the resolved policy with:
+
+```bash
+npx cc-devflow config resolve --cwd /path/to/your/project --format policy
+npx cc-devflow config get output.document_language --cwd /path/to/your/project
+npx cc-devflow config doctor --cwd /path/to/your/project
+```
+
+See `config/user-config.template.yml` for the full sample.
+
 ## 🧩 skills.sh Distribution
 
 [skills.sh](https://skills.sh/) is supported only as a distribution channel for the new `.claude` skills.

package/README.zh-CN.md

@@ -76,6 +76,49 @@ npx cc-devflow adapt --cwd /path/to/your/project --platform antigravity
 
 如果你不是通过已安装包，而是在源码仓库里调试 CLI，本地运行请用 `node bin/cc-devflow-cli.js ...` 或 `npm exec -- cc-devflow ...`。
 
+## ⚙️ 个人 YAML 配置
+
+CC-DevFlow 会在写入 durable workflow 文档前按运行时读取个人 / 项目 YAML 配置。配置文件支持三层：
+
+```text
+~/.cc-devflow/config.yml
+<repo>/.cc-devflow/config.yml
+<repo>/.cc-devflow/config.local.yml
+```
+
+优先级固定为：默认值 < 用户 < 项目 < 本地 < 环境变量 < CLI 参数。`output.document_language` 是机器约束，目前只支持 `en` 和 `zh-CN`。非标偏好统一放在 `agent_preferences` 下，它只作为表达和格式建议，不覆盖 workflow 合同。
+
+最小示例：
+
+```yaml
+version: 1
+output:
+  document_language: zh-CN
+agent_preferences:
+  general:
+    - 先给结论。
+  documentation:
+    - 标题短一些，避免营销腔。
+```
+
+创建或修改配置：
+
+```bash
+npx cc-devflow config init --cwd /path/to/your/project --project
+npx cc-devflow config set output.document_language zh-CN --cwd /path/to/your/project --project
+npx cc-devflow config set output.document_language zh-CN --user
+```
+
+查看和诊断解析后的策略：
+
+```bash
+npx cc-devflow config resolve --cwd /path/to/your/project --format policy
+npx cc-devflow config get output.document_language --cwd /path/to/your/project
+npx cc-devflow config doctor --cwd /path/to/your/project
+```
+
+完整样例见 `config/user-config.template.yml`。
+
 ## 🧩 skills.sh 分发
 
 [skills.sh](https://skills.sh/) 只作为新的 `.claude` Skill 分发渠道使用。