@guanlin4924/devflow-pi 0.1.93 → 0.1.94

package/plugins/devflow-intel/skills/workflow-code-index/scripts/code_index.py

@@ -150,7 +150,7 @@ def _worktree_signature(root: Path) -> str:
     kept = []
     for line in proc.stdout.splitlines():
         path = line[3:].strip() if len(line) > 3 else ""
-        if path.startswith(".planning/code-index/"):
+        if path.startswith(".devflow/planning/code-index/"):
             continue
         kept.append(line)
     return "\n".join(kept)
@@ -198,7 +198,7 @@ def main(argv=None) -> int:
 
     scan = sub.add_parser("scan", help="Build or refresh the code index.")
     scan.add_argument("--root", default=".", help="Project root. Defaults to current directory.")
-    scan.add_argument("--output", default=".planning/code-index", help="Index output directory.")
+    scan.add_argument("--output", default=".devflow/planning/code-index", help="Index output directory.")
     scan.add_argument("--codebase", action="append", default=[], help="Explicit codebase: name:path[:type]. Can repeat.")
     scan.add_argument("--changed-files", nargs="*", default=[], help="Optional changed files for incremental refresh.")
     scan.add_argument("--include", action="append", default=[], help="Repository-relative include glob. Can repeat.")
@@ -206,7 +206,7 @@ def main(argv=None) -> int:
     scan.add_argument("--exclude", action="append", default=[], help="Additional directory names to exclude.")
 
     validate = sub.add_parser("validate", help="Validate an index in staged levels.")
