@guanlin4924/devflow-pi 0.1.93 → 0.1.95

package/plugins/devflow-core/skills/workflow-pipeline/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-pipeline
-description: Use when running or resuming the full .planning delivery pipeline from requirements through implementation, frozen acceptance tests, and Devflow release closeout.
+description: Use when running or resuming the full .devflow/planning delivery pipeline from requirements through implementation, frozen acceptance tests, and Devflow release closeout.
 ---
 
 <objective>
@@ -49,7 +49,7 @@ pipeline 本身不包含执行规则——所有门禁、CP 协议、失败分
 | 80 | execute | 代码执行 |
 | 84 | code-index-refresh | 刷新机器代码索引并审查 |
 | 85 | code-review | 代码审查（完成标准验证） |
-| 86 | generate-mainflow-cases | 主流程自动化用例生成 |
+| 86 | human-acceptance | 人工验收与开发者同步 |
 | 88 | run-acceptance-tests | 冻结 TC 验收执行 |
 | 100 | release-closeout | 验收通过后的版本收口与里程碑归档 |
 
@@ -60,6 +60,8 @@ pipeline 本身不包含执行规则——所有门禁、CP 协议、失败分
 
 双轨制原则：API 契约是分叉前的共同事实，`integration-verify` 是合并前的强门禁。单轨只产出局部轨道文档，不代表完整交付。
 
+`workflow-generate-mainflow-cases` 不是独立 workflow step，而是 `run-acceptance-tests` 绑定阶段的组成部分：对执行面为 `ui` / `api_flow` 且绑定为 `automated` 的 TC，必须先生成 v1 DSL 并经 `devflow_approval` 批准执行计划，否则该 TC 保持 blocked。人工 TC 结果同样只经 `human_result` 批准计入聚合门禁。
+
 如果提供了需求文档但未指定功能名，从文档标题自动提取功能名。
 
 ## 1. 需求入口前置路由
@@ -97,11 +99,11 @@ devflow_state(action="inspect")
 | `blocked` | 将阻塞原因报告给用户 |
 | `workflow_complete` | 报告完成，流程结束 |
 
-**降级策略**：`.planning/STATE.md` 是唯一规范状态源。如果 `inspect_state.rb` 不可用或 STATE 缺少 YAML front matter，报告主流程阻塞并提示运行 `init_workflow.rb --write`、`init_state.rb --write` 修复控制面；不要读取已废弃的 `.planning/pipeline-state.md` 作为状态来源。
+**降级策略**：`.devflow/planning/STATE.md` 是唯一规范状态源。如果 `inspect_state.rb` 不可用或 STATE 缺少 YAML front matter，报告主流程阻塞并提示运行 `init_workflow.rb --write`、`init_state.rb --write` 修复控制面；不要读取已废弃的 `.devflow/planning/pipeline-state.md` 作为状态来源。
 
 ### 轨道参数传递
 
-`--track A` 或 `--track B` 参数会写入 `.planning/STATE.md` 的 `active_track` 字段。orchestrator 读取该字段后：
+`--track A` 或 `--track B` 参数会写入 `.devflow/planning/STATE.md` 的 `active_track` 字段。orchestrator 读取该字段后：
 
 - **active_track: A** → 只路由 Track A 允许步骤，Track A 完成后以 `track_scope_complete` 阻断，不进入完整交付。
 - **active_track: B** → 新需求从完整需求主链开始；前端设计步骤依赖 `api-contract` 完成。Track B 完成后以 `track_scope_complete` 阻断。

package/plugins/devflow-core/skills/workflow-pipeline/references/pipeline-flow.md

@@ -1,154 +1,82 @@
 # 研发交付全链路流程
 
+`feature-development.yaml` 是步骤拓扑、checkpoint 和失败分支的规范来源。本文档只做人类可读投影；两者不一致时，以 workflow YAML 及 `.devflow/planning/STATE.md` 为准。
+
+## 规范链路
+
+```text
+workflow-pipeline
+  → devflow_state(action="inspect")
+  → 缺少项目上下文时执行 workflow-project-context
+  → requirement-triage
+  → requirement-wayfinder
+  → domain-modeling
+  → requirement-feasibility-review
+  → requirement-baseline
+  → CP-1：需求基线确认
+  → wireframe-proposal
+  → wireframe-validate
+  → wireframe-render
+  → wireframe-review
+  → CP-WIREFRAME：线框确认
+  → api-contract
+  → CP-API：API 契约确认
+  → architecture-feasibility
+  → 双轨设计
+      ├─ Track A: backend-tech-spec → api-call-guide
+      └─ Track B: ui-spec → feature-breakdown → frontend-tech-spec → api-supplement
+  → integration-verify
+  → CP-2：双轨合并方案确认
+  → acceptance-test-design（编码前产生候选 TC-*）
+  → change-plan（任务绑定候选 TC-*）
+  → CP-3：确认变更计划并冻结验收套件
+  → phase-structure
+  → execute（代码与 TDD 证据）
+  → code-index-refresh
+  → code-review
+  → human-acceptance（人工 TC、问题反馈和开发者同步）
+  → run-acceptance-tests（执行冻结 TC-*）
+  → CP-4：验收结果确认
+  → release-closeout
+  → 完成
 ```
