@guanlin4924/devflow-pi 0.1.93 → 0.1.94

package/plugins/devflow-requirements/skills/workflow-requirement-baseline/SKILL.md

@@ -12,12 +12,12 @@ argument-hint: '[@需求文档.md]'
 user-invocable: true
 pattern: inversion+generator+reviewer
 inputs:
-- .planning/PROJECT.md
-- .planning/navigation/INDEX.md
-- .planning/navigation/*.md
-- .planning/milestones/
+- .devflow/planning/PROJECT.md
+- .devflow/planning/navigation/INDEX.md
+- .devflow/planning/navigation/*.md
+- .devflow/planning/milestones/
 - 原始需求文档/PRD/会议纪要/用户描述
-output: .planning/requirements/baseline.md
+output: .devflow/planning/requirements/baseline.md
 phase-gate:
   step1: 加载项目上下文和原始需求
   step2: 需求整理：结构化原文信息
@@ -47,10 +47,10 @@ This skill receives raw requirements and turns them into a stable requirement ba
 
 Before Phase 1, check these mandatory upstream artifacts:
 
-- `.planning/requirements/{feature}/入口分诊.md` and `.meta.json`;
-- `.planning/requirements/{feature}/决策地图.md` and `.meta.json`;
-- `.planning/requirements/{feature}/领域模型记录.md` and `.meta.json`;
-- `.planning/requirements/{feature}/可实现性审查.md` and `.meta.json`.
+- `.devflow/planning/requirements/{feature}/入口分诊.md` and `.meta.json`;
+- `.devflow/planning/requirements/{feature}/决策地图.md` and `.meta.json`;
+- `.devflow/planning/requirements/{feature}/领域模型记录.md` and `.meta.json`;
+- `.devflow/planning/requirements/{feature}/可实现性审查.md` and `.meta.json`.
 
 If any are missing, run the earliest missing main-chain step. Baseline must not become the first place where duplicate capability, fog, terminology ambiguity, or feasibility gaps are discovered.
 
@@ -105,24 +105,24 @@ When triage found partial overlap or prior rejection, preserve it as source mate
 
 Always create or update:
 
-- `.planning/requirements/baseline.md` — unified requirement baseline
-- `.planning/requirements/baseline.meta.json` — structured metadata. Schema defined in `feature-development.yaml` under `steps[requirement-baseline].meta_output.fields`: `review_status`, `fp_count`, `br_count`, `bc_count`, `blocking_pending_count`, `critical_image_missing_count`, `challenge_pending_count`, `code_reality_missing_count`, `current_feature`, `depends_on_count`, plus optional `pending_items`, `risks`, and `key_decisions`.
-- `.planning/requirements/{feature}/traceability.json` — copy the orchestrator `templates/traceability.json` schema and create one atomic `REQ-*` record for every confirmed in-scope requirement. Every record must define `input`、`output`、`behavior`、`orchestration`、`failure`、`verification`; use `N/A` only with a reason when a dimension truly does not apply.
+- `.devflow/planning/requirements/baseline.md` — unified requirement baseline
+- `.devflow/planning/requirements/baseline.meta.json` — structured metadata. Schema defined in `feature-development.yaml` under `steps[requirement-baseline].meta_output.fields`: `review_status`, `fp_count`, `br_count`, `bc_count`, `blocking_pending_count`, `critical_image_missing_count`, `challenge_pending_count`, `code_reality_missing_count`, `current_feature`, `depends_on_count`, plus optional `pending_items`, `risks`, and `key_decisions`.
+- `.devflow/planning/requirements/{feature}/traceability.json` — copy the orchestrator `templates/traceability.json` schema and create one atomic `REQ-*` record for every confirmed in-scope requirement. Every record must define `input`、`output`、`behavior`、`orchestration`、`failure`、`verification`; use `N/A` only with a reason when a dimension truly does not apply.
 
 Before the CP-1 result is reported, run:
 
 ```bash
-python3 <workflow-orchestrator>/scripts/traceability_check.py --file .planning/requirements/{feature}/traceability.json --stage baseline
+python3 <workflow-orchestrator>/scripts/traceability_check.py --file .devflow/planning/requirements/{feature}/traceability.json --stage baseline
 ```
 
 Set `baseline.meta.json.traceability_status` to `passed` only when that command succeeds. A failed traceability check is a blocking baseline defect, not a deferred documentation suggestion.
 
 Do not create by default:
 
-- `.planning/features/{功能名}/功能点梳理.md`
-- `.planning/features/{功能名}/前端技术方案.md`
-- `.planning/features/{功能名}/后端技术方案.md`
-- `.planning/features/{功能名}/变更清单.md`
+- `.devflow/planning/features/{功能名}/功能点梳理.md`
+- `.devflow/planning/features/{功能名}/前端技术方案.md`
+- `.devflow/planning/features/{功能名}/后端技术方案.md`
+- `.devflow/planning/features/{功能名}/变更清单.md`
 
 ## Argument Handling
 
@@ -135,21 +135,21 @@ If both a requirement document and pasted text are provided, use both and record
 
 ### 上游契约（与本技能串联的上游流程）
 
-当 `.planning/requirements/{feature}/入口分诊.md` 存在时（由 `workflow-requirement-triage` 生成）：
+当 `.devflow/planning/requirements/{feature}/入口分诊.md` 存在时（由 `workflow-requirement-triage` 生成）：
 
 1. 将分诊分类写入 `baseline.meta.json.requirement_type` 或需求来源摘要。
 2. 将 `related_code_paths` 作为 Phase 1.5/4 的优先检查入口，但不能直接当作行为结论。
 3. 将 `related_history_paths` 和 prior rejection 记录纳入 Phase 4.5 Challenge Review。
 4. 如果 `route` 不是 `ready_for_wayfinder`，按 Phase 0 路由停止或切换技能。
 
-当 `.planning/requirements/{feature}/决策地图.md` 存在时（由 `workflow-wayfinder` 生成）：
+当 `.devflow/planning/requirements/{feature}/决策地图.md` 存在时（由 `workflow-wayfinder` 生成）：
 
 1. 只有 `决策地图.meta.json.ready_for_baseline = true` 才可继续 baseline。
 2. Destination 和 Known Land 作为需求来源。
-3. 读取 `.planning/requirements/{feature}/wayfinder/WF-*.md` 中 `status=resolved` 的 ticket；其 Findings / Answer 转为 FP/BR/BC 或 `反向审视与用户拍板` 记录。
+3. 读取 `.devflow/planning/requirements/{feature}/wayfinder/WF-*.md` 中 `status=resolved` 的 ticket；其 Findings / Answer 转为 FP/BR/BC 或 `反向审视与用户拍板` 记录。
 4. Open ticket 只能进入待确认或后置探索，不能伪装成已确认需求。
 
-当 `.planning/requirements/{feature}/需求澄清记录.md` 存在时（由 `workflow-demand-clarify` 生成）：
+当 `.devflow/planning/requirements/{feature}/需求澄清记录.md` 存在时（由 `workflow-demand-clarify` 生成）：
 
 1. 优先以 **需求澄清记录.md** 的场景清单和分级任务单作为原始需求来源
 2. 将决策日志中的 L1-L4 决策结论转化为 `key_decisions` 元数据
@@ -157,14 +157,14 @@ If both a requirement document and pasted text are provided, use both and record
 4. 假设验证区内容进入 BR（业务规则），标记为"待上线验证"
 5. 不需要再对用户做"场景反讲"等基础澄清——这些已经在 demand-clarify 阶段完成
 
-当 `.planning/requirements/{feature}/领域模型记录.md` 或 `.planning/CONTEXT.md` 存在时（由 `workflow-domain-modeling` 维护）：
+当 `.devflow/planning/requirements/{feature}/领域模型记录.md` 或 `.devflow/planning/CONTEXT.md` 存在时（由 `workflow-domain-modeling` 维护）：
 
-1. `.planning/CONTEXT.md` 只作为纯词汇表读取，不从中读取需求追溯。
+1. `.devflow/planning/CONTEXT.md` 只作为纯词汇表读取，不从中读取需求追溯。
 2. 使用已确认术语写 FP/BR/BC 名称，避免同义多词。
 3. 从 `领域模型记录.md` 读取术语冲突、边缘案例压力测试和追溯信息，并纳入 Phase 4/7 审查。
 4. ADR 只作为需求决策证据，不展开技术方案。
 
-当 `.planning/requirements/{feature}/可实现性审查.md` 存在时（由 `requirement-feasibility-review` 维护）：
+当 `.devflow/planning/requirements/{feature}/可实现性审查.md` 存在时（由 `requirement-feasibility-review` 维护）：
 
 1. 仅消费其中 `SOURCE_FACT`、`CONFIRMED_DECISION` 和已接受实现方向；不得把 `DERIVED_QUESTION` 或 `ASSUMPTION` 写入 baseline。
 2. 将审查已确认的范围排除、外部能力边界、入口门禁和存量兼容规则转化为 FP/BR/BC。
@@ -174,7 +174,7 @@ If both a requirement document and pasted text are provided, use both and record
 
 **叠加原则：baseline.md 是需求的累积目录，不是单功能快照。每次新增需求时，在已有内容上追加，不覆盖。**
 
-If `.planning/requirements/baseline.md` already exists:
+If `.devflow/planning/requirements/baseline.md` already exists:
 
 1. Read it before restructuring new input. Understand ALL existing features, not just the current one.
 2. **Preserve all confirmed `FP-*`, `BR-*`, `BC-*` from previous features.** Do not delete, renumber, or silently drop them.
@@ -193,7 +193,7 @@ Each new requirement gets its own stable `{功能名}`. **This is additive — a
 3. Keep it short, stable, and safe as a path segment.
 4. Once written to baseline, do not change it in later clarification unless the user explicitly renames the feature.
 5. If the feature name changes, record the old name, new name, reason, and downstream directory impact in `澄清与变更记录`.
-6. The canonical downstream output directory is `.planning/features/{功能名}/`. Multiple features → multiple directories.
+6. The canonical downstream output directory is `.devflow/planning/features/{功能名}/`. Multiple features → multiple directories.
 7. Legacy root `features/{功能名}/` may be read as historical evidence only; new workflow outputs must not use it.
 8. When baseline already has features, the new `{功能名}` must be distinct from existing ones unless the user explicitly says it's an iteration on the same feature.
 
@@ -220,21 +220,21 @@ Load bundled resources only when needed:
 
 Load available project context:
 
-1. `.planning/PROJECT.md`
-2. `.planning/navigation/INDEX.md`
-3. `.planning/navigation/INDEX.md` for the Codebase Registry — identify which codebases are relevant to the requirement
-4. Load the navigation files (`.planning/navigation/{name}.md`) for each relevant codebase from the registry
-5. If `.planning/code-index/` exists, note that `code-index-query` must be used for Phase 1.5 routing and Phase 4 source-reality checks
-6. `.planning/milestones/`
-7. `.planning/requirements/`
-8. `.planning/lessons/`
-9. `.planning/*/CONTEXT.md`
+1. `.devflow/planning/PROJECT.md`
+2. `.devflow/planning/navigation/INDEX.md`
+3. `.devflow/planning/navigation/INDEX.md` for the Codebase Registry — identify which codebases are relevant to the requirement
+4. Load the navigation files (`.devflow/planning/navigation/{name}.md`) for each relevant codebase from the registry
+5. If `.devflow/planning/code-index/` exists, note that `code-index-query` must be used for Phase 1.5 routing and Phase 4 source-reality checks
+6. `.devflow/planning/milestones/`
+7. `.devflow/planning/requirements/`
+8. `.devflow/planning/lessons/`
+9. `.devflow/planning/*/CONTEXT.md`
 
 History model rule:
 
 - This workflow's primary historical artifacts are milestone and planning artifacts, not outbound-call style `features/*.spec.md` files.
-- Use `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, and `.planning/*/CONTEXT.md` first.
-- If `features/`, `.context/lessons/`, or `.context/workflow/` exist in the target project, treat them as optional legacy/project-rule evidence and record that distinction.
+- Use `.devflow/planning/milestones/`, `.devflow/planning/requirements/`, `.devflow/planning/lessons/`, and `.devflow/planning/*/CONTEXT.md` first.
+- If `features/`, `.devflow/context/lessons/`, or `.devflow/context/workflow/` exist in the target project, treat them as optional legacy/project-rule evidence and record that distinction.
 
 Then collect this requirement input:
 
@@ -289,16 +289,16 @@ Use this wording pattern when blocked by an image:
 
 **混合类型**：一个需求可能同时涉及多种类型（如 A+D 混合）。标记为主类型+副类型（如 `A+D`），后续 Phase 按主类型流程推进，在 Phase 3.5 和 Phase 4 兼顾副类型的检查项。
 
-写入 `.planning/requirements/baseline.meta.json` 的 `requirement_type` 字段。
+写入 `.devflow/planning/requirements/baseline.meta.json` 的 `requirement_type` 字段。
 
 ### 1.5.3 Code routing scan before questions
 
 Before asking the user any clarification question, produce an internal code routing summary from project artifacts:
 
-1. Use `.planning/navigation/INDEX.md` to identify relevant codebases.
-2. Read the relevant navigation files (`.planning/navigation/BACKEND.md`, `.planning/navigation/FRONTEND.md`, or other registered codebase files).
+1. Use `.devflow/planning/navigation/INDEX.md` to identify relevant codebases.
+2. Read the relevant navigation files (`.devflow/planning/navigation/BACKEND.md`, `.devflow/planning/navigation/FRONTEND.md`, or other registered codebase files).
 3. Treat navigation as a routing index only. It helps find files quickly, but it is not sufficient evidence for requirement conclusions.
-4. If `.planning/code-index/` exists, use `code-index-query` with requirement concepts to find candidate routes/pages/services/models/tests/resources. Treat these as routing candidates only.
+4. If `.devflow/planning/code-index/` exists, use `code-index-query` with requirement concepts to find candidate routes/pages/services/models/tests/resources. Treat these as routing candidates only.
 5. Confirm likely related source paths exist by listing directories or opening only top-level file structure, imports, class/function names, route declarations, comments, and short module headers.
 6. Do not inspect function bodies, branch logic, data flow, SQL/query details, permission checks, or state transitions in Phase 1.5. Those are Phase 4 Level 2 responsibilities.
 7. Do not conclude "already supported", "not supported", or "conflicting" in Phase 1.5. Only record "possibly related" modules and why they should be checked later.
@@ -471,7 +471,7 @@ seam_type: "新建" | "扩展" | "修改"
 module_depth: "深" | "浅（需下游关注）" | "待评估"
 ```
 
-写入 `.planning/requirements/baseline.md` 中每个 FP 的描述末尾。
+写入 `.devflow/planning/requirements/baseline.md` 中每个 FP 的描述末尾。
 
 ### 完成门禁
 
@@ -508,7 +508,7 @@ Review the decomposed feature points for:
 
 **Level 1: 导航 Call Chain Map 对照（结构层）**
 - 对每个涉及已有代码的 FP，从导航文件的 API Modules / Route-Component Map 提取受影响文件清单
-- 若 `.planning/code-index/` 存在，必须通过 `code-index-query` 用需求关键词、API 路径、页面名、字段名、状态名、表/配置/资源名查询 Symbol Index 和 Relation Graph，补充 navigation 未覆盖的调用方、被调用方、入口和数据流候选
+- 若 `.devflow/planning/code-index/` 存在，必须通过 `code-index-query` 用需求关键词、API 路径、页面名、字段名、状态名、表/配置/资源名查询 Symbol Index 和 Relation Graph，补充 navigation 未覆盖的调用方、被调用方、入口和数据流候选
 - 调用链重叠类型判断：扩展已有 vs 新建分支
 - 契约影响预判：修改已有接口时检查其他调用方
 - 导航无候选时，先通过 `code-index-query` 查 code-index；仍无候选时，再用需求关键词、API 路径、页面名、字段名、状态名通过 `rg` 查实际源码。navigation 不能作为"无相关代码"的唯一证据
@@ -618,7 +618,7 @@ After every user answer in Phase 5:
 
 **叠加模式（baseline 已存在）**：
 
-1. Read existing `.planning/requirements/baseline.md` as the base.
+1. Read existing `.devflow/planning/requirements/baseline.md` as the base.
 2. Append new feature points after the existing ones. Keep all old FP-*, BR-*, BC-* intact.
 3. Update `需求来源` to add the new source entry.
 4. Update `当前功能切片` to list only the current feature's FP/BR/BC IDs, active `SL-*`, deferred slices, and any `depends_on` historical references.
@@ -634,10 +634,10 @@ After every user answer in Phase 5:
 
 Read `assets/baseline-template.md`.
 
-Generate `.planning/requirements/baseline.md` with:
+Generate `.devflow/planning/requirements/baseline.md` with:
 
 - Requirement source summary
-- Feature name and canonical output directory, using one stable `{功能名}` for all downstream `.planning/features/{功能名}/...` outputs
+- Feature name and canonical output directory, using one stable `{功能名}` for all downstream `.devflow/planning/features/{功能名}/...` outputs
 - Structured requirement summary
 - Current feature slice with current FP/BR/BC IDs
 - Slice plan with active `SL-*`, deferred slices, dependencies, and gates
@@ -655,11 +655,11 @@ Generate `.planning/requirements/baseline.md` with:
 - Clarification and change log
 - Review result
 
-Create `.planning/requirements/` if needed.
+Create `.devflow/planning/requirements/` if needed.
 
 Do not create synonym duplicate sections such as `需求来源汇总` or `历史影响` when the template section is named `需求来源` or `与历史功能/里程碑的关联`.
 
-Write `.planning/requirements/baseline.meta.json` with the fields required by the workflow YAML. `review_status` must be `passed` only when the baseline review conclusion is `通过`; otherwise use `failed`. Count blocking items explicitly:
+Write `.devflow/planning/requirements/baseline.meta.json` with the fields required by the workflow YAML. `review_status` must be `passed` only when the baseline review conclusion is `通过`; otherwise use `failed`. Count blocking items explicitly:
 
 - `blocking_pending_count`: unanswered clarification items that block reliable baseline or downstream handoff
 - `critical_image_missing_count`: missing or unclear `critical_image` items
@@ -731,7 +731,7 @@ Completion gate: baseline and baseline.meta.json are written and contain no unre
 
 Before claiming baseline readiness, submit `requirement`、`rule`、`boundary`、`slice` and `acceptance` candidates through `devflow_requirement_graph`. Each requirement candidate must cite source IDs and reference behavior/acceptance IDs returned by the writer. Run `devflow_requirement_graph(action="validate")` and record its result in baseline metadata. Do not directly create `governance.json`, allocate IDs, or set candidate status to `confirmed`.
 
-The baseline handoff must also call `devflow_requirement_graph(action="inspect")` after all proposals and validation. Record the returned graph `revision` and the SHA-256 of `.planning/requirements/{feature}/governance.json` as `graph_revision` and `governance_graph_sha256` in `baseline.meta.json`. The step is not complete if the Core-owned graph file, revision, or hash is missing.
+The baseline handoff must also call `devflow_requirement_graph(action="inspect")` after all proposals and validation. Record the returned graph `revision` and the SHA-256 of `.devflow/planning/requirements/{feature}/governance.json` as `graph_revision` and `governance_graph_sha256` in `baseline.meta.json`. The step is not complete if the Core-owned graph file, revision, or hash is missing.
 
 ```markdown
 - [ ] 每个原始需求映射到 FP-*/BR-*/BC-* 或 out-of-scope