-    validate.add_argument("--index", default=".planning/code-index", help="Index directory.")
+    validate.add_argument("--index", default=".devflow/planning/code-index", help="Index directory.")
     validate.add_argument("--snapshot", help="Immutable generation id.")
     validate.add_argument(
         "--level",
@@ -217,19 +217,19 @@ def main(argv=None) -> int:
 
     audit = sub.add_parser("audit", help="Audit stale files and relation integrity.")
     audit.add_argument("--root", default=".", help="Project root.")
-    audit.add_argument("--index", default=".planning/code-index", help="Index directory.")
+    audit.add_argument("--index", default=".devflow/planning/code-index", help="Index directory.")
     audit.add_argument("--skill-root", default=".skills", help="Optional skill root for project-binding checks.")
     audit.add_argument("--snapshot", help="Immutable generation id.")
     audit.add_argument("--level", choices=("publish", "full"), default="publish")
 
     query = sub.add_parser("query", help="Search symbols using SQLite FTS or LIKE fallback.")
-    query.add_argument("--index", default=".planning/code-index", help="Index directory.")
+    query.add_argument("--index", default=".devflow/planning/code-index", help="Index directory.")
     query.add_argument("--term", required=True, help="Search term.")
     query.add_argument("--limit", type=int, default=20)
     query.add_argument("--snapshot", help="Immutable generation id. Historical queries do not require current workspace freshness.")
 
     relations = sub.add_parser("relations", help="Traverse resolved relations in a fixed snapshot.")
-    relations.add_argument("--index", default=".planning/code-index")
+    relations.add_argument("--index", default=".devflow/planning/code-index")
     relations.add_argument("--object", required=True, help="Source symbol id.")
     relations.add_argument("--depth", type=int, default=3)
     relations.add_argument("--limit", type=int, default=100)
@@ -238,7 +238,7 @@ def main(argv=None) -> int:
     relations.add_argument("--direction", choices=["incoming", "outgoing", "both"], default="outgoing")
 
     impact = sub.add_parser("impact", help="Traverse cross-layer semantic facts in a fixed snapshot.")
-    impact.add_argument("--index", default=".planning/code-index")
+    impact.add_argument("--index", default=".devflow/planning/code-index")
     impact.add_argument("--entity", required=True, help="Logical entity id, feature id, API id, or symbol id.")
     impact.add_argument("--depth", type=int, default=5)
     impact.add_argument("--limit", type=int, default=200)
@@ -247,7 +247,7 @@ def main(argv=None) -> int:
 
     for action in ("search-content", "resolve-domain", "query-plan", "domain-import"):
         operation = sub.add_parser(action)
-        operation.add_argument("--index", default=".planning/code-index")
+        operation.add_argument("--index", default=".devflow/planning/code-index")
         operation.add_argument("--snapshot")
         operation.add_argument("--project-id", default="")
         operation.add_argument("--limit", type=int, default=20)

package/plugins/devflow-intel/skills/workflow-code-index/scripts/core/discovery.py

@@ -45,7 +45,7 @@ def _parse_explicit(root: Path, value: str) -> Optional[Codebase]:
 
 
 def _from_navigation(root: Path) -> List[Codebase]:
-    index = root / ".planning/navigation/INDEX.md"
+    index = root / ".devflow/planning/navigation/INDEX.md"
     if not index.exists():
         return []
     rows = _read_markdown_table(index)
@@ -72,7 +72,7 @@ def _from_navigation(root: Path) -> List[Codebase]:
 
 
 def _from_spec_index(root: Path) -> List[Codebase]:
-    index = root / ".context/spec/index.md"
+    index = root / ".devflow/context/spec/index.md"
     if not index.exists():
         return []
     rows = _read_markdown_table(index)

package/plugins/devflow-intel/skills/workflow-code-index/scripts/core/scanner.py

@@ -7,7 +7,11 @@ from typing import Iterable, List, Sequence
 
 DEFAULT_EXCLUDES = {
     ".git",
+    ".devflow",
+    # Old protocol directories are excluded as source even after the new
+    # namespaced layout becomes authoritative.
     ".planning",
+    ".context",
     "node_modules",
     "vendor",
     "dist",
@@ -139,4 +143,3 @@ def _is_excluded(path: Path, root: Path, excluded: Sequence[str]) -> bool:
     if any(fnmatch.fnmatch(relative, pattern) or fnmatch.fnmatch(relative + "/", pattern.rstrip("/") + "/") for pattern in excluded):
         return True
     return any(part in excluded for part in parts) or any("/" in pattern and ("/" + "/".join(parts) + "/").find("/" + pattern.strip("/") + "/") >= 0 for pattern in excluded)
-

package/plugins/devflow-intel/skills/workflow-code-index/scripts/validators/project_binding_check.py

@@ -5,8 +5,8 @@ from pathlib import Path
 PLACEHOLDER_OK = re.compile(r"\{[A-Za-z0-9_:-]+\}")
 
 GENERIC_TOKENS = (
-    ".planning/",
-    ".context/",
+    ".devflow/planning/",
+    ".devflow/context/",
     ".skills/",
     "references/",
     "scripts/",
@@ -40,8 +40,8 @@ def audit_project_binding(paths):
                 stripped = PLACEHOLDER_OK.sub("", line)
                 if (
                     path_like.search(stripped)
-                    and ".planning/" not in stripped
-                    and ".context/" not in stripped
+                    and ".devflow/planning/" not in stripped
+                    and ".devflow/context/" not in stripped
                     and ".skills/" not in stripped
                 ):
                     findings.append(

package/plugins/devflow-intel/skills/workflow-context-sync/SKILL.md

@@ -28,7 +28,7 @@ code facts changed -> project context must remain trustworthy
 
 Preserve these properties:
 
-- **Freshness**: `.planning/code-index/`, `.planning/navigation/`, and `.context/spec/` must not describe old routes, APIs, entries, services, commands, or codebase roots.
+- **Freshness**: `.devflow/planning/code-index/`, `.devflow/planning/navigation/`, and `.devflow/context/spec/` must not describe old routes, APIs, entries, services, commands, or codebase roots.
 - **Minimality**: do not run a full project initialization when changed-file indexing is enough.
 - **Evidence**: do not update navigation/spec from memory or inference alone; read the changed source or manifest evidence first.
 - **Non-destruction**: do not overwrite user-authored business context; append logs or update machine-derived sections only.
@@ -40,7 +40,7 @@ Preserve these properties:
 |---|---|---|
 | project indexes | Accelerate rule/spec/navigation discovery; fall back to LSP/search/source when stale | Advisory evidence, never a source-read blocker |
 | `workflow-code-index` | Refresh, validate, and audit machine facts | Light, Medium, Full; audit/staleness problems |
-| `workflow-update-navigation` | Update `.planning/navigation/*.md` | Medium route/API/page/service/command changes |
+| `workflow-update-navigation` | Update `.devflow/planning/navigation/*.md` | Medium route/API/page/service/command changes |
 | `workflow-project-context` | Full reinitialization | Full only |
 | `workflow-bug-fix` | Bug-fix main workflow | Must call this skill after verification and lesson capture |
 | `workflow-execute-phase` | Feature implementation workflow | Must call this skill after implementation verification |
@@ -63,9 +63,9 @@ If no flag is provided, default to `--dry-run` and infer changed files from git.
 
 ```text
 workflow-context-sync
-  -> read .planning/rules/INDEX.md
-  -> read .context/spec/index.md
-  -> read .planning/navigation/INDEX.md
+  -> read .devflow/planning/rules/INDEX.md
+  -> read .devflow/context/spec/index.md
+  -> read .devflow/planning/navigation/INDEX.md
   -> collect changed files with per-repo cursor
   -> classify files and affected codebases
   -> choose Light / Medium / Full
@@ -81,7 +81,7 @@ workflow-context-sync
 Maintain pull synchronization state in:
 
 ```text
-.planning/context-sync-state.json
+.devflow/planning/context-sync-state.json
 ```
 
 This file is workflow-owned machine state. It stores one cursor per independently discovered Git repository:
@@ -104,7 +104,7 @@ This file is workflow-owned machine state. It stores one cursor per independentl
 
 Rules:
 
-- Discover repositories from `.planning/navigation/INDEX.md` Codebase Registry, then deduplicate by `git rev-parse --show-toplevel`.
+- Discover repositories from `.devflow/planning/navigation/INDEX.md` Codebase Registry, then deduplicate by `git rev-parse --show-toplevel`.
 - For `--after-pull`, diff `last_synced_head..HEAD` per repo.
 - If a repo has no cursor yet, fall back to `ORIG_HEAD..HEAD` for that repo.
 - If the stored cursor is unavailable or not an ancestor of `HEAD`, use the script-reported fallback/warning and prefer a broader sync level.
@@ -150,7 +150,7 @@ Map paths to codebases:
 | skit-admin | `skit/frontend/admin/**` |
 | skit-h5 | `skit/frontend/h5/**` |
 | skit-backend | `skit/internal/**`, `skit/ioc/**`, `skit/pkg/**`, `skit/backend/migrations/**`, `skit/go.mod`, `skit/Makefile`, `skit/main.go` |
-| project context | `.planning/**`, `.context/spec/**`, `.omp/**`, `AGENTS.md` |
+| project context | `.devflow/planning/**`, `.devflow/context/spec/**`, `.omp/**`, `AGENTS.md` |
 
 Classify impact:
 
@@ -162,7 +162,7 @@ Classify impact:
 | backend boundary | `internal/web/*handler.go`, `ioc/web.go`, `internal/job/**`, public service interfaces | Medium |
 | toolchain/manifest | `package.json`, `go.mod`, `Makefile`, vite/router config | Medium or Full |
 | structure | codebase roots, large directory moves, new top-level/second-level directories | Full |
-| context docs | `.planning/**`, `.context/spec/**` | validate consistency; avoid blind overwrite |
+| context docs | `.devflow/planning/**`, `.devflow/context/spec/**` | validate consistency; avoid blind overwrite |
 
 ## Sync Levels
 
@@ -178,7 +178,7 @@ devflow_code_index(action="validate")
 devflow_code_index(action="audit")
 ```
 
-Then append a concise `.planning/STATE.md` change-log line if this skill modified files.
+Then append a concise `.devflow/planning/STATE.md` change-log line if this skill modified files.
 
 ### Medium
 
@@ -190,10 +190,10 @@ Actions:
 2. Read relevant changed source files.
 3. Read matching navigation/spec entry for each affected codebase.
 4. Update only stale sections, usually:
-   - `.planning/navigation/{codebase}.md`
-   - `.context/spec/frontend|backend/{codebase}.md` only when a codebase rule or stack fact changed
-   - `.planning/toolchain.md` only when commands/manifests changed
-   - `.planning/STATE.md` change log
+   - `.devflow/planning/navigation/{codebase}.md`
+   - `.devflow/context/spec/frontend|backend/{codebase}.md` only when a codebase rule or stack fact changed
+   - `.devflow/planning/toolchain.md` only when commands/manifests changed
+   - `.devflow/planning/STATE.md` change log
 5. Validate and audit code-index again if navigation/spec edits introduce new files or references.
 
 ### Full

package/plugins/devflow-intel/skills/workflow-context-sync/scripts/context_sync_cursor.py

@@ -13,8 +13,8 @@ from pathlib import Path
 from typing import Any
 
 
-DEFAULT_STATE = ".planning/context-sync-state.json"
-NAVIGATION_INDEX = ".planning/navigation/INDEX.md"
+DEFAULT_STATE = ".devflow/planning/context-sync-state.json"
+NAVIGATION_INDEX = ".devflow/planning/navigation/INDEX.md"
 
 
 def run_git(repo: Path, args: list[str], check: bool = True) -> subprocess.CompletedProcess[str]:

package/plugins/devflow-intel/skills/workflow-update-navigation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-update-navigation
-description: "Use when code changes require incremental updates to .planning/navigation files before audit, archive, or future workflow steps."
+description: "Use when code changes require incremental updates to .devflow/planning/navigation files before audit, archive, or future workflow steps."
 ---
 
 ## Legacy Command Metadata
@@ -11,9 +11,9 @@ Original slash-command metadata retained only as workflow invocation guidance.
 user-invocable: true
 pattern: generator+reviewer
 inputs:
-- .planning/features/{功能名}/变更清单.md
-- .planning/navigation/
-output: .planning/navigation/{name}.md (updated)
+- .devflow/planning/features/{功能名}/变更清单.md
+- .devflow/planning/navigation/
+output: .devflow/planning/navigation/{name}.md (updated)
 phase-gate:
   step1: 加载变更清单和当前 navigation
   step2: 识别受影响的代码库和模块
@@ -36,22 +36,22 @@ Incrementally update navigation files after code changes. Do not re-scan the ent
 
 Always update:
 
-- `.planning/navigation/{name}.md` — affected codebase navigation files
-- `.planning/navigation/INDEX.md` — Codebase Registry scan status timestamps
+- `.devflow/planning/navigation/{name}.md` — affected codebase navigation files
+- `.devflow/planning/navigation/INDEX.md` — Codebase Registry scan status timestamps
 
-When `.planning/code-index/` exists or code-index support is part of the project workflow, also refresh and audit the machine index before editing Markdown navigation:
+When `.devflow/planning/code-index/` exists or code-index support is part of the project workflow, also refresh and audit the machine index before editing Markdown navigation:
 
-- `.planning/code-index/files.jsonl`
-- `.planning/code-index/symbols.jsonl`
-- `.planning/code-index/relations.jsonl`
-- `.planning/code-index/diagnostics.jsonl`
-- `.planning/code-index/index.sqlite`
-- `.planning/code-index/AUDIT.md`
+- `.devflow/planning/code-index/files.jsonl`
+- `.devflow/planning/code-index/symbols.jsonl`
+- `.devflow/planning/code-index/relations.jsonl`
+- `.devflow/planning/code-index/diagnostics.jsonl`
+- `.devflow/planning/code-index/index.sqlite`
+- `.devflow/planning/code-index/AUDIT.md`
 
 Do not create by default:
 
 - New navigation files (only update existing ones)
-- New `.planning/` directories
+- New `.devflow/planning/` directories
 
 ## Resource Loading
 
@@ -59,10 +59,10 @@ Do not create by default:
 
 ## Phase 1 — Load Change List And Current Navigation
 
-1. Read `.planning/features/{功能名}/变更清单.md` — extract all code-level changes (new/modified/deleted/renamed files).
-2. Read `.planning/navigation/INDEX.md` — identify which codebases are affected by the changes.
-3. For each affected codebase, read its `.planning/navigation/{name}.md`.
-4. If `.planning/code-index/` exists, collect changed file paths and run an incremental code-index refresh before updating Markdown navigation:
+1. Read `.devflow/planning/features/{功能名}/变更清单.md` — extract all code-level changes (new/modified/deleted/renamed files).
+2. Read `.devflow/planning/navigation/INDEX.md` — identify which codebases are affected by the changes.
+3. For each affected codebase, read its `.devflow/planning/navigation/{name}.md`.
+4. If `.devflow/planning/code-index/` exists, collect changed file paths and run an incremental code-index refresh before updating Markdown navigation:
 
 ```text
 devflow_code_index(action="scan", changedFiles=["<changed-file>", "..."])
@@ -130,7 +130,7 @@ For affected handlers, routes, components, jobs, or integrations identified in P
 
 Use the same call chain tracing method as `workflow-project-context` Step 3b, but limited to changed modules only.
 
-If code-index is available, use `.planning/code-index/relations.jsonl` or `index.sqlite` as the first source for fine-grained call relationships, then read the changed source files to confirm evidence before updating navigation. Navigation remains a human-readable summary; do not copy unverified low-confidence relations into navigation as facts.
+If code-index is available, use `.devflow/planning/code-index/relations.jsonl` or `index.sqlite` as the first source for fine-grained call relationships, then read the changed source files to confirm evidence before updating navigation. Navigation remains a human-readable summary; do not copy unverified low-confidence relations into navigation as facts.
 
 Gate: every changed handler/route/component/job from the change list has its corresponding row updated in the navigation file.
 
@@ -150,7 +150,7 @@ If conventions haven't changed, skip this phase.
 1. For each updated codebase navigation file:
    - Update `Identity → Scan Status` to the current date
    - Add a note: "Updated after 变更清单 execution, {日期}"
-2. Update `.planning/navigation/INDEX.md`:
+2. Update `.devflow/planning/navigation/INDEX.md`:
    - Sync the `Scan Status` column in the Codebase Registry for affected codebases
 3. Run the review checklist:
 
@@ -169,18 +169,18 @@ Fix gaps before reporting completion.
 Run these commands after all navigation edits. Replace `<affected-navigation-file>` with every navigation file selected in Phase 1.
 
 ```bash
-test -s .planning/navigation/INDEX.md
-test -s .planning/navigation/<affected-navigation-file>
-test -s .planning/code-index/AUDIT.md  # when the code index exists
+test -s .devflow/planning/navigation/INDEX.md
+test -s .devflow/planning/navigation/<affected-navigation-file>
+test -s .devflow/planning/code-index/AUDIT.md  # when the code index exists
 ```
 
-When `.planning/code-index/` exists, call `devflow_code_index(action="validate")` and
+When `.devflow/planning/code-index/` exists, call `devflow_code_index(action="validate")` and
 `devflow_code_index(action="audit")` before the shell artifact checks.
 
-The code-index commands are required only when `.planning/code-index/` exists or this workflow refreshed it. Pass only when every selected navigation file and `INDEX.md` is non-empty, `validate` and `audit` exit with code 0, and `AUDIT.md` contains no blocking finding. Also complete every Phase 6 checklist item; commands validate artifact integrity, while the checklist validates change-list coverage. If any check fails, do not advance to audit or archive: correct the navigation/index discrepancy and rerun the failed checks.
+The code-index commands are required only when `.devflow/planning/code-index/` exists or this workflow refreshed it. Pass only when every selected navigation file and `INDEX.md` is non-empty, `validate` and `audit` exit with code 0, and `AUDIT.md` contains no blocking finding. Also complete every Phase 6 checklist item; commands validate artifact integrity, while the checklist validates change-list coverage. If any check fails, do not advance to audit or archive: correct the navigation/index discrepancy and rerun the failed checks.
 
 ## Downstream Read Contract
 
 - `workflow-release-closeout` should verify that navigation `Scan Status` is not older than the last commit before archiving.
 - Future `workflow-requirement-baseline` invocations will read the updated navigation for conflict and reuse detection.
-- Future source-tracing tasks should use `.planning/code-index/` for fine-grained relation facts when available, with source readback before answering.
+- Future source-tracing tasks should use `.devflow/planning/code-index/` for fine-grained relation facts when available, with source readback before answering.

package/plugins/devflow-intel/skills/workflow-update-navigation/references/incremental-update-guide.md

@@ -4,7 +4,7 @@
 
 只重新扫描变更清单中涉及的模块。变更清单外的代码库和模块不做任何扫描或写入。
 
-如果项目存在 `.planning/code-index/`，先按变更文件刷新机器索引，再更新 Markdown navigation：
+如果项目存在 `.devflow/planning/code-index/`，先按变更文件刷新机器索引，再更新 Markdown navigation：
 
 ```text
 devflow_code_index(action="scan", changedFiles=["<changed-file>", "..."])
@@ -34,7 +34,7 @@ devflow_code_index(action="audit")
 
 当 code-index 可用时：
 
-1. 先从 `.planning/code-index/index.sqlite` 或 `relations.jsonl` 查 changed files 对应 symbols/relations。
+1. 先从 `.devflow/planning/code-index/index.sqlite` 或 `relations.jsonl` 查 changed files 对应 symbols/relations。
 2. 按 `routes_to`、`calls`、`imports`、`reads`、`writes` 扩展相关边。
 3. 回读 `evidence_path` 源码。
 4. 只把已确认且适合人读摘要的链路写入 navigation。

package/plugins/devflow-quality/skills/code-review/SKILL.md

@@ -15,11 +15,11 @@ description: "Use when code needs review for project conventions, spec complianc
 4. 若需修复后复审，在下一轮 task 中携带上一轮 `chain_id`，最多三轮。第三轮仍有 P0 时停止当前任务；事实不足时停止并请求人工确认。每轮重新验证源码、契约和证据版本，不复用旧结论。
 5. 主 Agent 向用户交付门禁裁决、证据链、开放 finding 与下一步动作。本文后续的规范扫描和检查清单仍用于审查内容，但其“输出 Markdown”要求仅适用于独立调用本技能，不覆盖正式工作流协议。
 
-逐层对照 `.context/spec/` 规范文档，检查目标代码的合规性，输出可操作的问题清单。若项目存在 `.context/spec/index.md`，先按索引匹配 stack spec 和 codebase spec，再加载具体层级规范。
+逐层对照 `.devflow/context/spec/` 规范文档，检查目标代码的合规性，输出可操作的问题清单。若项目存在 `.devflow/context/spec/index.md`，先按索引匹配 stack spec 和 codebase spec，再加载具体层级规范。
 
 ## 核心原则
 
-1. **规范是唯一标准** — 只对照 `.context/spec/` 中的规范文档，不参考其他已有代码；代码推断规则必须低于显式规范和 codebase spec
+1. **规范是唯一标准** — 只对照 `.devflow/context/spec/` 中的规范文档，不参考其他已有代码；代码推断规则必须低于显式规范和 codebase spec
 2. **文件级全量扫描** — 扫描目标文件的每一行，不只看"最近改动的部分"
 3. **逐条不跳过** — 规范文档中的每一条规则都要检查，包括"看起来无关"的细节。**禁止主观过滤**：不能因为"这个 VO 字段很简单"、"只有一个字段"、"直接传字符串"等主观判断而跳过检查项，规范就是规范，简单的代码同样要逐条对照
 4. **加法和减法都查** — 既查"缺了什么该有的"，也查"多了什么不该有的"（未使用方法/字段/import）
@@ -31,7 +31,7 @@ description: "Use when code needs review for project conventions, spec complianc
 **当 code-review 作为 feature-development 工作流的独立 `code-review` step 被调用时必须执行。** 独立调用 code-review（如"帮我 review 一下 XX 模块"）时，若提供 phase number 则尝试关联变更清单，否则跳过此步。
 
 1. **定位变更清单**：
-   - 若传入 phase number：从 phase 目录的 CONTEXT.md 推断功能名，查找 `.planning/features/{功能名}/变更清单.md`
+   - 若传入 phase number：从 phase 目录的 CONTEXT.md 推断功能名，查找 `.devflow/planning/features/{功能名}/变更清单.md`
    - 若直接调用但用户提供了变更清单路径：使用用户指定路径
    - 若找不到变更清单：跳过此步，在输出 REVIEW.md 中标注 "无变更清单，跳过完成标准验证"
 
@@ -114,12 +114,12 @@ seam 标注: "只改 OrderWorkflow.process()"
 ### 第二步：加载规范（渐进式）
 
 **必读**（每次审查都要读）：
-1. `.planning/rules/INDEX.md`（如存在）— 找到项目规则入口
-2. `.context/spec/index.md`（如存在）— 匹配目标文件所在 codebase 的 stack spec 和 codebase spec
-3. 命中的 `.context/spec/stacks/{stack_key}.md` — 技术栈通用规范
-4. 命中的 `.context/spec/backend|frontend/{codebase}.md` — 项目实例规范
-5. `.planning/code-index/`（如存在）— 用于调用方、被调用方、导入、读写资源、测试覆盖等关系事实定位
-6. 兼容旧规范：`.context/spec/backend/index.md` 和 `.context/spec/backend/go.md`（如存在）
+1. `.devflow/planning/rules/INDEX.md`（如存在）— 找到项目规则入口
+2. `.devflow/context/spec/index.md`（如存在）— 匹配目标文件所在 codebase 的 stack spec 和 codebase spec
+3. 命中的 `.devflow/context/spec/stacks/{stack_key}.md` — 技术栈通用规范
+4. 命中的 `.devflow/context/spec/backend|frontend/{codebase}.md` — 项目实例规范
+5. `.devflow/planning/code-index/`（如存在）— 用于调用方、被调用方、导入、读写资源、测试覆盖等关系事实定位
+6. 兼容旧规范：`.devflow/context/spec/backend/index.md` 和 `.devflow/context/spec/backend/go.md`（如存在）
 
 **按层级按需加载**（只读涉及的层级，详见 `references/spec-checklist.md`）：
 - Handler 层 → 读 `handler.md`
@@ -130,7 +130,7 @@ seam 标注: "只改 OrderWorkflow.process()"
 - 有分页 → 读 `pagination.md`
 
 **经验教训**（目录存在时读取）：
-- `.context/lessons/README.md`（如存在）— 项目积累的踩坑经验；不存在时跳过，不阻塞审查
+- `.devflow/context/lessons/README.md`（如存在）— 项目积累的踩坑经验；不存在时跳过，不阻塞审查
 
 ### 第三步：逐层执行审查
 
@@ -150,7 +150,7 @@ seam 标注: "只改 OrderWorkflow.process()"
 **⛔ Gate 合规检查：** 审查输出中，每个涉及源码的结论必须附带 code-index 符号引用（格式：`[符号名 @ path:line]`）。若审查全程未出现 code-index 查询操作，或输出中的源码引用无 code-index 依据，则在问题清单最上方追加：
 
 ```
-⛔ SOURCE-READ GATE VIOLATION — 本次审查未走 .planning/code-index/ gate。
+⛔ SOURCE-READ GATE VIOLATION — 本次审查未走 .devflow/planning/code-index/ gate。
 审查结论降级为"未经索引验证"，需重新执行。
 ```
 
@@ -244,7 +244,7 @@ seam 标注: "只改 OrderWorkflow.process()"
 ```markdown
 ## 完成标准验证
 
-> **来源**：`.planning/features/{功能名}/变更清单.md`
+> **来源**：`.devflow/planning/features/{功能名}/变更清单.md`
 > **格式**：checkbox（N 条）/ legacy（M 条）
 > **总结**：{passed}/{total} 通过，{failed} 未通过，{unverifiable} 待人工，{skipped} 跳过
 

package/plugins/devflow-quality/skills/code-review/references/spec-checklist.md

@@ -4,7 +4,7 @@
 
 ## 规范文件路径
 
-所有规范文件位于 `.context/spec/backend/` 目录下。
+所有规范文件位于 `.devflow/context/spec/backend/` 目录下。
 
 ## 加载矩阵
 

package/plugins/devflow-quality/skills/workflow-acceptance-test-design/SKILL.md

@@ -13,22 +13,22 @@ description: "Use after integration verification and before change planning to d
 
 1. 先调用 `devflow_contract(action="status")` 检查当前会话是否有 active contract；
 2. 未激活时调用 `devflow_contract(action="activate", feature="<feature>", step="acceptance-test-design")` 合成并激活（planning / waiting-user / awaiting-approval，或 Runtime 已触发当前步骤的 executing 回合均可；Core 校验 STATE 当前 feature/step 与图谱 revision 后由用户确认）；
-3. 会话中断后 contract 由 runtime 在 `session_start` 时从 `.planning/contracts/{feature}/EC-*.json` 自动恢复；恢复时校验 state/graph revision，推进后自动失效，需重新合成。
+3. 会话中断后 contract 由 runtime 在 `session_start` 时从 `.devflow/planning/contracts/{feature}/EC-*.json` 自动恢复；恢复时校验 state/graph revision，推进后自动失效，需重新合成。
 
 ## 输入
 
 按顺序读取：
 
 1. `devflow_requirement_graph(action="inspect")` 的已确认 `REQ/BR/BC/AC` 节点与当前 revision；
-2. `.planning/features/{feature}/integration-report.md`、API 契约、UI 方案、前后端技术方案；
+2. `.devflow/planning/features/{feature}/integration-report.md`、API 契约、UI 方案、前后端技术方案；
 3. 当前图谱中的 `RISK/WSH/WLC/DECISION` 节点；
-4. `.planning/toolchain.md`、`.planning/execution-contract.md` 和项目测试能力。
+4. `.devflow/planning/toolchain.md`、`.devflow/planning/execution-contract.md` 和项目测试能力。
 
 若需求、契约或架构事实不足以写出可观察 oracle，记录缺口并回流到上游；不得用实现猜测补全。
 
 ## 生成规则
 
-先调用 `devflow_api_test_matrix(action="compile", feature="...")`（无 API 时也会写 no-op 测试资产），检查 `.planning/features/{feature}/完整API验收测试用例.md` 中的契约缺口；存在 `API-*` 时通过后调用 `devflow_api_test_matrix(action="import", feature="...")`。Core 会一次性生成并导入全部 API `TC-*`：
+先调用 `devflow_api_test_matrix(action="compile", feature="...")`（无 API 时也会写 no-op 测试资产），检查 `.devflow/planning/features/{feature}/完整API验收测试用例.md` 中的契约缺口；存在 `API-*` 时通过后调用 `devflow_api_test_matrix(action="import", feature="...")`。Core 会一次性生成并导入全部 API `TC-*`：
 
 - 每个字段的缺失、`null`、错误类型、最小/最大（长度、数值、数组项）、超长、非法格式/模式、非法枚举；
 - 仅由有效等价类构成的 pairwise 组合（负向值一项一测，避免错误码歧义）；
@@ -62,13 +62,13 @@ description: "Use after integration verification and before change planning to d
 
 ## 输出
 
-写 `.planning/features/{feature}/验收测试设计.md` 作为派生视图，包含：TC 覆盖矩阵、自动/人工/阻塞数量、每项专项义务的 TC/环境前提和当前图谱 revision。写对应 `.meta.json`，其 revision/fingerprint 必须来自 Core 的 `tests.json` 视图。
+写 `.devflow/planning/features/{feature}/验收测试设计.md` 作为派生视图，包含：TC 覆盖矩阵、自动/人工/阻塞数量、每项专项义务的 TC/环境前提和当前图谱 revision。写对应 `.meta.json`，其 revision/fingerprint 必须来自 Core 的 `tests.json` 视图。
 
 API 完整测试资产由 Core 额外写入：
 
-- `.planning/requirements/{feature}/api-test-matrix.json`：机器可读的请求、预期和派生义务；
-- `.planning/features/{feature}/完整API验收测试用例.md`：可审查的人类视图；
-- `.planning/features/{feature}/api-acceptance-bindings.template.json`：导入后的 TC 与 HTTP 执行绑定模板。
+- `.devflow/planning/requirements/{feature}/api-test-matrix.json`：机器可读的请求、预期和派生义务；
+- `.devflow/planning/features/{feature}/完整API验收测试用例.md`：可审查的人类视图；
+- `.devflow/planning/features/{feature}/api-acceptance-bindings.template.json`：导入后的 TC 与 HTTP 执行绑定模板。
 
 运行 `devflow_requirement_graph(action="validate")` 和 machine evidence。通过后交给 `workflow-change-plan` 绑定实现任务。
 

package/plugins/devflow-quality/skills/workflow-gen-test-guide/SKILL.md

@@ -14,17 +14,17 @@ description: "根据功能点梳理和需求基线生成检查点树形态的测
 
 必须先读取 `legacy/SKILL.md`，再按其中引用的相对 `references/`、`assets/` 规则生成：
 
-`.planning/features/{feature}/测试指导书.md`
+`.devflow/planning/features/{feature}/测试指导书.md`
 
 当前 Devflow 输入路径映射如下（旧版 Skill 的 WORKSPACE_ROOT 逻辑已由适配器显式映射）：
 
-- `.planning/requirements/baseline.md`
-- `.planning/features/{feature}/功能点梳理.md`
-- `.planning/PROJECT.md`
-- `.planning/navigation/INDEX.md`
+- `.devflow/planning/requirements/baseline.md`
+- `.devflow/planning/features/{feature}/功能点梳理.md`
+- `.devflow/planning/PROJECT.md`
+- `.devflow/planning/navigation/INDEX.md`
 
 旧版 Skill 中的旧目录和外部 PRD URL 约定不能直接写入项目；以本适配器列出的
-`.planning/` 路径为准。若旧版资源要求读取不存在的文档，必须在“待确认/缺少内容”分支记录，不得伪造文件或事实。
+`.devflow/planning/` 路径为准。若旧版资源要求读取不存在的文档，必须在“待确认/缺少内容”分支记录，不得伪造文件或事实。
 
 该步骤只生成检查点树文档，不生成或修改 Core 所有的 `tests.json`、`api-test-matrix.json`、需求图谱和验收测试冻结事实。结构化 `TC-*` 测试仍由后续 `workflow-acceptance-test-design` 负责。
 

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/SKILL.md

@@ -5,11 +5,11 @@ argument-hint: "<功能名> [@PRD文档.md 或 语雀URL] [--auto]"
 user-invocable: true
 pattern: generator
 inputs:
-  - ".planning/features/{feature}/功能点梳理.md"
-  - ".planning/requirements/baseline.md"
-  - ".planning/PROJECT.md"
+  - ".devflow/planning/features/{feature}/功能点梳理.md"
+  - ".devflow/planning/requirements/baseline.md"
+  - ".devflow/planning/PROJECT.md"
   - "可选 PRD 原文（仅在当前步骤明确提供时读取）"
-output: ".planning/features/{feature}/测试指导书.md"
+output: ".devflow/planning/features/{feature}/测试指导书.md"
 allowed-tools:
   - Read
   - Write
@@ -20,7 +20,7 @@ allowed-tools:
 
 # 检查点树生成 Skill
 
-> Devflow 适配说明：本文件随插件分发，由上层适配器调用。项目事实统一位于 `.planning/`；执行时以本文件的 Devflow 路径和适配器传入的输入为准，不解析旧版的 `_shared/` 或机器本地路径。
+> Devflow 适配说明：本文件随插件分发，由上层适配器调用。项目事实统一位于 `.devflow/planning/`；执行时以本文件的 Devflow 路径和适配器传入的输入为准，不解析旧版的 `_shared/` 或机器本地路径。
 
 This skill consumes 需求(PRD/baseline/功能点梳理) and creates a **检查点树**(checkpoint tree)——每个可测点展平成树的叶子检查点(一句话,可勾可数),**不是**用例字段块形态。Do not re-discuss requirements or generate technical plans.
 
@@ -32,21 +32,21 @@ This skill consumes 需求(PRD/baseline/功能点梳理) and creates a **检查
 Devflow 由 Runtime 传入当前项目根目录和 feature，不再解析旧版 `WORKSPACE_ROOT` 参数。
 
 路径约定：
-- **共享文件**: `.planning/` — PROJECT.md, STATE.md, navigation/
-- **功能文件**: `.planning/features/{feature}/` — baseline.md, 功能点梳理.md, 测试指导书.md, etc.
+- **共享文件**: `.devflow/planning/` — PROJECT.md, STATE.md, navigation/
+- **功能文件**: `.devflow/planning/features/{feature}/` — baseline.md, 功能点梳理.md, 测试指导书.md, etc.
 </workspace_config>
 
 ## Outputs
 
 Always create or update:
 
-- `.planning/features/{feature}/测试指导书.md`（**检查点树形态**,非用例字段块形态。供 change-xmind 转 xmind）
+- `.devflow/planning/features/{feature}/测试指导书.md`（**检查点树形态**,非用例字段块形态。供 change-xmind 转 xmind）
 
 > 本 skill 产出**检查点树**:每个可测点是树的一句话叶子,按 `测试视角层→功能模块→子模块/组件→状态/维度分叉→条件→叶子` 组织,**标题纯语义名(无 FP/章节号)**。**不产**用例字段块形态(无 优先级/关联/前置/步骤/预期 块)。
 
 ## Argument Handling
 
-- `<功能名>`: 由 Devflow 当前 feature 提供，用于定位 `.planning/features/{feature}/` 和输出路径。
+- `<功能名>`: 由 Devflow 当前 feature 提供，用于定位 `.devflow/planning/features/{feature}/` 和输出路径。
 - `@PRD文档.md` 或 `语雀URL`: 可选,PRD 原文(feature-breakdown 缺失时作为可测点源头,有则始终读作覆盖核对基准)。
 - `--auto`: do not ask for supplementary information; mark gaps as `待确认` 进 PT-xxx 分支。
 
@@ -83,9 +83,9 @@ Load bundled resources only when needed:
 
 源头优先级(feature-breakdown > baseline > PRD 原文),按可用性读:
 
-1. Read `.planning/features/{feature}/功能点梳理.md` — 首选(字段级三维叶子,可测点素材)。
-2. Read `.planning/requirements/baseline.md` — FP/BR/BC/CR 清单 + 澄清过的规则。
-3. Read `.planning/PROJECT.md` — 项目上下文 + 代码路径(Phase 1.5 用)。
+1. Read `.devflow/planning/features/{feature}/功能点梳理.md` — 首选(字段级三维叶子,可测点素材)。
+2. Read `.devflow/planning/requirements/baseline.md` — FP/BR/BC/CR 清单 + 澄清过的规则。
+3. Read `.devflow/planning/PROJECT.md` — 项目上下文 + 代码路径(Phase 1.5 用)。
 4. **Read PRD 原文**(语雀 URL 或 `@文件.md`)— 始终读,作为覆盖核对的基准。feature-breakdown/baseline 缺失时,PRD 是可测点的唯一源头。
 5. 若 feature-breakdown 和 baseline 都缺失且无 PRD → 报错,要求用户提供需求来源。
 
@@ -96,7 +96,7 @@ This phase runs ONLY when PROJECT.md "Project Locations" table contains at least
 ### 1.5.1 Load Navigation Files
 
 If code paths exist:
-1. Read `.planning/navigation/INDEX.md`.
+1. Read `.devflow/planning/navigation/INDEX.md`.
 2. Follow only navigation documents linked from INDEX.md; do not require fixed FRONTEND.md, ADMIN.md, or BACKEND.md filenames.
 3. Extract concrete directory paths for components, pages, routes, controllers, services, models/entities, and enums/constants from the available navigation documents.
 4. If a category is absent, record it as unavailable rather than inventing a path.
@@ -264,7 +264,7 @@ Consolidate findings into an internal "Code Context Summary" (NOT written to dis
 
 ## Phase 5 — 输出检查点树
 
-加载 `assets/output-template.md`。按其层级约定写 `.planning/features/{feature}/测试指导书.md`(文件名保留,内容是检查点树形态):
+加载 `assets/output-template.md`。按其层级约定写 `.devflow/planning/features/{feature}/测试指导书.md`(文件名保留,内容是检查点树形态):
 
 1. 来源信息
 2. 检查点树(Phase 3-4 组织的 **测试视角层→功能模块→子模块/组件→状态/维度分叉→条件→叶子** 缩进结构,标题纯语义名)