@guanlin4924/devflow-pi 0.1.93 → 0.1.94

package/plugins/devflow-quality/skills/workflow-generate-mainflow-cases/SKILL.md

@@ -10,10 +10,10 @@ description: "Use after workflow-execute-phase to bind frozen API/page TC accept
 ## Hard Rules
 
 - MUST NOT hardcode `platform-backend` or `platform-frontend`.
-- MUST derive code roots from `.planning/navigation` and `.context/spec`.
-- MUST use `.planning/code-index/` for fine-grained entrypoint, route, component, API, call, import, and data-flow evidence when present.
+- MUST derive code roots from `.devflow/planning/navigation` and `.devflow/context/spec`.
+- MUST use `.devflow/planning/code-index/` for fine-grained entrypoint, route, component, API, call, import, and data-flow evidence when present.
 - MUST only generate `api-mainflow` and `ui-mainflow` cases.
-- MUST read the frozen `.planning/requirements/{feature}/tests.json` before selecting case scope. Only frozen positive `TC-*` with `test_type: api` or `page` may produce mainflow cases. Core-generated API TC carrying `execution.expect.error_code` is a negative/exception case and is excluded here; it is executed by `run-acceptance-tests`.
+- MUST read the frozen `.devflow/planning/requirements/{feature}/tests.json` before selecting case scope. Only frozen positive `TC-*` with `test_type: api` or `page` may produce mainflow cases. Core-generated API TC carrying `execution.expect.error_code` is a negative/exception case and is excluded here; it is executed by `run-acceptance-tests`.
 - MUST NOT read `SUMMARY.md`, delivery self-reports, or diffs to decide what to test. Current code is allowed only to bind an already frozen TC to an entrypoint, selector, request, or runner adapter.
 - MUST run `scripts/compile_dsl.py` before final output.
 - MUST run `scripts/validate_case_payloads.py` before reporting success.
@@ -32,14 +32,14 @@ The workflow step id is `generate-mainflow-cases`, order `86`, and it depends on
 
 Always create or update:
 
-- `.planning/generated-cases/{feature}/source-map.md`
-- `.planning/generated-cases/{feature}/mainflow-analysis.md`
-- `.planning/generated-cases/{feature}/case-descriptions.json`
-- `.planning/generated-cases/{feature}/case-import-payloads.json`
-- `.planning/generated-cases/{feature}/validation-report.md`
-- `.planning/phases/{phase}/MAINFLOW-CASES.md`
+- `.devflow/planning/generated-cases/{feature}/source-map.md`
+- `.devflow/planning/generated-cases/{feature}/mainflow-analysis.md`
+- `.devflow/planning/generated-cases/{feature}/case-descriptions.json`
+- `.devflow/planning/generated-cases/{feature}/case-import-payloads.json`
+- `.devflow/planning/generated-cases/{feature}/validation-report.md`
+- `.devflow/planning/phases/{phase}/MAINFLOW-CASES.md`
 
-The discovery script also writes support artifact `.planning/generated-cases/{feature}/codebase-discovery.json`.
+The discovery script also writes support artifact `.devflow/planning/generated-cases/{feature}/codebase-discovery.json`.
 
 ## Resource Loading
 
@@ -53,29 +53,29 @@ Read these references before generating cases:
 
 ## Process
 
-1. Read `.planning/STATE.md` and resolve `{feature}` and `{phase}`.
+1. Read `.devflow/planning/STATE.md` and resolve `{feature}` and `{phase}`.
 2. Run codebase discovery:
 
    ```text
-   devflow_mainflow(action="discover", args=["--output", ".planning/generated-cases/{feature}/codebase-discovery.json"])
+   devflow_mainflow(action="discover", args=["--output", ".devflow/planning/generated-cases/{feature}/codebase-discovery.json"])
    ```
 
    Stop if it exits non-zero.
 
 3. Read the frozen TC suite first. Record the source `TC-*` for every selected mainflow case; a missing or stale source TC is a blocker. Then read planning inputs when present:
-   - `.planning/requirements/baseline.md`
-   - `.planning/features/{feature}/功能点梳理.md`
-   - `.planning/features/{feature}/UI-SPEC.md`
-   - `.planning/features/{feature}/前端技术方案.md`
-   - `.planning/features/{feature}/后端技术方案.md`
-   - `.planning/features/{feature}/变更清单.md`
-   - `.planning/features/{feature}/PROGRESS.md`
+   - `.devflow/planning/requirements/baseline.md`
+   - `.devflow/planning/features/{feature}/功能点梳理.md`
+   - `.devflow/planning/features/{feature}/UI-SPEC.md`
+   - `.devflow/planning/features/{feature}/前端技术方案.md`
+   - `.devflow/planning/features/{feature}/后端技术方案.md`
+   - `.devflow/planning/features/{feature}/变更清单.md`
+   - `.devflow/planning/features/{feature}/PROGRESS.md`
 
 4. Read discovery output, then read each discovered codebase's navigation and spec files. Select scan targets by codebase type:
    - Backend: router/controller, service/usecase, schema/dto/request/response, model/entity, API entry.
    - Frontend: router, pages/views, api/client, types/contracts, stores/hooks/components related to the feature.
 
-5. If `.planning/code-index/` exists, query symbols and relations for candidate entrypoints and mainflow paths:
+5. If `.devflow/planning/code-index/` exists, query symbols and relations for candidate entrypoints and mainflow paths:
    - Backend/API: `routes_to`, `calls`, `reads`, `writes`, `config_uses`, `tested_by`.
    - Frontend/UI: route/page/component symbols, `routes_to`, `imports`, `calls` into API clients, store/hook relations.
    Read `evidence_path:evidence_line` before using an edge in case selection.
@@ -86,7 +86,7 @@ Read these references before generating cases:
 10. Compile descriptions into strict DSL:
 
    ```text
-   devflow_mainflow(action="compile", args=[".planning/generated-cases/{feature}/case-descriptions.json", "--output", ".planning/generated-cases/{feature}/case-import-payloads.json"])
+   devflow_mainflow(action="compile", args=[".devflow/planning/generated-cases/{feature}/case-descriptions.json", "--output", ".devflow/planning/generated-cases/{feature}/case-import-payloads.json"])
    ```
 
    Stop if it exits non-zero. The compiler owns all target key selection, strategy decisions, and assertion formatting.
@@ -94,12 +94,12 @@ Read these references before generating cases:
 11. Validate compiled payloads:
 
     ```text
-    devflow_mainflow(action="validate", args=[".planning/generated-cases/{feature}/case-import-payloads.json", "--discovery", ".planning/generated-cases/{feature}/codebase-discovery.json", "--output", ".planning/generated-cases/{feature}/validation-report.md"])
+    devflow_mainflow(action="validate", args=[".devflow/planning/generated-cases/{feature}/case-import-payloads.json", "--discovery", ".devflow/planning/generated-cases/{feature}/codebase-discovery.json", "--output", ".devflow/planning/generated-cases/{feature}/validation-report.md"])
     ```
 
     Stop if it exits non-zero.
 
-11. Write `.planning/phases/{phase}/MAINFLOW-CASES.md` summarizing:
+11. Write `.devflow/planning/phases/{phase}/MAINFLOW-CASES.md` summarizing:
     - Generated case count by tag.
     - Import payload path.
     - Validation status.

package/plugins/devflow-quality/skills/workflow-generate-mainflow-cases/references/codebase-discovery.md

@@ -1,16 +1,16 @@
 # Codebase Discovery
 
-Use discovery before reading feature source files. The goal is to make the skill portable across projects that have valid `.planning` and `.context/spec` initialization artifacts.
+Use discovery before reading feature source files. The goal is to make the skill portable across projects that have valid `.devflow/planning` and `.devflow/context/spec` initialization artifacts.
 
 ## Required Sources
 
 Read and cross-check:
 
-- `.planning/STATE.md`
-- `.planning/navigation/INDEX.md`
-- `.context/spec/index.md`
-- `.planning/navigation/{CODEBASE}.md`
-- `.context/spec/{domain}/{CODEBASE}.md`
+- `.devflow/planning/STATE.md`
+- `.devflow/planning/navigation/INDEX.md`
+- `.devflow/context/spec/index.md`
+- `.devflow/planning/navigation/{CODEBASE}.md`
+- `.devflow/context/spec/{domain}/{CODEBASE}.md`
 
 Do not infer code roots from common directory names. Treat the navigation/spec registry as the source of truth.
 