-workflow-pipeline 启动
-         │
-         ▼
-┌─────────────────────────────────────┐
-│ Step 0: 断点检测                     │
-│ 读取 STATE.md + inspector 恢复进度   │
-└─────────────────────────────────────┘
-         │
-         ▼
-┌─────────────────────────────────────┐
-│ Step 1: 项目初始化                   │
-│ workflow-project-context                     │
-│ 输出: .planning/PROJECT.md          │
-└─────────────────────────────────────┘
-         │
-         ▼
-┌─────────────────────────────────────┐
-│ Step 2: 需求完善                     │
-│ workflow-requirement-baseline                 │
-│ 输出: .planning/requirements/baseline.md │
-│ 门禁: 冲突/复用/过度工程/替代方案已拍板 │
-└──────────────┬──────────────────────┘
-         │             ↑
-         ▼             │ 用户拒绝
-┌─────────────────────────────────────┐
-│ 🔴 CP-1: 需求基线人工确认             │
-│ ask 强制暂停              │
-│ 确认: FP/BR/BC 准确完整              │
-└──────────────┬──────────────────────┘
-         │ 用户确认
-         ▼
-┌─────────────────────────────────────┐
-│ Step 3: 三文档并行生成                │
-│                                    │
-│  ┌──────────┐ ┌──────────┐ ┌──────┐ │
-│  │ feature- │ │frontend- │ │back- │ │
-│  │breakdown │ │tech-spec │ │end-  │ │
-│  │          │ │          │ │tech- │ │
-│  │ 功能点   │ │ 前端方案 │ │spec  │ │
-│  │ 梳理.md  │ │ .md      │ │后端  │ │
-│  └──────────┘ └──────────┘ └──────┘ │
-└─────────────────────────────────────┘
-         │             ↑
-         ▼             │ 用户拒绝
-┌─────────────────────────────────────┐
-│ 🟡 CP-2: 技术方案人工确认             │
-│ ask 强制暂停              │
-│ --no-review 可跳过                    │
-│ 确认: DB/API/架构决策合理可行         │
-└──────────────┬──────────────────────┘
-         │ 用户确认
-         ▼
-┌─────────────────────────────────────┐
-│ Step 4: 变更清单                     │
-│ workflow-change-plan                         │
-│ 输入: 前端+后端技术方案               │
-│ 输出: .planning/features/{功能名}/变更清单.md │
-└──────────────┬──────────────────────┘
-         │             ↑
-         ▼             │ 用户拒绝
-┌─────────────────────────────────────┐
-│ 🔴 CP-3: 变更清单人工确认             │
-│ ask 强制暂停              │
-│ 不可跳过                              │
-│ 确认: DDL/代码/上线步骤可执行         │
-└──────────────┬──────────────────────┘
-         │ 用户确认
-         ▼
-┌─────────────────────────────────────┐
-│ Step 4.5: Phase 结构初始化           │
-│ phase-init                           │
-│ 创建 ROADMAP.md + .planning/phases/  │
-│ 桥接 workflow 产物到 phase 结构      │
-└─────────────────────────────────────┘
-         │
-         ▼
-┌─────────────────────────────────────┐
-│ Step 5: 代码执行                     │
-│ workflow-execute-phase                   │
-│ Wave1: DDL → Wave2: Domain/Service  │
-│ Wave3: API → Wave4: 前端 → Wave5: 联调│
-│ 输出: SUMMARY.md 写入 phases/ 目录   │
-└──────────────┬──────────────────────┘
-	         │             ↑
-	         ▼             │ 修复后重试
-┌─────────────────────────────────────┐
-│ Step 5.5: 代码索引刷新               │
-│ workflow-code-index                  │
-│ 刷新 Symbol/Relation/Call Graph      │
-│ 输出 .planning/code-index/ + AUDIT   │
-└──────────────┬──────────────────────┘
-	         │             ↑
-	         ▼             │ 索引审查失败
-┌─────────────────────────────────────┐
-│ Step 5.6: 代码审查 + 主流程用例      │
-│ code-review + generate-mainflow-cases│
-│ 基于 code-index + 源码 evidence       │
-└──────────────┬──────────────────────┘
-	         │             ↑
-	         ▼             │ 审查失败/用例生成失败
-┌─────────────────────────────────────┐
-│ Step 6: 需求验收测试执行              │
-│ workflow-run-acceptance-tests         │
-│ 执行冻结的 TC-*                       │
-│ 失败/阻塞 → 修复 → 重跑                │
-└──────────────┬──────────────────────┘
-	         │             ↑
-	         ▼             │ 用户拒绝
-┌─────────────────────────────────────┐
-│ 🔴 CP-4: 验收结果确认                 │
-│ ask 强制暂停              │
-│ 不可跳过                              │
-│ 确认: TC-* 全部通过,允许版本收口       │
-└──────────────┬──────────────────────┘
-         │ 用户确认
-         ▼
-┌─────────────────────────────────────┐
-│ Step 7: 版本收口与里程碑归档          │
-│ workflow-release-closeout             │
-│ 校验 TC/code-index → 归档 → 更新状态   │
-└─────────────────────────────────────┘
-         │
-         ▼
-           完成 ✓
+
+`workflow-generate-mainflow-cases` 不参与独立排序，而是 `run-acceptance-tests` 绑定阶段的组成部分：automated 的 ui / api_flow TC 需要先生成 v1 DSL 并批准执行计划。人工验收结果（经 `human_result` 批准）会与自动执行结果聚合，验收失败是硬门禁。
+
+## 双轨与 Checkpoint 规则
+
+- 双轨设计支持时最多并行两个步骤；不支持时按 workflow 声明顺序串行降级。
+- `CP-1`、`CP-WIREFRAME`、`CP-API`、`CP-2`、`CP-3` 和 `CP-4` 都会暂停链路，等待用户审查当前产物。
+- `--no-review` 仅保留参数位，不会跳过 `CP-2`；`integration-verify` Merge Gate 不可跳过。
+- 用户拒绝或提出修改意见时，流程保持在当前步骤，不会自动推进。
+- 单轨 `--track A` / `--track B` 只产出对应轨道文档，不会越过 `integration-verify` 进入完整实施。
+
+## 失败分支
+
+`run-acceptance-tests` 失败、阻塞或验收结果被拒绝时，进入 `acceptance-failed-remediation`：
+
+```text
+验收失败 → 诊断/修复 → 刷新代码索引 → 重跑原冻结 TC-* → CP-4
 ```
 
 ## 断点续接
 