package/plugins/devflow-requirements/skills/workflow-requirement-baseline/assets/baseline-template.md

@@ -5,11 +5,11 @@
 - **来源类型**：{{PRD / 会议纪要 / 用户描述 / 其他}}
 - **来源文件/说明**：{{来源}}
 - **生成时间**：{{日期}}
-- **项目上下文**：`.planning/PROJECT.md`
-- **项目导航**：`.planning/navigation/INDEX.md`
+- **项目上下文**：`.devflow/planning/PROJECT.md`
+- **项目导航**：`.devflow/planning/navigation/INDEX.md`
 - **功能名称**：{{功能名称}}
-- **功能目录名**：{{功能名，用于 .planning/features/{功能名}/}}
-- **下游输出目录**：`.planning/features/{{功能名}}/`
+- **功能目录名**：{{功能名，用于 .devflow/planning/features/{功能名}/}}
+- **下游输出目录**：`.devflow/planning/features/{{功能名}}/`
 
 ## 二、需求整理摘要
 
@@ -138,11 +138,11 @@
 
 | 来源类型 | 路径/范围 | 结论 |
 |----------|-----------|------|
-| 里程碑 | `.planning/milestones/...` | {{相关/无相关/不存在/未扫描原因}} |
-| 历史需求基线 | `.planning/requirements/...` | {{相关/无相关/不存在/未扫描原因}} |
-| 经验教训 | `.planning/lessons/...` | {{相关/无相关/不存在/未扫描原因}} |
-| 阶段上下文 | `.planning/*/CONTEXT.md` | {{相关/无相关/不存在/未扫描原因}} |
-| Legacy/项目规则历史 | `features/` / `.context/lessons/` / `.context/workflow/` | {{如存在则记录；不存在则写“不适用”}} |
+| 里程碑 | `.devflow/planning/milestones/...` | {{相关/无相关/不存在/未扫描原因}} |
+| 历史需求基线 | `.devflow/planning/requirements/...` | {{相关/无相关/不存在/未扫描原因}} |
+| 经验教训 | `.devflow/planning/lessons/...` | {{相关/无相关/不存在/未扫描原因}} |
+| 阶段上下文 | `.devflow/planning/*/CONTEXT.md` | {{相关/无相关/不存在/未扫描原因}} |
+| Legacy/项目规则历史 | `features/` / `.devflow/context/lessons/` / `.devflow/context/workflow/` | {{如存在则记录；不存在则写“不适用”}} |
 
 ### 9.2 关联历史功能/里程碑
 