@@ -19,13 +19,13 @@ Do not infer code roots from common directory names. Treat the navigation/spec r
 Run:
 
 ```text
-devflow_mainflow(action="discover", args=["--output", ".planning/generated-cases/{feature}/codebase-discovery.json"])
+devflow_mainflow(action="discover", args=["--output", ".devflow/planning/generated-cases/{feature}/codebase-discovery.json"])
 ```
 
 The script must fail if:
 
-- `.planning/navigation/INDEX.md` is missing.
-- `.context/spec/index.md` is missing.
+- `.devflow/planning/navigation/INDEX.md` is missing.
+- `.devflow/context/spec/index.md` is missing.
 - A registered codebase lacks a root path, navigation path, or spec path.
 - A registered root path does not exist.
 - A registered navigation/spec file does not exist.

package/plugins/devflow-quality/skills/workflow-generate-mainflow-cases/references/project-dsl-contract.md

@@ -25,7 +25,7 @@ Legacy normalization input is an object with metadata and cases:
       },
       "source_evidence": [
         {
-          "path": ".planning/features/Feature/后端技术方案.md",
+          "path": ".devflow/planning/features/Feature/后端技术方案.md",
           "line": 120,
           "reason": "API contract source"
         }

package/plugins/devflow-quality/skills/workflow-generate-mainflow-cases/scripts/compile_dsl.py

@@ -559,13 +559,13 @@ def compile_all(payload: dict[str, Any], frozen_mainflow_tc_ids: set[str] | None
 
 def frozen_mainflow_tc_ids_from_cwd(cwd: Path) -> set[str] | None:
     """Return the frozen API/page suite for new workflows, else preserve legacy compilation."""
-    state_path = cwd / ".planning" / "STATE.md"
+    state_path = cwd / ".devflow/planning" / "STATE.md"
     if not state_path.is_file():
         return None
     match = re.search(r"^current_feature:\s*['\"]?([^'\"\n]+)", state_path.read_text(encoding="utf-8"), re.MULTILINE)
     if not match:
         return None
-    suite_path = cwd / ".planning" / "requirements" / match.group(1).strip() / "tests.json"
+    suite_path = cwd / ".devflow/planning" / "requirements" / match.group(1).strip() / "tests.json"
     if not suite_path.is_file():
         return None
     suite = json.loads(suite_path.read_text(encoding="utf-8"))

package/plugins/devflow-quality/skills/workflow-generate-mainflow-cases/scripts/discover_codebases.py

@@ -10,8 +10,8 @@ from datetime import datetime, timezone
 from pathlib import Path
 
 
-NAV_INDEX = Path(".planning/navigation/INDEX.md")
-SPEC_INDEX = Path(".context/spec/index.md")
+NAV_INDEX = Path(".devflow/planning/navigation/INDEX.md")
+SPEC_INDEX = Path(".devflow/context/spec/index.md")
 
 
 def clean_cell(value: str) -> str:

package/plugins/devflow-quality/skills/workflow-release-closeout/SKILL.md

@@ -11,13 +11,13 @@ description: "在冻结需求验收测试全部通过后，执行 Devflow 自有
 
 ## 必须读取
 
-- `.planning/requirements/{feature}/tests.json`
-- `.planning/test-runs/{feature}/acceptance-results.json`
-- `.planning/features/{feature}/变更清单.md`
-- `.planning/code-index/AUDIT.md`
-- `.planning/PROJECT.md`
-- `.planning/STATE.md`
-- `.planning/navigation/INDEX.md`
+- `.devflow/planning/requirements/{feature}/tests.json`
+- `.devflow/planning/test-runs/{feature}/acceptance-results.json`
+- `.devflow/planning/features/{feature}/变更清单.md`
+- `.devflow/planning/code-index/AUDIT.md`
+- `.devflow/planning/PROJECT.md`
+- `.devflow/planning/STATE.md`
+- `.devflow/planning/navigation/INDEX.md`
 
 ## 归档前置条件（全部满足）
 
@@ -32,17 +32,17 @@ description: "在冻结需求验收测试全部通过后，执行 Devflow 自有
 ## 收口动作
 
 1. 读取 Core-owned `acceptance-results.json`，计算通过/失败/阻塞数量。
-2. 更新 `.planning/navigation/INDEX.md`，记录本次 code-index revision 和验收结果 fingerprint。
-3. 在 `.planning/milestones/` 写入本版本的 ROADMAP、需求覆盖、测试结果、变更清单和已接受风险摘要。
-4. 更新 `.planning/PROJECT.md` 的当前版本与下一步目标。
-5. 通过 Core 状态工具更新 `.planning/STATE.md`，将当前 feature 标记为完成。
+2. 更新 `.devflow/planning/navigation/INDEX.md`，记录本次 code-index revision 和验收结果 fingerprint。
+3. 在 `.devflow/planning/milestones/` 写入本版本的 ROADMAP、需求覆盖、测试结果、变更清单和已接受风险摘要。
+4. 更新 `.devflow/planning/PROJECT.md` 的当前版本与下一步目标。
+5. 通过 Core 状态工具更新 `.devflow/planning/STATE.md`，将当前 feature 标记为完成。
 6. 归档写入完成后才允许创建 git tag；是否提交或推送由用户明确决定。
 
 ## 输出
 
-- `.planning/milestones/{version}-CLOSEOUT.md`
-- 更新后的 `.planning/PROJECT.md`
-- 更新后的 `.planning/STATE.md`
-- 更新后的 `.planning/navigation/INDEX.md`
+- `.devflow/planning/milestones/{version}-CLOSEOUT.md`
+- 更新后的 `.devflow/planning/PROJECT.md`
+- 更新后的 `.devflow/planning/STATE.md`
+- 更新后的 `.devflow/planning/navigation/INDEX.md`
 
 归档文件是结果摘要，不是通过依据；唯一的验收真相是 Core-owned `acceptance-results.json` 和 code-index 审计结果。

package/plugins/devflow-quality/skills/workflow-run-acceptance-tests/SKILL.md

@@ -11,7 +11,7 @@ description: "Execute the frozen TC acceptance suite after code review. Use the
 
 测试意图只能读取：
 
-- `.planning/requirements/{feature}/tests.json` 中已冻结且未 stale 的 `TC-*`；
+- `.devflow/planning/requirements/{feature}/tests.json` 中已冻结且未 stale 的 `TC-*`；
 - 图谱中被 TC 引用的已确认 REQ / BR / BC / AC、契约与架构风险；
 - 初始化发现的测试工具链能力。
 
@@ -19,7 +19,7 @@ description: "Execute the frozen TC acceptance suite after code review. Use the
 
 禁止读取或使用以下内容来扩大、缩小或补造验收范围：
 
-- `.planning/phases/{phase}/SUMMARY.md`；
+- `.devflow/planning/phases/{phase}/SUMMARY.md`；
 - agent 的交付自述、代码 diff 或“已完成”结论；
 - 未冻结的临时需求列表。
 
@@ -29,7 +29,7 @@ description: "Execute the frozen TC acceptance suite after code review. Use the
 2. 读取冻结 TC 与其 oracle、前置数据、身份和自动化模式。
    对 `api_refs`、`workload_refs` 和 `risk_refs` 指向的专项用例，保留其契约、性能/迁移或韧性义务；没有适配器或环境时必须写为 blocked，不能用普通主流程替代。
 3. 读取代码审查报告、代码索引和实际源码，仅为每个 TC 绑定运行适配器；不得改变 TC 的断言、范围或预期。
-4. 写入 `.planning/features/{feature}/acceptance-test-bindings.json`：
+4. 写入 `.devflow/planning/features/{feature}/acceptance-test-bindings.json`：
    - 固定 `test_suite.graph_revision` 与 `fingerprint`；
    - 每个 TC 恰好一条绑定；
    - `mode` 必须与冻结 TC 的 `automation_mode` 一致；
@@ -44,7 +44,7 @@ description: "Execute the frozen TC acceptance suite after code review. Use the
 
 ## 输出
 
-- `.planning/features/{feature}/acceptance-test-bindings.json`
-- `.planning/test-runs/{feature}/acceptance-results.json`
+- `.devflow/planning/features/{feature}/acceptance-test-bindings.json`
+- `.devflow/planning/test-runs/{feature}/acceptance-results.json`
 
 `acceptance-results.json` 是 Core-owned 的执行事实；Markdown 结论不能替代它。

package/plugins/devflow-requirements/skills/requirement-feasibility-review/SKILL.md

@@ -15,7 +15,7 @@ In the main delivery chain, run this skill after `workflow-wayfinder` and `workf
 
 Read the raw requirement, meeting decisions, relevant existing requirement artifacts, and only the project/context sources needed to verify claims. Treat a later confirmed meeting decision as higher priority than an earlier conflicting PRD statement.
 
-If the project has `.planning/requirements/{feature}/`, create or update:
+If the project has `.devflow/planning/requirements/{feature}/`, create or update:
 
 - `可实现性审查.md`
 - `可实现性审查.meta.json`

package/plugins/devflow-requirements/skills/workflow-demand-clarify/SKILL.md

@@ -13,7 +13,7 @@ user-invocable: true
 pattern: inversion+generator
 inputs:
 - 用户的一句话需求/场景描述/业务反馈
-output: .planning/requirements/{功能名}/需求澄清记录.md
+output: .devflow/planning/requirements/{功能名}/需求澄清记录.md
 phase-gate:
   step1: 场景共建：强制反讲确认业务故事
   step2: 决策驱动：L1-L4 分层决策树问答
@@ -37,7 +37,7 @@ allowed-tools:
 
 ## Phase 0 — Wayfinder Ticket 检查
 
-开始前读取 `.planning/requirements/{功能名}/wayfinder/WF-*.md`：
+开始前读取 `.devflow/planning/requirements/{功能名}/wayfinder/WF-*.md`：
 
 - 仅在当前 Wayfinder Grilling ticket 明确要求一轮 L1-L4 访谈时继续。
 - 若不存在对应 ticket，先执行或回到 `workflow-wayfinder`；不要从分诊直接进入澄清。
@@ -69,8 +69,8 @@ allowed-tools:
 
 Always create or update:
 
-- `.planning/requirements/{功能名}/需求澄清记录.md` — 包含场景清单、决策日志、分级任务单
-- `.planning/requirements/{功能名}/需求澄清记录.meta.json` — 结构化元数据
+- `.devflow/planning/requirements/{功能名}/需求澄清记录.md` — 包含场景清单、决策日志、分级任务单
+- `.devflow/planning/requirements/{功能名}/需求澄清记录.meta.json` — 结构化元数据
 
 ### 输出契约（下游消费约定）
 
@@ -81,8 +81,8 @@ Always create or update:
 3. **分级任务单** → 核心确定区的 FP 直接进入 baseline；假设验证区的 BR 标记为待确认
 
 本技能不输出的内容（留给下游负责）：
-- `.planning/requirements/baseline.md` — 由 workflow-requirement-baseline 生成
-- `.planning/features/{功能名}/功能点梳理.md` — 由 workflow-feature-breakdown 生成
+- `.devflow/planning/requirements/baseline.md` — 由 workflow-requirement-baseline 生成
+- `.devflow/planning/features/{功能名}/功能点梳理.md` — 由 workflow-feature-breakdown 生成
 - 任何技术方案 — 由 workflow-frontend/backend-tech-spec 生成
 
 ## 第一阶段：场景共建
@@ -203,7 +203,7 @@ Always create or update:
 - 单个答案会改变大部分后续问题。
 - 预计要拆多个 active slice 才能写出可靠 baseline。
 
-切换时写入 `需求澄清记录.md` 的"转探索原因"，并创建或更新 `.planning/requirements/{功能名}/决策地图.md`。后续由 `workflow-wayfinder` 维护 Destination / Frontier / Fog / Out of Scope 和 Research / Prototype / Grilling / Task ticket。
+切换时写入 `需求澄清记录.md` 的"转探索原因"，并创建或更新 `.devflow/planning/requirements/{功能名}/决策地图.md`。后续由 `workflow-wayfinder` 维护 Destination / Frontier / Fog / Out of Scope 和 Research / Prototype / Grilling / Task ticket。
 
 ## 第二阶段.5 — 领域词汇维护（调用 workflow-domain-modeling 纪律）
 
@@ -225,7 +225,7 @@ Always create or update:
 
 ### 写入规则
 
-写入 `.planning/CONTEXT.md`：
+写入 `.devflow/planning/CONTEXT.md`：
 
 ```markdown
 ## 词汇表
@@ -236,8 +236,8 @@ Always create or update:
 | 订单快照 | 订单状态变更时的全字段副本 | 当前订单主表最新值 |
 ```
 
-如果 `.planning/CONTEXT.md` 不存在，创建它。
-来源、决策层级、对应需求和术语变更历史写入 `.planning/requirements/{功能名}/领域模型记录.md`，不要写入 CONTEXT.md。
+如果 `.devflow/planning/CONTEXT.md` 不存在，创建它。
+来源、决策层级、对应需求和术语变更历史写入 `.devflow/planning/requirements/{功能名}/领域模型记录.md`，不要写入 CONTEXT.md。
 
 ### 术语冲突处理
 

package/plugins/devflow-requirements/skills/workflow-domain-modeling/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-domain-modeling
-description: "Use as the mandatory domain-modeling step after workflow-wayfinder and before requirement-feasibility-review; also use during later clarification or planning when domain terms, business concepts, status names, ownership, or decision records may be ambiguous. Challenges the glossary, stress-tests relationships, updates .planning/CONTEXT.md, and creates ADR notes only for hard-to-reverse surprising trade-offs."
+description: "Use as the mandatory domain-modeling step after workflow-wayfinder and before requirement-feasibility-review; also use during later clarification or planning when domain terms, business concepts, status names, ownership, or decision records may be ambiguous. Challenges the glossary, stress-tests relationships, updates .devflow/planning/CONTEXT.md, and creates ADR notes only for hard-to-reverse surprising trade-offs."
 ---
 
 # Workflow: Domain Modeling（领域模型主动维护）
@@ -11,25 +11,25 @@ description: "Use as the mandatory domain-modeling step after workflow-wayfinder
 
 Always update when changes are found:
 
-- `.planning/CONTEXT.md`
-- `.planning/requirements/{功能名}/领域模型记录.md`
-- `.planning/requirements/{功能名}/领域模型记录.meta.json`
+- `.devflow/planning/CONTEXT.md`
+- `.devflow/planning/requirements/{功能名}/领域模型记录.md`
+- `.devflow/planning/requirements/{功能名}/领域模型记录.meta.json`
 
 Only create ADR when the ADR gate passes:
 
-- `.planning/adr/{编号}-{slug}.md`
+- `.devflow/planning/adr/{编号}-{slug}.md`
 
 ## Phase 1 — Load Existing Language
 
 Read, if present:
 
-1. `.planning/CONTEXT.md`
-2. `.planning/requirements/{功能名}/决策地图.md`
-3. `.planning/requirements/{功能名}/wayfinder/WF-*.md` 中已解决 ticket
-4. `.planning/requirements/baseline.md`
-5. `.planning/features/**/需求梳理.md`
-6. `.planning/features/**/需求澄清记录.md`
-7. `.planning/*/CONTEXT.md`
+1. `.devflow/planning/CONTEXT.md`
+2. `.devflow/planning/requirements/{功能名}/决策地图.md`
+3. `.devflow/planning/requirements/{功能名}/wayfinder/WF-*.md` 中已解决 ticket
+4. `.devflow/planning/requirements/baseline.md`
+5. `.devflow/planning/features/**/需求梳理.md`
+6. `.devflow/planning/features/**/需求澄清记录.md`
+7. `.devflow/planning/*/CONTEXT.md`
 8. Relevant source names from navigation: model names, table names, enum/status constants, route names, page titles
 
 Do not load broad source bodies unless a term conflict depends on exact code behavior.
@@ -38,7 +38,7 @@ Do not load broad source bodies unless a term conflict depends on exact code beh
 
 For each important term in the current conversation or artifact:
 
-1. **Existing definition check**: does `.planning/CONTEXT.md` already define it?
+1. **Existing definition check**: does `.devflow/planning/CONTEXT.md` already define it?
 2. **Collision check**: is the same word used for multiple concepts?
 3. **Synonym check**: are multiple words used for the same concept?
 4. **Code-language check**: do routes, models, fields, enum constants, and UI labels use different names?
@@ -65,7 +65,7 @@ For each core relationship, invent at least two edge cases to test whether the d
 
 If an edge case changes the meaning of a term, update the glossary or create a pending question. Do not turn edge cases into new scope automatically.
 
-## Phase 4 — Update `.planning/CONTEXT.md`
+## Phase 4 — Update `.devflow/planning/CONTEXT.md`
 
 Use this section shape:
 
@@ -81,7 +81,7 @@ Rules:
 - Definition must be domain-facing, not implementation-facing.
 - Add `反例/不包括` whenever a term could be confused with a neighbor concept.
 - Preserve existing terms unless the user confirmed a replacement.
-- Keep `.planning/CONTEXT.md` pure glossary. Do not store implementation details, FP/BR/BC IDs, source paths, requirement traceability, decision levels, or change history in it.
+- Keep `.devflow/planning/CONTEXT.md` pure glossary. Do not store implementation details, FP/BR/BC IDs, source paths, requirement traceability, decision levels, or change history in it.
 - If a definition changes, record the old definition, new definition, reason, source, decision level, related requirement, and edge cases in `领域模型记录.md`.
 
 Use `领域模型记录.md` for traceability:
@@ -106,7 +106,7 @@ Create an ADR only when all three conditions are true:
 2. **Surprising**: a future developer could reasonably choose a different direction without this record.
 3. **Real trade-off**: at least two credible options exist and each has a cost.
 
-If any condition is false, record the decision in `领域模型记录.md` or `.planning/CONTEXT.md`, not ADR.
+If any condition is false, record the decision in `领域模型记录.md` or `.devflow/planning/CONTEXT.md`, not ADR.
 
 ADR template:
 
@@ -153,15 +153,15 @@ Submit bounded candidates through `devflow_requirement_graph`: use `term` for sh
 When this run adds or changes domain language, replace `<feature>` and run:
 
 ```bash
-test -s .planning/CONTEXT.md
-test -s .planning/requirements/<feature>/领域模型记录.md
-python3 -m json.tool .planning/requirements/<feature>/领域模型记录.meta.json >/dev/null
-grep -q '"feature_name"' .planning/requirements/<feature>/领域模型记录.meta.json
-grep -q '"terms_added"' .planning/requirements/<feature>/领域模型记录.meta.json
-grep -q '"terms_changed"' .planning/requirements/<feature>/领域模型记录.meta.json
-grep -q '## 词汇表' .planning/CONTEXT.md
-grep -q '## 术语变更记录' .planning/requirements/<feature>/领域模型记录.md
-grep -q '## 边缘案例压测' .planning/requirements/<feature>/领域模型记录.md
+test -s .devflow/planning/CONTEXT.md
+test -s .devflow/planning/requirements/<feature>/领域模型记录.md
+python3 -m json.tool .devflow/planning/requirements/<feature>/领域模型记录.meta.json >/dev/null
+grep -q '"feature_name"' .devflow/planning/requirements/<feature>/领域模型记录.meta.json
+grep -q '"terms_added"' .devflow/planning/requirements/<feature>/领域模型记录.meta.json
+grep -q '"terms_changed"' .devflow/planning/requirements/<feature>/领域模型记录.meta.json
+grep -q '## 词汇表' .devflow/planning/CONTEXT.md
+grep -q '## 术语变更记录' .devflow/planning/requirements/<feature>/领域模型记录.md
+grep -q '## 边缘案例压测' .devflow/planning/requirements/<feature>/领域模型记录.md
 ```
 
 Pass only when every command exits with code 0, the metadata is valid JSON with the required counters, and each changed term has both a domain-facing glossary definition and a traceability record. If no language changed, record that no-change conclusion in the feature's domain-model record; do not create an ADR. If a check fails, repair the glossary, record, or metadata before continuing to baseline or technical planning.