-每次启动时，workflow-pipeline 通过 `devflow_state(action="inspect")` 读取规范状态文件 `.planning/STATE.md`，由 inspector 返回当前动作和下一节点：
+Pipeline 通过 `devflow_state(action="inspect")` 读取 `.devflow/planning/STATE.md`，并根据 inspector 返回的 `action` 路由到下一步、当前步骤、checkpoint、失败分支或并行窗口。
 
-```
-1. 校验 `.planning/STATE.md` 的 YAML front matter、workflow 配置和 artifact registry
-2. 根据 inspector 返回的 `action` 路由到下一步、当前步骤、确认、失败分支或并行窗口
-3. 如果控制面缺失或校验失败，报告阻塞并提示运行 `init_workflow.rb --write`、`init_state.rb --write` 修复
-4. `.planning/pipeline-state.md` 已废弃，不作为恢复状态来源
-```
+1. 校验 `STATE.md` 的 YAML front matter、workflow 配置和 artifact registry。
+2. 如果控制面缺失或校验失败，报告阻塞并通过专用 Core 恢复链路处理。
+3. `.devflow/planning/pipeline-state.md` 已废弃，不作为恢复状态来源。
 
-## 简化流程门禁
+## 需求基线门禁
 
-只有单文件/单方法/单文档、无跨层影响、无未拍板需求决策时，才允许向用户提议简化流程。用户未明确同意时，继续完整 pipeline。
+`requirement-baseline` 完成后必须检查：
 
-## 需求拍板门禁
+- `.devflow/planning/requirements/baseline.md` 中的待确认事项、反向审视与下游输入契约。
+- `.devflow/planning/requirements/baseline.meta.json` 的 `review_status` 必须为 `passed`。
+- `blocking_pending_count`、`critical_image_missing_count`、`challenge_pending_count` 和 `code_reality_missing_count` 必须全为 `0`。
 
-Step 2 之后必须检查 `.planning/requirements/baseline.md`：
+影响 scope、语义、归属、兼容性或实现成本的未确认项是阻塞项，不得将其当作已确认范围传入技术方案或变更清单。
 
-- `待确认事项`
-- `反向审视与用户拍板`
-- `下游输入契约`
-- `.planning/requirements/baseline.meta.json` 中 `review_status` 必须为 `passed`，且 `blocking_pending_count`、`critical_image_missing_count`、`challenge_pending_count`、`code_reality_missing_count` 必须全为 0
+## 简化流程
 
-影响 scope、语义、归属、兼容性或实现成本的未确认项是阻塞项。不能把它们传入技术方案或变更清单当成已确认范围。
+只有单文件、单方法或单文档变更，且无跨层影响、无未拍板需求决策时，才能向用户提议简化流程。用户未明确同意时，继续完整 Pipeline。

package/plugins/devflow-core/skills/workflow-project-context/SKILL.md

@@ -13,7 +13,7 @@ This skill is the project-context interface wrapper. Prefer using it from a dele
 
 The control database under the product data directory is the only machine authority for initialization. `.devflow/project.json` locates project identity. Workspaces, scan configurations, input snapshots, runs, facts, evidence, index references, current pointers, document jobs, and authority revisions are stored through `devflow_project_context`.
 