@@ -169,7 +169,7 @@
 统一使用以下功能目录，后续 skill 不得重新生成不同目录名：
 
 - **功能名**：{{功能名}}
-- **输出目录**：`.planning/features/{{功能名}}/`
+- **输出目录**：`.devflow/planning/features/{{功能名}}/`
 - **当前功能切片**：读取本文档“当前功能切片”中的当前 FP/BR/BC。
 - **当前执行切片**：读取本文档“3.0a 当前执行切片范围”。非当前切片只能作为依赖上下文，不得生成实现任务。
 - **跨功能依赖**：读取 `depends_on` 引用的历史 FP/BR/BC 详情，不得只读当前 FP 而忽略依赖项。
@@ -178,37 +178,37 @@
 
 - 读取本文档的当前功能切片、`depends_on` 引用详情、功能点详情、业务规则、边界场景。
 - 输出必须带当前 `Slice ID`，且只展开当前执行切片。
-- 输出 `.planning/features/{{功能名}}/功能点梳理.md`。
+- 输出 `.devflow/planning/features/{{功能名}}/功能点梳理.md`。
 
 ### 11.1a 给测试指导书
 
-- 读取 `.planning/features/{{功能名}}/功能点梳理.md`（主要输入）和本文档的 FP/BR/BC/CR 关联。
-- 同时读取 `.planning/PROJECT.md`。
+- 读取 `.devflow/planning/features/{{功能名}}/功能点梳理.md`（主要输入）和本文档的 FP/BR/BC/CR 关联。
+- 同时读取 `.devflow/planning/PROJECT.md`。
 - 此步骤为可选，不阻塞下游门禁。