-Never determine current initialization state from Markdown, file mtimes, or duplicated run markers. Never write `.planning/STATE.md`, execution contracts, workflow artifacts, requirements, approvals, or user instruction files.
+Never determine current initialization state from Markdown, file mtimes, or duplicated run markers. Never write `.devflow/planning/STATE.md`, execution contracts, workflow artifacts, requirements, approvals, or user instruction files.
 
 Human-readable files are projections. Existing unmanaged files are preserved; the generator writes a `.devflow-pending` sibling when it cannot prove that the current file is its previous output.
 
@@ -22,12 +22,12 @@ Human-readable files are projections. Existing unmanaged files are preserved; th
 Before choosing a tool action, inspect the generated external contract when it exists:
 
 ```text
-.planning/interface-index.json
-.planning/knowledge-index.json
-.context/knowledge/interfaces/
+.devflow/planning/interface-index.json
+.devflow/planning/knowledge-index.json
+.devflow/context/knowledge/interfaces/
 ```
 
-`.planning/interface-index.json` is the machine-readable contract for external AI/tool callers. It lists callable interfaces, actions, request shapes, response shapes, read/write boundaries, and approval tier. `.context/knowledge/interfaces/` is the human-readable projection of the same contract. `.planning/knowledge-index.json` connects interface nodes, source documents, knowledge pages, code facts, and reserved BUG/FIX/INCIDENT/LESSON nodes.
+`.devflow/planning/interface-index.json` is the machine-readable contract for external AI/tool callers. It lists callable interfaces, actions, request shapes, response shapes, read/write boundaries, and approval tier. `.devflow/context/knowledge/interfaces/` is the human-readable projection of the same contract. `.devflow/planning/knowledge-index.json` connects interface nodes, source documents, knowledge pages, code facts, and reserved BUG/FIX/INCIDENT/LESSON nodes.
 
 If the contract files do not exist yet, use the rules in this skill to run initialization and then report that the interface contract was created. If they exist, do not invent action shapes from memory; follow the contract unless it conflicts with this skill's safety rules.
 
@@ -44,10 +44,10 @@ Use a delegated sub-agent for non-trivial project-context work:
 
 The delegated sub-agent must:
 
-1. read `.planning/interface-index.json` when available;
+1. read `.devflow/planning/interface-index.json` when available;
 2. choose the narrowest safe action;
 3. call `devflow_project_context` or `devflow_skill_script` only through the documented action shape;
-4. read `.planning/knowledge-index.json` and `.planning/code-index/` only when needed for evidence;
+4. read `.devflow/planning/knowledge-index.json` and `.devflow/planning/code-index/` only when needed for evidence;
 5. return a result pack to the parent agent.
 
 The parent agent should not directly compose multi-step initialization calls unless the task is a simple status read or the delegated agent path is unavailable.
@@ -59,7 +59,7 @@ The parent agent should not directly compose multi-step initialization calls unl
 | `initialize-project` | `workspaces` → `config` → `scan` → `project-context-db-validate` | Full mode by default; static only; no workflow state mutation. |
 | `query-facts` | `query` | Requires a fixed `snapshotId`; follow pagination. |
 | `query-api` | `query(kind="api")` plus code-index readback when implementation detail is needed | Do not scan just to answer from an existing fresh snapshot. |
-| `query-knowledge` | read `knowledge-index.json` and relevant `.context/knowledge/*` | Use `query` only for machine facts. |
+| `query-knowledge` | read `knowledge-index.json` and relevant `.devflow/context/knowledge/*` | Use `query` only for machine facts. |
 | `query-bug-knowledge` | read reserved/actual BUG/FIX/INCIDENT/LESSON nodes, then query/diff if code facts are needed | Do not invent BUG records. |
 | `refresh-after-code-change` | `scan` → optional `diff` | Use a new request ID. Compare old and new snapshots when impact is requested. |
 | `refresh-after-bug-fix` | verify BUG/FIX/LESSON docs if present → `scan` → optional `diff` | `scan` refreshes facts; it does not fix the bug. |
@@ -85,7 +85,7 @@ Every delegated project-context result must return this structure in prose or JS
 - snapshotId
 - codeIndexGeneration
 - sourceSnapshot
-- interfaceContract: .planning/interface-index.json if used
+- interfaceContract: .devflow/planning/interface-index.json if used
 
 ## Evidence
 - facts, knowledge pages, code facts, document paths, or diagnostics used
@@ -129,10 +129,10 @@ Do not infer move/copy identity from timestamps or similar directory names.
 
 ## Legacy input
 