-- 输出 `.planning/features/{{功能名}}/测试指导书.md`。
+- 输出 `.devflow/planning/features/{{功能名}}/测试指导书.md`。
 
 ### 11.2 给前端技术方案
 
-- 读取 `.planning/features/{{功能名}}/功能点梳理.md` 中的页面/组件/字段/交互拆解。
+- 读取 `.devflow/planning/features/{{功能名}}/功能点梳理.md` 中的页面/组件/字段/交互拆解。
 - 只为当前执行切片生成前端方案；后置切片只列为依赖或后续范围。
 - 读取本文档的当前功能切片、跨功能依赖、涉及页面/模块、入口/触发、主流程、边界场景、数据要求。
-- 同时读取 `.planning/navigation/INDEX.md` → 筛选前端类型代码库 → 加载对应 navigation 文件。
-- 输出 `.planning/features/{{功能名}}/前端技术方案.md`。
+- 同时读取 `.devflow/planning/navigation/INDEX.md` → 筛选前端类型代码库 → 加载对应 navigation 文件。
+- 输出 `.devflow/planning/features/{{功能名}}/前端技术方案.md`。
 
 ### 11.3 给后端技术方案
 
-- 读取 `.planning/features/{{功能名}}/功能点梳理.md` 中的 API/服务节点和逻辑维度。
+- 读取 `.devflow/planning/features/{{功能名}}/功能点梳理.md` 中的 API/服务节点和逻辑维度。
 - 只为当前执行切片生成后端方案；共享能力若服务于后置切片，必须有当前切片可验证门禁。
 - 读取本文档的当前功能切片、跨功能依赖、业务规则、数据要求、与历史功能/里程碑的关联、兼容性要求、边界场景、代码现实对照。