-Legacy `.planning` or `.context` files are never read as current machine facts. On an explicit import request, register selected files as historical material in shadow mode:
+Legacy `.devflow/planning` or `.devflow/context` files are never read as current machine facts. On an explicit import request, register selected files as historical material in shadow mode:
 
 ```text
-devflow_project_context(action="import-legacy", sources=[".planning/PROJECT.md"], requestId="<stable-request-id>")
+devflow_project_context(action="import-legacy", sources=[".devflow/planning/PROJECT.md"], requestId="<stable-request-id>")
 ```
 
 Imported prose remains `historical`, `observed=false`, and `approved=false`. Do not import requirements or design approval merely because text looks final.
@@ -161,11 +161,11 @@ The scan freezes the complete file manifest, including uncommitted and untracked
 
 Python uses AST scopes. TypeScript, JavaScript, and Ruby use conservative structured scopes with declared inference limits. Other languages use file-level generic extraction. Declarations are not calls. Receiver or dynamic calls stay unresolved unless a supported resolver proves a target. Name uniqueness alone is at most an inference and generic text never becomes an exact method edge.
 
-Every full scan publishes an immutable generation under `.planning/code-index/snapshots/<generation>/`; root index files are compatibility projections. Current queries reject stale committed, modified, deleted, or newly added input. Historical queries name a generation. Relation traversal is cycle-safe and exposes depth, result limits, uncertainty, and truncation.
+Every full scan publishes an immutable generation under `.devflow/planning/code-index/snapshots/<generation>/`; root index files are compatibility projections. Current queries reject stale committed, modified, deleted, or newly added input. Historical queries name a generation. Relation traversal is cycle-safe and exposes depth, result limits, uncertainty, and truncation.
 
 ## Human-readable documents
 
-Program-owned projections are `.planning/PROJECT.md`, `.planning/toolchain.md`, `.planning/navigation/INDEX.md`, `.planning/navigation/{codebase}.md`, `.planning/rules/INDEX.md`, and `.planning/initialization/report.md`.
+Program-owned projections are `.devflow/planning/PROJECT.md`, `.devflow/planning/toolchain.md`, `.devflow/planning/navigation/INDEX.md`, `.devflow/planning/navigation/{codebase}.md`, `.devflow/planning/rules/INDEX.md`, and `.devflow/planning/initialization/report.md`.
 
 Template mode is an explicit no-model fallback. A configured low-tier organizer may improve prose, but the program owns exact paths, commands, counts, tables, unknowns, and completion status. Model output containing internal identifiers, database structure, hashes, code blocks, or unsupported machine detail is rejected. Document failure never invalidates an already published data snapshot; retry `generate-docs` for that snapshot.
 