-- 同时读取 `.planning/navigation/INDEX.md` → 筛选后端/服务类型代码库 → 加载对应 navigation 文件。
-- 输出 `.planning/features/{{功能名}}/后端技术方案.md`。
+- 同时读取 `.devflow/planning/navigation/INDEX.md` → 筛选后端/服务类型代码库 → 加载对应 navigation 文件。
+- 输出 `.devflow/planning/features/{{功能名}}/后端技术方案.md`。
 
 ### 11.4 给变更清单
 
 - 读取本文档的功能点、业务规则、边界场景、反向审视与用户拍板。
-- 同时读取 `.planning/features/{{功能名}}/前端技术方案.md` 和 `.planning/features/{{功能名}}/后端技术方案.md`。
+- 同时读取 `.devflow/planning/features/{{功能名}}/前端技术方案.md` 和 `.devflow/planning/features/{{功能名}}/后端技术方案.md`。
 - 变更任务必须标注 `Slice ID`；不得生成后置切片的实现任务。
-- 输出 `.planning/features/{{功能名}}/变更清单.md`。
+- 输出 `.devflow/planning/features/{{功能名}}/变更清单.md`。
 
 ### 11.5 给测试验收
 

package/plugins/devflow-requirements/skills/workflow-requirement-baseline/references/antipatterns.md

@@ -35,13 +35,13 @@ Required:
 Wrong:
 
 - Assuming the project keeps outbound-call style `features/*.spec.md` history.
-- Treating `.context/lessons/README.md` as the only source of historical product or requirement decisions.
+- Treating `.devflow/context/lessons/README.md` as the only source of historical product or requirement decisions.
 - Ignoring milestone artifacts because their filenames differ from spec documents.
 
 Required:
 
-- Use this workflow's primary history model first: `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, and `.planning/*/CONTEXT.md`.
-- Treat `features/`, `.context/lessons/`, and `.context/workflow/` as optional legacy or project-rule evidence when present.
+- Use this workflow's primary history model first: `.devflow/planning/milestones/`, `.devflow/planning/requirements/`, `.devflow/planning/lessons/`, and `.devflow/planning/*/CONTEXT.md`.
+- Treat `features/`, `.devflow/context/lessons/`, and `.devflow/context/workflow/` as optional legacy or project-rule evidence when present.
 - Record exactly which history sources were checked.
 
 ## Implementation Leakage

package/plugins/devflow-requirements/skills/workflow-requirement-baseline/references/challenge-review-guide.md

@@ -25,7 +25,7 @@ Do not:
 
 ## Entry Triage Carry-Forward
 
-If `.planning/requirements/{功能名}/入口分诊.md` exists, start challenge review from its findings:
+If `.devflow/planning/requirements/{功能名}/入口分诊.md` exists, start challenge review from its findings:
 
 - Duplicate or already-done evidence feeds C1 and C2.
 - Prior rejection / out-of-scope evidence feeds C3 and may block baseline until the user explicitly reverses it.
@@ -96,8 +96,8 @@ Do not silently choose. The user must decide when the choice changes scope, sema
 
 Search available history before claiming there is no precedent:
 