@@ -209,7 +209,7 @@ Run the database validator with identifiers returned by the scan:
 devflow_skill_script(script="project-context-db-validate", args=["--database", "<control.db>", "--project-id", "<project-id>", "--workspace-id", "<workspace-id>", "--run-id", "<run-id>"])
 ```
 
-The `--database` value must come from `devflow_project_context(action="scan").database` or the loaded project context `controlDatabasePath`. Never guess `./control.db`, `.devflow/control.db`, `.planning/code-index/index.sqlite`, an OMP agent database, or any SQLite found by searching user directories. Code-index SQLite is not the initialization control database and does not contain the initialization `schema_meta` table.
+The `--database` value must come from `devflow_project_context(action="scan").database` or the loaded project context `controlDatabasePath`. Never guess `./control.db`, `.devflow/control.db`, `.devflow/planning/code-index/index.sqlite`, an OMP agent database, or any SQLite found by searching user directories. Code-index SQLite is not the initialization control database and does not contain the initialization `schema_meta` table.
 
 Completion requires a stable immutable input, matching context snapshot, accounted required categories, evidence for observed facts, a registered immutable index in full mode, revision-safe pointer publication, and separate document statuses. Workflow `STATE` and other non-initialization authorities must remain unchanged.
 

package/plugins/devflow-core/skills/workflow-project-context/assets/agents-md-template.md

@@ -4,11 +4,11 @@
 
 Before any operation, read these files in order:
 
-1. `.planning/rules/INDEX.md` — project rule index (gate entry point)
-2. `.context/spec/index.md` — design and codebase specification entry
+1. `.devflow/planning/rules/INDEX.md` — project rule index (gate entry point)
+2. `.devflow/context/spec/index.md` — design and codebase specification entry
 {{#if codebase_count}}
-3. `.planning/navigation/INDEX.md` — codebase registry and navigation files
-4. `.planning/code-index/` — machine code facts generated by `workflow-code-index` during full initialization unless fast mode skipped it
+3. `.devflow/planning/navigation/INDEX.md` — codebase registry and navigation files
+4. `.devflow/planning/code-index/` — machine code facts generated by `workflow-code-index` during full initialization unless fast mode skipped it
 {{/if}}
 
 ## Codebases
@@ -20,6 +20,6 @@ This project has {{codebase_count}} codebase(s):
 
 ## Key Directories
 
-- `.planning/` — workflow state, navigation, rules, execution contract
-- `.context/spec/` — design and codebase specifications (MUST/SHOULD/OBSERVED rules)
-- `.context/lessons/` — accumulated project experience and regression prevention
+- `.devflow/planning/` — workflow state, navigation, rules, execution contract
+- `.devflow/context/spec/` — design and codebase specifications (MUST/SHOULD/OBSERVED rules)
+- `.devflow/context/lessons/` — accumulated project experience and regression prevention

package/plugins/devflow-core/skills/workflow-project-context/assets/codebase-backend-spec-template.md

@@ -1,13 +1,13 @@
 # {{name}} Backend Codebase Specification
 
-This file describes project-instance rules for one backend/service codebase. Stack-level defaults are in `.context/spec/stacks/{{stack_key}}.md`.
+This file describes project-instance rules for one backend/service codebase. Stack-level defaults are in `.devflow/context/spec/stacks/{{stack_key}}.md`.
 
 ## Version
 
 - Generated at: {{generated_at}}
 - Codebase: `{{name}}`
-- Navigation: `.planning/navigation/{{name}}.md`
-- Stack spec: `.context/spec/stacks/{{stack_key}}.md`
+- Navigation: `.devflow/planning/navigation/{{name}}.md`
+- Stack spec: `.devflow/context/spec/stacks/{{stack_key}}.md`
 - Source manifests: {{manifest_sources}}
 - Dependency fingerprint: {{dependency_fingerprint}}
 - Regenerate when:
@@ -53,7 +53,7 @@ This file describes project-instance rules for one backend/service codebase. Sta
 
 ## Explicit Rules
 
-Rules from `AGENTS.md`, `CLAUDE.md`, `.cursorrules`, existing `.context/spec/`, or equivalent files.
+Rules from `AGENTS.md`, `CLAUDE.md`, `.cursorrules`, existing `.devflow/context/spec/`, or equivalent files.
 
 - {{explicit_rule}}
 

package/plugins/devflow-core/skills/workflow-project-context/assets/codebase-frontend-spec-template.md

@@ -1,13 +1,13 @@
 # {{name}} Frontend Codebase Specification
 
-This file describes project-instance rules for one frontend codebase. Stack-level defaults are in `.context/spec/stacks/{{stack_key}}.md`.
+This file describes project-instance rules for one frontend codebase. Stack-level defaults are in `.devflow/context/spec/stacks/{{stack_key}}.md`.
 
 ## Version
 
 - Generated at: {{generated_at}}
 - Codebase: `{{name}}`
-- Navigation: `.planning/navigation/{{name}}.md`
-- Stack spec: `.context/spec/stacks/{{stack_key}}.md`
+- Navigation: `.devflow/planning/navigation/{{name}}.md`
+- Stack spec: `.devflow/context/spec/stacks/{{stack_key}}.md`
 - Source manifests: {{manifest_sources}}
 - Dependency fingerprint: {{dependency_fingerprint}}
 - Regenerate when:
@@ -49,7 +49,7 @@ This file describes project-instance rules for one frontend codebase. Stack-leve
 
 ## Explicit Rules
 
-Rules from `AGENTS.md`, `CLAUDE.md`, `.cursorrules`, existing `.context/spec/`, or equivalent files.
+Rules from `AGENTS.md`, `CLAUDE.md`, `.cursorrules`, existing `.devflow/context/spec/`, or equivalent files.
 
 - {{explicit_rule}}
 

package/plugins/devflow-core/skills/workflow-project-context/assets/codebase-navigation-template.md

@@ -147,7 +147,7 @@ Convention categories: Component hierarchy, Data flow (composable/store), Route
 
 ## Rule Sources
 
-See `.planning/rules/INDEX.md` for the full project rule index. This codebase's relevant rule files:
+See `.devflow/planning/rules/INDEX.md` for the full project rule index. This codebase's relevant rule files:
 
 | Rule | Path | Status |
 |------|------|--------|

package/plugins/devflow-core/skills/workflow-project-context/assets/context-domain-index-template.md

@@ -16,13 +16,13 @@ Generated during project initialization.
 
 ## Read Order
 
-1. `.planning/rules/INDEX.md`
-2. `.context/spec/index.md`
+1. `.devflow/planning/rules/INDEX.md`
+2. `.devflow/context/spec/index.md`
 3. Matching stack spec
 4. Matching codebase spec
 5. Applicable depth specs from the registry below
 6. Matching navigation file
-7. `.planning/code-index/` machine symbols/relations for source-level relation facts; if fast mode skipped generation, refresh through `workflow-code-index` or record fallback
+7. `.devflow/planning/code-index/` machine symbols/relations for source-level relation facts; if fast mode skipped generation, refresh through `workflow-code-index` or record fallback
 8. Actual source files selected from navigation/spec/code-index evidence
 
 ## Depth Spec Registry
@@ -36,7 +36,7 @@ Generated during project initialization.
 ## Pending Templates
 
 Record discovered topics whose matching depth spec template is missing as `PENDING_TEMPLATE`.
-Mirror the same blocker in `.planning/STATE.md` front matter.
+Mirror the same blocker in `.devflow/planning/STATE.md` front matter.
 
 ## Pending Confirmation
 

package/plugins/devflow-core/skills/workflow-project-context/assets/context-spec-index-template.md

@@ -11,19 +11,19 @@ Generated during project initialization. This file is a registry and read-order
 
 Downstream skills must read rule sources in this order:
 
-1. `.planning/rules/INDEX.md`
-2. `.context/spec/index.md`
-3. Matching `.context/spec/stacks/{stack_key}.md`
-4. Matching `.context/spec/frontend|backend/{codebase}.md`
-5. Matching `.context/spec/{domain}/index.md` and applicable depth specs
-6. `.planning/navigation/{codebase}.md`
-7. `.planning/code-index/` machine symbols/relations for source-level relation facts; if fast mode skipped generation, refresh through `workflow-code-index` or record fallback
+1. `.devflow/planning/rules/INDEX.md`
+2. `.devflow/context/spec/index.md`
+3. Matching `.devflow/context/spec/stacks/{stack_key}.md`
+4. Matching `.devflow/context/spec/frontend|backend/{codebase}.md`
+5. Matching `.devflow/context/spec/{domain}/index.md` and applicable depth specs
+6. `.devflow/planning/navigation/{codebase}.md`
+7. `.devflow/planning/code-index/` machine symbols/relations for source-level relation facts; if fast mode skipped generation, refresh through `workflow-code-index` or record fallback
 8. Actual source files
 
 Priority when rules conflict:
 
 1. User-explicit requirement
-2. Explicit project rules (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`, existing `.context/spec/`)
+2. Explicit project rules (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`, existing `.devflow/context/spec/`)
 3. Codebase spec
 4. Stack spec
 5. Code-inferred convention
@@ -32,13 +32,13 @@ Priority when rules conflict:
 
 | Stack Key | Spec | Codebases | Manifest Sources | Fingerprint |
 |-----------|------|-----------|------------------|-------------|
-| {{stack_key}} | `.context/spec/stacks/{{stack_key}}.md` | {{codebases}} | {{manifest_sources}} | {{fingerprint}} |
+| {{stack_key}} | `.devflow/context/spec/stacks/{{stack_key}}.md` | {{codebases}} | {{manifest_sources}} | {{fingerprint}} |
 
 ## Codebase Specs
 
 | Codebase | Type | Navigation | Stack Key | Spec |
 |----------|------|------------|-----------|------|
-| {{name}} | {{type}} | `.planning/navigation/{{name}}.md` | {{stack_key}} | `.context/spec/{{domain}}/{{name}}.md` |
+| {{name}} | {{type}} | `.devflow/planning/navigation/{{name}}.md` | {{stack_key}} | `.devflow/context/spec/{{domain}}/{{name}}.md` |
 
 ## Missing Or Pending
 

package/plugins/devflow-core/skills/workflow-project-context/assets/execution-contract-template.md

@@ -2,7 +2,7 @@
 
 ## Layer Model
 
-Each codebase has its own layer conventions documented in `.planning/navigation/{name}.md`. This section consolidates the layer rules that downstream skills must follow.
+Each codebase has its own layer conventions documented in `.devflow/planning/navigation/{name}.md`. This section consolidates the layer rules that downstream skills must follow.
 
 {{#backend_codebases}}
 ### {{name}} ({{role}})
@@ -47,7 +47,7 @@ Tests can be written before code (TDD) or incrementally within the same task, bu
 
 All code tasks must pass three gates before marking complete:
 1. **Test gate**: task-level tests must be added/updated and pass (or skip classified as acceptable/needs-review).
-2. **Spec Compliance gate**: every MUST rule from the relevant `.context/spec/` depth spec file must be satisfied or explicitly waived.
+2. **Spec Compliance gate**: every MUST rule from the relevant `.devflow/context/spec/` depth spec file must be satisfied or explicitly waived.
 3. **Verification Iron Law**: before claiming completion: IDENTIFY the verification command → RUN it → READ the output → VERIFY against expected results → ONLY THEN mark complete.
 
 For task-level test strategy requirements, see `workflow-execute-phase` "验证铁律" and `workflow-change-plan` "测试策略强制规则" and "跳过自动化测试分级".

package/plugins/devflow-core/skills/workflow-project-context/assets/navigation-index-template.md

@@ -7,34 +7,34 @@
 | Name | Path | Type | Role | Navigation | Scan Status |
 |------|------|------|------|------------|-------------|
 {{#codebases}}
-| {{name}} | {{path}} | {{type}} | {{role}} | `.planning/navigation/{{name}}.md` | {{scan_status}} |
+| {{name}} | {{path}} | {{type}} | {{role}} | `.devflow/planning/navigation/{{name}}.md` | {{scan_status}} |
 {{/codebases}}
 
 ## Project Rule Package
 
-The project rule index is at `.planning/rules/INDEX.md`. Downstream skills should read it first, then use `.context/spec/index.md` to resolve stack/codebase specs and each domain index to resolve applicable depth specs before using codebase navigation files for coarse routing. Use `.planning/code-index/` before reading actual source evidence when source-level relation facts are needed; if fast mode skipped index generation, refresh it through `workflow-code-index` first or record the fallback.
+The project rule index is at `.devflow/planning/rules/INDEX.md`. Downstream skills should read it first, then use `.devflow/context/spec/index.md` to resolve stack/codebase specs and each domain index to resolve applicable depth specs before using codebase navigation files for coarse routing. Use `.devflow/planning/code-index/` before reading actual source evidence when source-level relation facts are needed; if fast mode skipped index generation, refresh it through `workflow-code-index` first or record the fallback.
 
 | Rule Source | Path | Status |
 |-------------|------|--------|
-| Rules Index | `.planning/rules/INDEX.md` | {{rules_index_status}} |
-| Execution Contract | `.planning/execution-contract.md` | {{execution_contract_status}} |
-| Toolchain Contract | `.planning/toolchain.md` | {{toolchain_status}} |
-| Planning Lessons | `.planning/lessons/README.md` | {{lessons_status}} |
-| Context Spec Index | `.context/spec/index.md` | {{context_spec_index_status}} |
-| Stack Specs | `.context/spec/stacks/` | {{stack_specs_status}} |
-| Context Specs | `.context/spec/` | {{context_spec_status}} |
-| Code Index | `.planning/code-index/` | {{code_index_status}} |
-| Design Rule Pack | `.context/spec/design/` | {{design_rule_pack_status}} |
-| Context Workflow | `.context/workflow/` | {{context_workflow_status}} |
-| Context Lessons | `.context/lessons/README.md` | {{context_lessons_status}} |
+| Rules Index | `.devflow/planning/rules/INDEX.md` | {{rules_index_status}} |
+| Execution Contract | `.devflow/planning/execution-contract.md` | {{execution_contract_status}} |
+| Toolchain Contract | `.devflow/planning/toolchain.md` | {{toolchain_status}} |
+| Planning Lessons | `.devflow/planning/lessons/README.md` | {{lessons_status}} |
+| Context Spec Index | `.devflow/context/spec/index.md` | {{context_spec_index_status}} |
+| Stack Specs | `.devflow/context/spec/stacks/` | {{stack_specs_status}} |
+| Context Specs | `.devflow/context/spec/` | {{context_spec_status}} |
+| Code Index | `.devflow/planning/code-index/` | {{code_index_status}} |
+| Design Rule Pack | `.devflow/context/spec/design/` | {{design_rule_pack_status}} |
+| Context Workflow | `.devflow/context/workflow/` | {{context_workflow_status}} |
+| Context Lessons | `.devflow/context/lessons/README.md` | {{context_lessons_status}} |
 | Root Instructions | `AGENTS.md` / `CLAUDE.md` | {{root_instructions_status}} |
 
 ## Downstream Read Contract
 
 | Skill | Should Read |
 |-------|-------------|
-| `workflow-requirement-baseline` | `.planning/PROJECT.md`, this INDEX.md, relevant codebase navigation files, and `.planning/code-index/` for source-level relation checks |
-| `workflow-feature-breakdown` | `.planning/PROJECT.md`, this INDEX.md, and codebase navigation files for codebases relevant to the feature |
-| `workflow-frontend-tech-spec` | `.planning/rules/INDEX.md` → `.context/spec/index.md` → matching stack spec → matching frontend codebase spec → frontend domain index/applicable depth specs → this INDEX.md/navigation → code-index → source evidence |
-| `workflow-backend-tech-spec` | `.planning/rules/INDEX.md` → `.context/spec/index.md` → matching stack spec → matching backend codebase spec → backend domain index/applicable depth specs → this INDEX.md/navigation → code-index → source evidence |
-| `workflow-change-plan` | `.planning/rules/INDEX.md` + `.context/spec/index.md` for task gates, this INDEX.md for output locations and source navigation |
+| `workflow-requirement-baseline` | `.devflow/planning/PROJECT.md`, this INDEX.md, relevant codebase navigation files, and `.devflow/planning/code-index/` for source-level relation checks |
+| `workflow-feature-breakdown` | `.devflow/planning/PROJECT.md`, this INDEX.md, and codebase navigation files for codebases relevant to the feature |
+| `workflow-frontend-tech-spec` | `.devflow/planning/rules/INDEX.md` → `.devflow/context/spec/index.md` → matching stack spec → matching frontend codebase spec → frontend domain index/applicable depth specs → this INDEX.md/navigation → code-index → source evidence |
+| `workflow-backend-tech-spec` | `.devflow/planning/rules/INDEX.md` → `.devflow/context/spec/index.md` → matching stack spec → matching backend codebase spec → backend domain index/applicable depth specs → this INDEX.md/navigation → code-index → source evidence |
+| `workflow-change-plan` | `.devflow/planning/rules/INDEX.md` + `.devflow/context/spec/index.md` for task gates, this INDEX.md for output locations and source navigation |