-- Primary workflow history: `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, and `.planning/*/CONTEXT.md`.
-- Optional legacy/project-rule history when present: `features/`, `.context/lessons/README.md`, `.context/workflow/`, root `AGENTS.md`, and root `CLAUDE.md`.
+- Primary workflow history: `.devflow/planning/milestones/`, `.devflow/planning/requirements/`, `.devflow/planning/lessons/`, and `.devflow/planning/*/CONTEXT.md`.
+- Optional legacy/project-rule history when present: `features/`, `.devflow/context/lessons/README.md`, `.devflow/context/workflow/`, root `AGENTS.md`, and root `CLAUDE.md`.
 
 Do not assume outbound-call style `features/*.spec.md` exists. This workflow's normal long-term memory is milestone/planning based.
 

package/plugins/devflow-requirements/skills/workflow-requirement-baseline/references/project-context-guide.md

@@ -2,20 +2,20 @@
 
 ## 加载顺序
 
-1. `.planning/PROJECT.md` — 项目上下文和已上线能力
-2. `.planning/navigation/INDEX.md` — 代码库注册表（Codebase Registry），从中识别与需求相关的代码库
-3. `.planning/navigation/{name}.md` — 加载 INDEX.md 中标识的相关代码库的导航文件
-4. `.planning/milestones/` — 归档的里程碑记录，是本工作流的主要历史口径
-5. `.planning/requirements/` — 已确认或历史需求基线
-6. `.planning/lessons/` — 跨里程碑经验教训
-7. `.planning/*/CONTEXT.md` — 之前阶段的决策记录
-8. `features/`、`.context/lessons/`、`.context/workflow/` — 仅当目标项目存在时作为兼容历史或项目规则来源，不作为默认历史口径
+1. `.devflow/planning/PROJECT.md` — 项目上下文和已上线能力
+2. `.devflow/planning/navigation/INDEX.md` — 代码库注册表（Codebase Registry），从中识别与需求相关的代码库
+3. `.devflow/planning/navigation/{name}.md` — 加载 INDEX.md 中标识的相关代码库的导航文件
+4. `.devflow/planning/milestones/` — 归档的里程碑记录，是本工作流的主要历史口径
+5. `.devflow/planning/requirements/` — 已确认或历史需求基线
+6. `.devflow/planning/lessons/` — 跨里程碑经验教训
+7. `.devflow/planning/*/CONTEXT.md` — 之前阶段的决策记录
+8. `features/`、`.devflow/context/lessons/`、`.devflow/context/workflow/` — 仅当目标项目存在时作为兼容历史或项目规则来源，不作为默认历史口径
 
 ## 对比分析要点
 
 ### 入口分诊证据复用
 
-- 如果 `.planning/requirements/{功能名}/入口分诊.md` 存在，先读取其中的"已实现/重叠检查"和"历史拒绝/范围检查"。
+- 如果 `.devflow/planning/requirements/{功能名}/入口分诊.md` 存在，先读取其中的"已实现/重叠检查"和"历史拒绝/范围检查"。
 - 分诊结果只能作为 Phase 4/4.5 的优先证据入口，不能替代源码比差。
 - 当分诊结论为 `already_done`、`wontfix` 或 `ready_for_human` 时，baseline 不应继续生成通过状态，除非用户明确改变范围或推翻历史决策。
 - 分诊已搜索的来源必须并入 baseline 的搜索来源记录，避免重复声明"未发现历史"。
@@ -39,8 +39,8 @@
 
 ### 历史口径映射
 
-- outbound-call 中的 `features/*.spec.md` 对应本工作流里的 `.planning/milestones/`、`.planning/requirements/baseline.md` 和阶段 `CONTEXT.md`。
-- outbound-call 中的 `.context/lessons/README.md` 对应本工作流里的 `.planning/lessons/README.md`；如果目标项目同时存在 `.context/lessons/`，将其标为项目规则/遗留经验来源。
+- outbound-call 中的 `features/*.spec.md` 对应本工作流里的 `.devflow/planning/milestones/`、`.devflow/planning/requirements/baseline.md` 和阶段 `CONTEXT.md`。
+- outbound-call 中的 `.devflow/context/lessons/README.md` 对应本工作流里的 `.devflow/planning/lessons/README.md`；如果目标项目同时存在 `.devflow/context/lessons/`，将其标为项目规则/遗留经验来源。
 - 输出时必须写清楚实际搜索了哪些目录或文件，不能只写"未发现历史"。
 
 ## 三级递进审查

package/plugins/devflow-requirements/skills/workflow-requirement-baseline/references/questioning.md

@@ -16,7 +16,7 @@
 4. 已形成代码路由摘要：可能相关模块、候选源码路径、映射到这些路径的需求词、需要 Phase 4 深查的问题
 5. 已将问题绑定到来源、现有模块、候选 FP/BR/BC/CR，或图片阻塞点
 
-如果只读了 `.planning/navigation/*.md` 或只做了 Phase 1.5 轻量路由扫描，不得声称“当前系统已支持/不支持某能力”。只能说“可能相关”，并在 Phase 4 Level 2 下钻源码后再产出行为结论。
+如果只读了 `.devflow/planning/navigation/*.md` 或只做了 Phase 1.5 轻量路由扫描，不得声称“当前系统已支持/不支持某能力”。只能说“可能相关”，并在 Phase 4 Level 2 下钻源码后再产出行为结论。
 
 在 Phase 2 之前，只允许问会阻塞需求理解的输入澄清问题，例如 `critical_image` 无法识别、核心业务目标缺失、需求明显指向多个现有模块但无法判断边界。
 

package/plugins/devflow-requirements/skills/workflow-requirement-baseline/references/requirement-review-checklist.md

@@ -54,7 +54,7 @@ Use this checklist after feature point decomposition and before writing the base
 - [ ] 每个涉及已有代码的 FP，已从导航 Call Chain Map 提取受影响的文件清单：
   - 前端：受影响的路由、页面组件、composable、API 模块
   - 后端：受影响的 handler、service、repository、DAO
-- [ ] 如果 `.planning/code-index/` 存在，已通过 `code-index-query` 查询需求关键词、API 路径、页面名、字段名、状态名、表/配置/资源名，并记录使用到的 symbol/relation id
+- [ ] 如果 `.devflow/planning/code-index/` 存在，已通过 `code-index-query` 查询需求关键词、API 路径、页面名、字段名、状态名、表/配置/资源名，并记录使用到的 symbol/relation id
 - [ ] 调用链重叠类型已判断：扩展已有调用链 vs 新建独立调用链
 - [ ] 契约影响已预判：修改已有接口/参数时，已检查 Call Chain Map 中的其他调用方
 - [ ] 受影响的调用链文件、路由、API 路径已写回 FP 的"关联已有模块"
@@ -88,8 +88,8 @@ Level 2 发现"已存在且一致"或"已存在但冲突"时启动。
 - Historical feature overlap is classified as new, modify, replace, or affect.
 - Compatibility requirements are recorded.
 - Reuse opportunities are checked across business capability, installed library, and project pattern layers.
-- Historical lessons or prior work are searched using the workflow history model first: `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, and `.planning/*/CONTEXT.md`.
-- Legacy history such as `features/` or `.context/lessons/` is used only when present and is labeled as legacy/project-rule evidence.
+- Historical lessons or prior work are searched using the workflow history model first: `.devflow/planning/milestones/`, `.devflow/planning/requirements/`, `.devflow/planning/lessons/`, and `.devflow/planning/*/CONTEXT.md`.
+- Legacy history such as `features/` or `.devflow/context/lessons/` is used only when present and is labeled as legacy/project-rule evidence.
 - The searched sources are recorded before claiming no related history.
 
 ### Challenge Review
@@ -103,7 +103,7 @@ Level 2 发现"已存在且一致"或"已存在但冲突"时启动。
 
 ### Downstream Readiness
 
-- One canonical feature name and `.planning/features/{功能名}/` output directory are defined.
+- One canonical feature name and `.devflow/planning/features/{功能名}/` output directory are defined.
 - Current feature slice and `depends_on` are sufficient for downstream skills to load current scope plus required historical context.
 - Frontend has enough information to identify pages, interactions, states, and API dependencies.
 - Backend has enough information to identify data, services, interfaces, rules, and risks.

package/plugins/devflow-requirements/skills/workflow-requirement-triage/SKILL.md

@@ -11,8 +11,8 @@ description: "Use as the lightweight first step for a new request, bug report, P
 
 Always create or update:
 
-- `.planning/requirements/{功能名}/入口分诊.md`
-- `.planning/requirements/{功能名}/入口分诊.meta.json`
+- `.devflow/planning/requirements/{功能名}/入口分诊.md`
+- `.devflow/planning/requirements/{功能名}/入口分诊.meta.json`
 
 `入口分诊.meta.json` minimum fields:
 
@@ -89,13 +89,13 @@ Search by domain concept, not just exact words.
 
 Required sources:
 
-1. `.planning/requirements/baseline.md`
-2. `.planning/features/`
-3. `.planning/milestones/`
-4. `.planning/lessons/`
-5. `.planning/*/CONTEXT.md`
-6. `.planning/navigation/INDEX.md` and relevant navigation files
-7. `code-index-query` against `.planning/code-index/` when present, for shallow symbol/entrypoint/resource candidate lookup
+1. `.devflow/planning/requirements/baseline.md`
+2. `.devflow/planning/features/`
+3. `.devflow/planning/milestones/`
+4. `.devflow/planning/lessons/`
+5. `.devflow/planning/*/CONTEXT.md`
+6. `.devflow/planning/navigation/INDEX.md` and relevant navigation files
+7. `code-index-query` against `.devflow/planning/code-index/` when present, for shallow symbol/entrypoint/resource candidate lookup
 8. Actual source files only enough to confirm whether a likely capability exists
 
 Search strategy:
@@ -128,13 +128,13 @@ Search for prior decisions that intentionally avoided this request.
 
 Required sources:
 
-- `.planning/requirements/baseline.md`
-- `.planning/features/**/需求梳理.md`
-- `.planning/features/**/需求澄清记录.md`
-- `.planning/features/**/PROGRESS.md`
-- `.planning/milestones/`
-- `.planning/lessons/`
-- `.planning/*/CONTEXT.md`
+- `.devflow/planning/requirements/baseline.md`
+- `.devflow/planning/features/**/需求梳理.md`
+- `.devflow/planning/features/**/需求澄清记录.md`
+- `.devflow/planning/features/**/PROGRESS.md`
+- `.devflow/planning/milestones/`
+- `.devflow/planning/lessons/`
+- `.devflow/planning/*/CONTEXT.md`
 - `.out-of-scope/` if present
 
 Treat these as prior rejection signals:

package/plugins/devflow-requirements/skills/workflow-wayfinder/SKILL.md

@@ -11,11 +11,11 @@ description: "Use when a requirement is too large or foggy for one clarification
 
 Always create or update:
 
-- `.planning/requirements/{功能名}/决策地图.md`
-- `.planning/requirements/{功能名}/决策地图.meta.json`
-- `.planning/requirements/{功能名}/source_units.yaml` (Core-generated)
-- `.planning/requirements/{功能名}/coverage.yaml`
-- `.planning/requirements/{功能名}/wayfinder/WF-xxx.md` for each ticket
+- `.devflow/planning/requirements/{功能名}/决策地图.md`
+- `.devflow/planning/requirements/{功能名}/决策地图.meta.json`
+- `.devflow/planning/requirements/{功能名}/source_units.yaml` (Core-generated)
+- `.devflow/planning/requirements/{功能名}/coverage.yaml`
+- `.devflow/planning/requirements/{功能名}/wayfinder/WF-xxx.md` for each ticket
 
 `决策地图.meta.json` minimum fields:
 
@@ -75,7 +75,7 @@ Do not merge `Grilling` and `Task`: a question to the user and a local artifact
 
 ## Phase 1 — Chart The First Map
 
-1. Read `.planning/requirements/{功能名}/入口分诊.md`.
+1. Read `.devflow/planning/requirements/{功能名}/入口分诊.md`.
 2. Read the raw user input and only the project context needed to understand the uncertainty.
 3. Run the **Source Coherence Gate** below before declaring Fog or creating any Grilling ticket.
 4. Write:

package/src/cli.ts

@@ -5,6 +5,8 @@ import { readFileSync } from "node:fs";
 
 import { formatDoctor, runHostDoctor } from "./doctor.ts";
 import { initializeProject, loadProjectContext, resolveProjectRoot } from "./project-context.ts";
+import { migrateLegacyProjectLayout } from "./project-layout.ts";
+import { InitializationStore } from "./initialization-store.ts";
 import { aggregateUsage, renderUsage } from "./usage-stats.ts";
 import { projectSessionDir } from "./paths.ts";
 
@@ -12,6 +14,7 @@ function usage(): string {
   return [
     "Usage:",
     "  devflow-pi init [project] [--scan]",
+    "  devflow-pi migrate [project] --confirm-active",
     "  devflow-pi doctor [project]",
     "  devflow-pi usage [project]",
     "  devflow-pi [project] [--resume [session-id]] [--prompt <text>] [--mcp] [--yolo]",
@@ -65,6 +68,18 @@ async function main(): Promise<void> {
     }
     return;
   }
+  if (command === "migrate") {
+    const projectArgument = args[1] && !args[1].startsWith("-") ? args[1] : undefined;
+    if (!args.includes("--confirm-active")) throw new Error("Legacy control-plane migration requires --confirm-active");
+    const requested = projectArgument ? path.resolve(projectArgument) : process.cwd();
+    const root = await resolveProjectRoot(requested, { explicit: requested, allowUninitialized: true });
+    const migrated = await migrateLegacyProjectLayout(root, { allowActive: true, allowUnmanifested: true });
+    const manifest = JSON.parse(readFileSync(path.join(root, ".devflow/project.json"), "utf8"));
+    const store = await InitializationStore.open({ root, manifest });
+    try { await store.registerWorkspace(); } finally { store.close(); }
+    console.log(JSON.stringify({ status: "migrated", root, migrated }, null, 2));
+    return;
+  }
   const positionalProject = command && !["doctor", "usage"].includes(command) && !command.startsWith("-") ? command : undefined;
   const requestedProject = ["doctor", "usage"].includes(command || "") ? args[1] : positionalProject;
   const root = await resolveProjectRoot(process.cwd(), { explicit: requestedProject });

package/src/constants.ts

@@ -1,5 +1,5 @@
 export const PRODUCT_NAME = "Devflow Pi";
-export const PRODUCT_VERSION = "0.1.93";
+export const PRODUCT_VERSION = "0.1.94";
 export const PROJECT_SCHEMA_VERSION = 1;
 export const OMP_RUNTIME_VERSION = "17.2.7";
 

package/src/initialization-store.ts

@@ -5,6 +5,7 @@ import path from "node:path";
 import { Database } from "bun:sqlite";
 
 import { projectControlDatabasePath, projectDataDir } from "./paths.ts";
+import { DEVFLOW_SCAN_EXCLUDES, PLANNING_DIRECTORY } from "./project-layout.ts";
 
 export const INITIALIZATION_SCHEMA_VERSION = 2;
 export const FACT_KINDS = [
@@ -323,7 +324,7 @@ export class InitializationStore {
     }));
     const requiredKinds = input.requiredKinds ?? [...FACT_KINDS];
     if (input.mode === "fast" && requiredKinds.length === FACT_KINDS.length) throw new Error("Fast mode must explicitly limit required fact kinds");
-    const config = { ...input, repositories, requiredKinds, includes: input.includes ?? ["**/*"], excludes: input.excludes ?? [".git/**", ".planning/**", ".devflow/**"], adapterVersions: input.adapterVersions ?? {} };
+    const config = { ...input, repositories, requiredKinds, includes: input.includes ?? ["**/*"], excludes: [...new Set([...DEVFLOW_SCAN_EXCLUDES, ...(input.excludes ?? [])])], adapterVersions: input.adapterVersions ?? {} };
     const configJson = canonicalJson(config);
     const contentHash = hash(configJson);
     const existing = this.db.query("SELECT id, revision FROM scan_configs WHERE project_id=? AND content_hash=?").get(this.context.manifest.projectId, contentHash) as { id: string; revision: number } | null;
@@ -510,7 +511,7 @@ export class InitializationStore {
       if (options.indexRef.status === "complete" && (typeof options.indexRef.generation !== "string" || typeof options.indexRef.snapshotHash !== "string")) throw new Error("Complete index references require generation and snapshot hash");
       if (options.indexRef.status === "complete") {
         if (typeof options.indexRef.contentManifestHash !== "string" || typeof options.indexRef.repositoryRevision !== "string") throw new Error("Complete index references require content manifest and repository revision");
-        const indexRoot = path.resolve(this.context.root, String(options.indexRef.stagingPath ?? options.indexRef.path ?? ".planning/code-index"));
+        const indexRoot = path.resolve(this.context.root, String(options.indexRef.stagingPath ?? options.indexRef.path ?? `${PLANNING_DIRECTORY}/code-index`));
         const immutable = path.resolve(indexRoot, String(options.indexRef.immutablePath ?? `snapshots/${options.indexRef.generation}`));
         const snapshotFile = path.join(immutable, "SNAPSHOT.json");
         if (!existsSync(snapshotFile)) throw new Error("Complete index reference does not point to an immutable generation");