@guanlin4924/devflow-pi 0.1.92 → 0.1.94

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

@@ -6,15 +6,15 @@
 
 | Rule File | Purpose | Status |
 |-----------|---------|--------|
-| `.planning/execution-contract.md` | Layer order, TDD strategy, codegen and verification gates | {{execution_contract_status}} |
-| `.planning/toolchain.md` | Build, test, lint, mock, migration commands | {{toolchain_status}} |
-| `.planning/lessons/README.md` | Cross-milestone lessons learned | {{lessons_status}} |
-| `.planning/code-index/` | Machine code facts: symbols, relations, entrypoints, and data flow | {{code_index_status}} |
-| `.context/spec/design/` | Frontend UI/UX recommendations and project-level design tokens | {{design_rule_pack_status}} |
-| `.context/spec/index.md` | Generated technical spec registry and read order | {{context_spec_index_status}} |
-| `.context/spec/stacks/` | Generated stack-level technical specs | {{stack_specs_status}} |
-| `.context/workflow/` | Existing workflow gates (TDD, verification, checklist) | {{context_workflow_status}} |
-| `.context/lessons/README.md` | Legacy project lessons | {{context_lessons_status}} |
+| `.devflow/planning/execution-contract.md` | Layer order, TDD strategy, codegen and verification gates | {{execution_contract_status}} |
+| `.devflow/planning/toolchain.md` | Build, test, lint, mock, migration commands | {{toolchain_status}} |
+| `.devflow/planning/lessons/README.md` | Cross-milestone lessons learned | {{lessons_status}} |
+| `.devflow/planning/code-index/` | Machine code facts: symbols, relations, entrypoints, and data flow | {{code_index_status}} |
+| `.devflow/context/spec/design/` | Frontend UI/UX recommendations and project-level design tokens | {{design_rule_pack_status}} |
+| `.devflow/context/spec/index.md` | Generated technical spec registry and read order | {{context_spec_index_status}} |
+| `.devflow/context/spec/stacks/` | Generated stack-level technical specs | {{stack_specs_status}} |
+| `.devflow/context/workflow/` | Existing workflow gates (TDD, verification, checklist) | {{context_workflow_status}} |
+| `.devflow/context/lessons/README.md` | Legacy project lessons | {{context_lessons_status}} |
 | `AGENTS.md` / `CLAUDE.md` | Root agent instructions | {{root_instructions_status}} |
 | `.cursorrules` | IDE-level AI rules | {{cursorrules_status}} |
 
@@ -22,58 +22,58 @@
 
 | Rule File | Path | Status |
 |-----------|------|--------|
-| Frontend Spec Index | `.context/spec/frontend/index.md` | {{frontend_spec_index_status}} |
-| Frontend Specs | `.context/spec/frontend/` | {{frontend_specs_status}} |
-| Design Specs | `.context/spec/design/` | {{design_specs_status}} |
+| Frontend Spec Index | `.devflow/context/spec/frontend/index.md` | {{frontend_spec_index_status}} |
+| Frontend Specs | `.devflow/context/spec/frontend/` | {{frontend_specs_status}} |
+| Design Specs | `.devflow/context/spec/design/` | {{design_specs_status}} |
 
 ## Backend Rules
 
 | Rule File | Path | Status |
 |-----------|------|--------|
-| Backend Spec Index | `.context/spec/backend/index.md` | {{backend_spec_index_status}} |
-| Backend Specs | `.context/spec/backend/` | {{backend_specs_status}} |
+| Backend Spec Index | `.devflow/context/spec/backend/index.md` | {{backend_spec_index_status}} |
+| Backend Specs | `.devflow/context/spec/backend/` | {{backend_specs_status}} |
 
 ## Stack Specs
 
 | Stack Key | Path | Codebases | Status |
 |-----------|------|-----------|--------|
-| {{stack_key}} | `.context/spec/stacks/{{stack_key}}.md` | {{codebases}} | {{stack_spec_status}} |
+| {{stack_key}} | `.devflow/context/spec/stacks/{{stack_key}}.md` | {{codebases}} | {{stack_spec_status}} |
 
 ## Codebase Specs
 
 | Codebase | Type | Stack Key | Path | Status |
 |----------|------|-----------|------|--------|
-| {{codebase_name}} | {{codebase_type}} | {{stack_key}} | `.context/spec/{{domain}}/{{codebase_name}}.md` | {{codebase_spec_status}} |
+| {{codebase_name}} | {{codebase_type}} | {{stack_key}} | `.devflow/context/spec/{{domain}}/{{codebase_name}}.md` | {{codebase_spec_status}} |
 
 ## Spec Read Contract
 
 Downstream skills must read technical rules 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. Matching `.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. Matching `.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
 
 ## Workflow Rules
 
 | Rule File | Path | Status |
 |-----------|------|--------|
-| TDD Gate | `.context/workflow/tdd.md` | {{tdd_status}} |
-| Verification Gate | `.context/workflow/verification.md` | {{verification_status}} |
-| Checklist | `.context/workflow/checklist.md` | {{checklist_status}} |
+| TDD Gate | `.devflow/context/workflow/tdd.md` | {{tdd_status}} |
+| Verification Gate | `.devflow/context/workflow/verification.md` | {{verification_status}} |
+| Checklist | `.devflow/context/workflow/checklist.md` | {{checklist_status}} |
 
 ## History Model
 
 | Source | Role | Status |
 |--------|------|--------|
-| `.planning/milestones/` | Archived milestone summaries | {{milestones_status}} |
-| `.planning/requirements/` | Requirement baselines | {{requirements_status}} |
-| `.planning/lessons/` | Cross-milestone lessons | {{planning_lessons_status}} |
-| `.planning/*/CONTEXT.md` | Phase/session decisions | {{context_md_status}} |
+| `.devflow/planning/milestones/` | Archived milestone summaries | {{milestones_status}} |
+| `.devflow/planning/requirements/` | Requirement baselines | {{requirements_status}} |
+| `.devflow/planning/lessons/` | Cross-milestone lessons | {{planning_lessons_status}} |
+| `.devflow/planning/*/CONTEXT.md` | Phase/session decisions | {{context_md_status}} |
 
 ---
 

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

@@ -9,9 +9,9 @@
 - **Run Started At**: {{run_started_at}}
 - **Last Scan At**: {{last_scan_at}}
 - **Initialized By**: `workflow-project-context`
-- **Project File**: `.planning/PROJECT.md`
-- **Navigation Root**: `.planning/navigation/`
-- **Code Index Root**: `.planning/code-index/`（generated by default unless fast mode skipped it）
+- **Project File**: `.devflow/planning/PROJECT.md`
+- **Navigation Root**: `.devflow/planning/navigation/`
+- **Code Index Root**: `.devflow/planning/code-index/`（generated by default unless fast mode skipped it）
 
 ## Workflow State
 
@@ -25,7 +25,7 @@
 | Name | Type | Path | Scan Status | Navigation File |
 |------|------|------|-------------|-----------------|
 {{#codebases}}
-| {{name}} | {{type}} | {{path}} | {{scan_status}} | `.planning/navigation/{{name}}.md` |
+| {{name}} | {{type}} | {{path}} | {{scan_status}} | `.devflow/planning/navigation/{{name}}.md` |
 {{/codebases}}
 
 ## Completion
@@ -39,9 +39,9 @@
 {{#codebases}}
 | {{name}} navigation | {{nav_status}} | {{nav_notes}} |
 {{/codebases}}
-| Rules index (`.planning/rules/INDEX.md`) | {{rules_index_status}} | {{rules_index_notes}} |
-| Execution contract (`.planning/execution-contract.md`) | {{execution_contract_status}} | {{execution_contract_notes}} |
-| Toolchain contract (`.planning/toolchain.md`) | {{toolchain_status}} | {{toolchain_notes}} |
+| Rules index (`.devflow/planning/rules/INDEX.md`) | {{rules_index_status}} | {{rules_index_notes}} |
+| Execution contract (`.devflow/planning/execution-contract.md`) | {{execution_contract_status}} | {{execution_contract_notes}} |
+| Toolchain contract (`.devflow/planning/toolchain.md`) | {{toolchain_status}} | {{toolchain_notes}} |
 | Project rule package (other sources) | {{project_rule_package_status}} | {{project_rule_package_notes}} |
 | Requirements baseline | Not created | Created later by workflow-requirement-baseline |
 | Feature breakdown | Not created | Created later by workflow-feature-breakdown |

package/plugins/devflow-core/skills/workflow-project-context/references/navigation-guide.md

@@ -16,20 +16,20 @@ Run the following for EACH codebase identified in Step 1:
 4. Read README files only for commands and architecture notes.
 5. Inspect top-level source folders and common entry files.
 6. Identify project rule package sources (once for the whole project, not per codebase):
-   - `.planning/rules/INDEX.md`
-   - `.planning/execution-contract.md`
-   - `.planning/toolchain.md`
-   - `.planning/lessons/README.md`
-   - `.planning/milestones/`
-   - `.planning/requirements/`
-   - `.context/spec/`
-   - `.context/workflow/`
-   - `.context/lessons/README.md`
+   - `.devflow/planning/rules/INDEX.md`
+   - `.devflow/planning/execution-contract.md`
+   - `.devflow/planning/toolchain.md`
+   - `.devflow/planning/lessons/README.md`
+   - `.devflow/planning/milestones/`
+   - `.devflow/planning/requirements/`
+   - `.devflow/context/spec/`
+   - `.devflow/context/workflow/`
+   - `.devflow/context/lessons/README.md`
    - root `AGENTS.md` / `CLAUDE.md`
    - `.cursorrules` files within each codebase root
 7. Identify history model locations (once for the whole project):
-   - primary: `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, `.planning/*/CONTEXT.md`
-   - optional legacy: `features/`, `.context/lessons/`
+   - primary: `.devflow/planning/milestones/`, `.devflow/planning/requirements/`, `.devflow/planning/lessons/`, `.devflow/planning/*/CONTEXT.md`
+   - optional legacy: `features/`, `.devflow/context/lessons/`
 8. Stop once entry points, conventions, commands, rule package locations, and history model locations are identified for each codebase.
 
 ## Scan Depth
@@ -113,7 +113,7 @@ Frontend navigation fields:
 - Styles / theme
 - Env config
 - Dev/build/test commands
-- Frontend rule sources such as `.context/spec/frontend/`, `.context/spec/design/`, `.planning/rules/`, `.planning/toolchain.md`, and lessons
+- Frontend rule sources such as `.devflow/context/spec/frontend/`, `.devflow/context/spec/design/`, `.devflow/planning/rules/`, `.devflow/planning/toolchain.md`, and lessons
 
 ## Frontend Stack Slot Detection
 
@@ -202,45 +202,45 @@ Common sources:
 
 | Source | Purpose |
 |--------|---------|
-| `.planning/rules/INDEX.md` | Project rule index used by workflow skills |
-| `.planning/execution-contract.md` | Layer order, TDD strategy, codegen and verification gates |
-| `.planning/toolchain.md` | Build, test, lint, mock, migration, and codegen commands |
-| `.planning/lessons/README.md` | Project lessons maintained by workflow |
-| `.planning/milestones/` | Primary milestone/history records for this workflow |
-| `.planning/requirements/` | Current or historical requirement baselines |
-| `.context/spec/index.md` | Generated or existing technical spec registry |
-| `.context/spec/stacks/` | Stack-level technical specs generated from stack profiles |
-| `.context/spec/frontend/` / `.context/spec/backend/` | Codebase-specific technical specs |
-| `.context/workflow/` | Existing workflow gates such as TDD and verification |
-| `.context/lessons/README.md` | Existing lessons from project work |
+| `.devflow/planning/rules/INDEX.md` | Project rule index used by workflow skills |
+| `.devflow/planning/execution-contract.md` | Layer order, TDD strategy, codegen and verification gates |
+| `.devflow/planning/toolchain.md` | Build, test, lint, mock, migration, and codegen commands |
+| `.devflow/planning/lessons/README.md` | Project lessons maintained by workflow |
+| `.devflow/planning/milestones/` | Primary milestone/history records for this workflow |
+| `.devflow/planning/requirements/` | Current or historical requirement baselines |
+| `.devflow/context/spec/index.md` | Generated or existing technical spec registry |
+| `.devflow/context/spec/stacks/` | Stack-level technical specs generated from stack profiles |
+| `.devflow/context/spec/frontend/` / `.devflow/context/spec/backend/` | Codebase-specific technical specs |
+| `.devflow/context/workflow/` | Existing workflow gates such as TDD and verification |
+| `.devflow/context/lessons/README.md` | Existing lessons from project work |
 | `AGENTS.md` / `CLAUDE.md` | Root agent instructions |
 
-If both `.planning/rules/` and `.context/spec/` exist, record both. Do not merge them during initialization.
+If both `.devflow/planning/rules/` and `.devflow/context/spec/` exist, record both. Do not merge them during initialization.
 
 ## Generated Context Spec Checks
 
-When project initialization generates `.context/spec/`, verify:
+When project initialization generates `.devflow/context/spec/`, verify:
 
 - Every local/scannable codebase has a stack profile with `stack_key`, manifest path, and dependency fingerprint.
-- Every unique `stack_key` has exactly one `.context/spec/stacks/{stack_key}.md`.
-- Every frontend-type codebase has `.context/spec/frontend/{name}.md`.
-- Every backend/service-type codebase has `.context/spec/backend/{name}.md`.
-- `.context/spec/index.md` maps each codebase to its stack spec, codebase spec, and navigation file.
+- Every unique `stack_key` has exactly one `.devflow/context/spec/stacks/{stack_key}.md`.
+- Every frontend-type codebase has `.devflow/context/spec/frontend/{name}.md`.
+- Every backend/service-type codebase has `.devflow/context/spec/backend/{name}.md`.
+- `.devflow/context/spec/index.md` maps each codebase to its stack spec, codebase spec, and navigation file.
 - Generated specs include version metadata and regeneration triggers.
 - Stack specs contain stack-level guidance only; codebase-local paths and route/module names belong in codebase specs.
 
 ## History Model Detection
 
-This workflow uses `.planning` artifacts as the primary long-term memory. Do not assume outbound-call style `features/*.spec.md` history exists.
+This workflow uses `.devflow/planning` artifacts as the primary long-term memory. Do not assume outbound-call style `features/*.spec.md` history exists.
 
 | Source | Role |
 |--------|------|
-| `.planning/milestones/` | Archived milestones and delivery summaries |
-| `.planning/requirements/` | Requirement baselines and requirement decisions |
-| `.planning/lessons/` | Cross-milestone lessons |
-| `.planning/*/CONTEXT.md` | Phase/session decisions and handoff context |
+| `.devflow/planning/milestones/` | Archived milestones and delivery summaries |
+| `.devflow/planning/requirements/` | Requirement baselines and requirement decisions |
+| `.devflow/planning/lessons/` | Cross-milestone lessons |
+| `.devflow/planning/*/CONTEXT.md` | Phase/session decisions and handoff context |
 | `features/` | Optional legacy feature docs if the target project already has them |
-| `.context/lessons/` | Optional legacy/project-rule lessons |
+| `.devflow/context/lessons/` | Optional legacy/project-rule lessons |
 
 Record whether each primary source exists. Label legacy sources as legacy/project-rule evidence rather than the default history model.
 
@@ -248,14 +248,14 @@ Record whether each primary source exists. Label legacy sources as legacy/projec
 
 - All codebase locations are recorded in the Codebase Registry.
 - Nonexistent or remote-only locations are marked pending.
-- Each codebase has a navigation file at `.planning/navigation/{name}.md`.
+- Each codebase has a navigation file at `.devflow/planning/navigation/{name}.md`.
 - Frameworks are recorded or `待确认` for each codebase.
 - Entry points and key directories are recorded or `待确认` for each codebase.
 - Frontend-type codebases have component conventions.
 - Backend-type codebases have layer conventions.
 - Dev/build/test commands are recorded or `待确认` for each codebase.
 - Project rule package sources are recorded when present.
-- History model sources are recorded, with `.planning` sources primary and legacy sources labeled.
+- History model sources are recorded, with `.devflow/planning` sources primary and legacy sources labeled.
 - `STATE.md` includes current step, completed steps, pending steps, blockers, and next action.
 - `INDEX.md` includes Codebase Registry and downstream read contract.
 - Initialization quality is marked as `complete`, `partial`, `pending`, or `not_applicable`.

package/plugins/devflow-core/skills/workflow-project-context/scripts/validate_initialization.py

@@ -17,25 +17,25 @@ SKILL_ROOT = Path(__file__).resolve().parents[1]
 SPEC_TEMPLATE_ROOT = SKILL_ROOT / "assets" / "spec-templates"
 
 CODE_INDEX_FILES = (
-    ".planning/code-index/index.sqlite",
-    ".planning/code-index/files.jsonl",
-    ".planning/code-index/symbols.jsonl",
-    ".planning/code-index/relations.jsonl",
-    ".planning/code-index/AUDIT.md",
+    ".devflow/planning/code-index/index.sqlite",
+    ".devflow/planning/code-index/files.jsonl",
+    ".devflow/planning/code-index/symbols.jsonl",
+    ".devflow/planning/code-index/relations.jsonl",
+    ".devflow/planning/code-index/AUDIT.md",
 )
 
 DESIGN_RULE_PACK_FILES = (
-    ".context/spec/design/tokens/project-tokens.md",
-    ".context/spec/design/recommendations/accessibility.md",
-    ".context/spec/design/recommendations/component-library.md",
-    ".context/spec/design/tools/ui-ux-pro-max/SKILL.md",
+    ".devflow/context/spec/design/tokens/project-tokens.md",
+    ".devflow/context/spec/design/recommendations/accessibility.md",
+    ".devflow/context/spec/design/recommendations/component-library.md",
+    ".devflow/context/spec/design/tools/ui-ux-pro-max/SKILL.md",
 )
 
 STATUS_FILES = (
-    ".planning/STATE.md",
-    ".planning/PROJECT.md",
-    ".planning/navigation/INDEX.md",
-    ".planning/rules/INDEX.md",
+    ".devflow/planning/STATE.md",
+    ".devflow/planning/PROJECT.md",
+    ".devflow/planning/navigation/INDEX.md",
+    ".devflow/planning/rules/INDEX.md",
 )
 
 
@@ -44,7 +44,7 @@ def parse_args() -> argparse.Namespace:
     parser.add_argument("--root", default=".")
     parser.add_argument(
         "--manifest",
-        default=".planning/project-context-run.json",
+        default=".devflow/planning/project-context-run.json",
     )
     return parser.parse_args()
 
@@ -136,7 +136,7 @@ def validate_status_markers(
         content = path.read_text(encoding="utf-8")
         if marker not in content:
             errors.append(f"current-run status marker missing: {relative_path}")
-        if relative_path == ".planning/STATE.md" and "PENDING_TEMPLATE" in content:
+        if relative_path == ".devflow/planning/STATE.md" and "PENDING_TEMPLATE" in content:
             errors.append("STATE.md contains an unresolved PENDING_TEMPLATE blocker")
 
 
@@ -149,8 +149,13 @@ def validate_code_index(
     mode = manifest.get("mode")
     status = manifest.get("code_index_status")
     if mode == "full":
+        if status == "degraded":
+            reason = str(manifest.get("code_index_skip_reason", ""))
+            if reason != "code_index_publish_failed":
+                errors.append("degraded full mode requires code_index_publish_failed reason")
+            return
         if status != "complete":
-            errors.append("full mode requires code_index_status=complete")
+            errors.append("full mode requires code_index_status=complete or degraded")
         if manifest.get("code_index_skip_reason") != "none":
             errors.append("full mode requires code_index_skip_reason=none")
         for relative_path in CODE_INDEX_FILES:
@@ -454,7 +459,7 @@ def validate_domain_indexes(
         )
 
     for domain, expected_markers in expected_by_domain.items():
-        relative_path = f".context/spec/{domain}/index.md"
+        relative_path = f".devflow/context/spec/{domain}/index.md"
         path = resolve_project_path(root, relative_path)
         require_fresh_file(path, started_at, errors)
         if not path.is_file():

package/plugins/devflow-design/skills/workflow-api-call-guide/SKILL.md

@@ -26,8 +26,8 @@ description: "Use after backend-tech-spec, before integration-verify. Generates
 
 ## 产出位置
 
-- `.planning/features/{功能名}/api-call-guide.md`
-- `.planning/features/{功能名}/api-call-guide.meta.json`
+- `.devflow/planning/features/{功能名}/api-call-guide.md`
+- `.devflow/planning/features/{功能名}/api-call-guide.meta.json`
 
 `api-call-guide.meta.json` 必须包含：
 
@@ -44,8 +44,8 @@ description: "Use after backend-tech-spec, before integration-verify. Generates
 
 ## 输入
 
-- `.planning/features/{功能名}/api-contract.md` — **API 签名唯一权威源**
-- `.planning/features/{功能名}/后端技术方案.md` — 后端实现细节和 seam 位置
+- `.devflow/planning/features/{功能名}/api-contract.md` — **API 签名唯一权威源**
+- `.devflow/planning/features/{功能名}/后端技术方案.md` — 后端实现细节和 seam 位置
 
 ## 核心原则
 

package/plugins/devflow-design/skills/workflow-api-contract/SKILL.md

@@ -24,17 +24,17 @@ description: "Use after requirement-baseline, before dual-track fork. Defines sh
 
 ## 产出位置
 
-- `.planning/features/{功能名}/api-contract.md`
-- `.planning/features/{功能名}/api-contract.meta.json`
+- `.devflow/planning/features/{功能名}/api-contract.md`
+- `.devflow/planning/features/{功能名}/api-contract.meta.json`
 
 The meta file must also set `traceability_status: "passed"` only after every API design has been written to `traceability.json.designs` and `traceability_check.py --stage design` succeeds; otherwise set `failed` and do not advance.
 
 ## 输入
 
-- `.planning/requirements/baseline.md` — 需求基线（FP/BR/BC）
-- `.planning/navigation/INDEX.md` 和相关 codebase navigation — 粗定位已有接口
-- `.planning/code-index/`（如存在）— 查询已有 route/handler/API symbol 与 `routes_to` / `calls` 关系，确认接口复用和冲突
-- `.planning/requirements/{feature}/traceability.json` — 每个接口必须回指它的 `REQ-*`，不能只写 FP 标题
+- `.devflow/planning/requirements/baseline.md` — 需求基线（FP/BR/BC）
+- `.devflow/planning/navigation/INDEX.md` 和相关 codebase navigation — 粗定位已有接口
+- `.devflow/planning/code-index/`（如存在）— 查询已有 route/handler/API symbol 与 `routes_to` / `calls` 关系，确认接口复用和冲突
+- `.devflow/planning/requirements/{feature}/traceability.json` — 每个接口必须回指它的 `REQ-*`，不能只写 FP 标题
 
 使用 code-index 时，必须回读 `evidence_path:evidence_line` 附近源码后再把既有接口写入契约；不得只凭 Markdown navigation 或 relation 摘要判断。
 
@@ -46,7 +46,7 @@ The meta file must also set `traceability_status: "passed"` only after every API
 4. **负载职责明确** — 事务命令、运营查询和统计查询不得在同一个接口语义中混写；统计查询必须引用已确认的 `METRIC-*`，并在响应中约定 `as_of`/新鲜度语义或明确强一致依据。
 5. **数据模型共享** — 核心业务实体定义在这里，前后端共用一个数据模型
 6. **切片对齐** — 若 baseline 包含 `SL-*`，先读取 `skill://workflow-pipeline/references/slice-safety-guide.md`，只为当前执行切片定义 API。后置切片接口不得提前进入契约。
-7. **既有接口优先查事实索引** — 当 `.planning/code-index/` 存在时，先用 Symbol/Relation 定位候选接口、调用方和处理器，再读取源码证据；缺失或过期时再按 navigation 和 `rg` 兜底。
+7. **既有接口优先查事实索引** — 当 `.devflow/planning/code-index/` 存在时，先用 Symbol/Relation 定位候选接口、调用方和处理器，再读取源码证据；缺失或过期时再按 navigation 和 `rg` 兜底。
 
 ## 可测试 API 契约（强制）
 
@@ -182,7 +182,7 @@ The meta file must also set `traceability_status: "passed"` only after every API
 - [ ] 每个涉及 API 的 FP 至少映射到一个接口
 - [ ] 若存在 `SL-*`，每个接口都标注当前 Slice ID，且未包含后置切片接口
 - [ ] 每个接口有完整的请求/响应结构
-- [ ] 若 `.planning/code-index/` 存在，已有接口复用/冲突判断已查询 code-index 并回读源码 evidence；未使用时已说明原因
+- [ ] 若 `.devflow/planning/code-index/` 存在，已有接口复用/冲突判断已查询 code-index 并回读源码 evidence；未使用时已说明原因
 - [ ] 核心数据模型已定义字段和类型
 - [ ] 没有包含实现细节（SQL、表结构、代码片段）
 - [ ] meta.json 中 `endpoint_count` 已记录接口总数

package/plugins/devflow-design/skills/workflow-api-supplement/SKILL.md

@@ -27,14 +27,14 @@ orchestrator 通过以下方式检测是否需要触发本 skill：
 
 ## 输入
 
-- `.planning/features/{功能名}/api-contract.md` — 已有 API 契约
-- `.planning/features/{功能名}/前端技术方案.md` — 刚刚完成的前端方案
-- `.planning/features/{功能名}/UI-SPEC.md` — UI 设计规范
+- `.devflow/planning/features/{功能名}/api-contract.md` — 已有 API 契约
+- `.devflow/planning/features/{功能名}/前端技术方案.md` — 刚刚完成的前端方案
+- `.devflow/planning/features/{功能名}/UI-SPEC.md` — UI 设计规范
 
 ## 产出
 
-- `.planning/features/{功能名}/api-supplement-requests.md`
-- `.planning/features/{功能名}/api-supplement-requests.meta.json`
+- `.devflow/planning/features/{功能名}/api-supplement-requests.md`
+- `.devflow/planning/features/{功能名}/api-supplement-requests.meta.json`
 
 即使没有 API 补充需求，也要生成 no-op meta：
 

package/plugins/devflow-design/skills/workflow-architecture-feasibility/SKILL.md

@@ -24,7 +24,7 @@ description: "Use after API contract and before frontend/backend technical speci
    - `recommendation_option_id` 是建议，不是自动决策。
 5. 对 `full` 评估，提交 `risk_type: architecture_option_risk` 的 `RISK` candidate，连接 `DECISION/WSH/WLC → RISK`，relation 为 `has_architecture_risk`。必须写失败模式、影响、处理、处理方式、负责人和复核条件。
 6. 只用 `devflow_requirement_graph(action="confirm")` 确认 WSH/WLC、架构 DECISION 和架构 RISK。Core 必须展示确认对话；确认方案比较时，用户确认的是显示的 `recommendation_option_id`，确认风险时只确认处理责任，不宣称生产风险已消失。
-7. 调用 `devflow_architecture_brief(action="render")` 生成 `.planning/features/{feature}/architecture-brief.md` 及 meta。不得手写或补写简报正文。
+7. 调用 `devflow_architecture_brief(action="render")` 生成 `.devflow/planning/features/{feature}/architecture-brief.md` 及 meta。不得手写或补写简报正文。
 
 ## 不变量
 

package/plugins/devflow-design/skills/workflow-backend-tech-spec/SKILL.md

@@ -12,26 +12,26 @@ argument-hint: <功能名>
 user-invocable: true
 pattern: generator+tool-wrapper
 inputs:
-- .planning/features/{功能名}/api-contract.md
-- .planning/features/{功能名}/architecture-brief.md
-- .planning/features/{功能名}/architecture-brief.meta.json
-- .planning/requirements/baseline.md
-- .planning/features/{功能名}/功能点梳理.md (optional, Track B context when already available)
-- .planning/PROJECT.md
-- .planning/navigation/INDEX.md
-- .planning/rules/INDEX.md
-- .planning/execution-contract.md
-- .planning/toolchain.md
-- .planning/lessons/README.md
-- .context/spec/index.md
-- .context/spec/stacks/
-- .context/spec/backend/index.md
-- .context/spec/backend/
-- .context/workflow/
-- .context/lessons/README.md（如存在）
-- .planning/milestones/
+- .devflow/planning/features/{功能名}/api-contract.md
+- .devflow/planning/features/{功能名}/architecture-brief.md
+- .devflow/planning/features/{功能名}/architecture-brief.meta.json
+- .devflow/planning/requirements/baseline.md
+- .devflow/planning/features/{功能名}/功能点梳理.md (optional, Track B context when already available)
+- .devflow/planning/PROJECT.md
+- .devflow/planning/navigation/INDEX.md
+- .devflow/planning/rules/INDEX.md
+- .devflow/planning/execution-contract.md
+- .devflow/planning/toolchain.md
+- .devflow/planning/lessons/README.md
+- .devflow/context/spec/index.md
+- .devflow/context/spec/stacks/
+- .devflow/context/spec/backend/index.md
+- .devflow/context/spec/backend/
+- .devflow/context/workflow/
+- .devflow/context/lessons/README.md（如存在）
+- .devflow/planning/milestones/
 - references/affected-module-exploration.md
-output: .planning/features/{功能名}/后端技术方案.md
+output: .devflow/planning/features/{功能名}/后端技术方案.md
 allowed-tools:
 - Read
 - Write
@@ -46,7 +46,7 @@ allowed-tools:
 
 ## 需求追溯硬约束
 
-读取 `.planning/requirements/{feature}/traceability.json`。每个设计章节必须列 `覆盖 REQ: REQ-*`；定时任务、批处理、导入和通知至少拆为“编排（扫描/触发/锁/重试）”与“业务算法（判定/计算/写入）”两个可独立验证的小节。不得把遍历全部活跃组织、发送通知、文件解析等编排事实藏在算法描述中。
+读取 `.devflow/planning/requirements/{feature}/traceability.json`。每个设计章节必须列 `覆盖 REQ: REQ-*`；定时任务、批处理、导入和通知至少拆为“编排（扫描/触发/锁/重试）”与“业务算法（判定/计算/写入）”两个可独立验证的小节。不得把遍历全部活跃组织、发送通知、文件解析等编排事实藏在算法描述中。
 
 当架构简报包含 `analytics_query`、`analytics_projection`、`METRIC-*` 或 `RM-*` 时，后端方案额外必须分别写明：业务事实源；指标粒度/纳入排除/时区与修正；读模型或直接聚合路径；索引/扫描范围；新鲜度；watermark/迟到数据；重建与对账。不得把统计 SQL 混进事务命令，或以“后续补统计”跳过这些字段。
 
@@ -67,17 +67,17 @@ allowed-tools:
 
 ### 第一阶段：理解需求
 
-1. 读取 `.planning/requirements/baseline.md` 理解需求
-2. 读取 `.planning/PROJECT.md` 了解项目上下文
-3. 如果 baseline.md 不存在，询问用户需求或在 `.planning/milestones/` 中查找相关历史
-4. 读取 `references/project-rule-contract.md`，按 Spec Read Contract 发现并加载目标项目的后端规则包：`.planning/rules/INDEX.md` → `.context/spec/index.md` → 命中的 stack spec → 命中的 backend codebase spec → navigation → code-index（如存在且需要关系事实）→ 源码
+1. 读取 `.devflow/planning/requirements/baseline.md` 理解需求
+2. 读取 `.devflow/planning/PROJECT.md` 了解项目上下文
+3. 如果 baseline.md 不存在，询问用户需求或在 `.devflow/planning/milestones/` 中查找相关历史
+4. 读取 `references/project-rule-contract.md`，按 Spec Read Contract 发现并加载目标项目的后端规则包：`.devflow/planning/rules/INDEX.md` → `.devflow/context/spec/index.md` → 命中的 stack spec → 命中的 backend codebase spec → navigation → code-index（如存在且需要关系事实）→ 源码
 5. 读取 `references/code-explore-guide.md`，按项目导航和规则包做通用后端探索
 6. 读取 baseline 的 `反向审视与用户拍板`、`待确认事项`、`下游输入契约`：
    - 已确认的冲突/复用/替代方案决策必须进入技术方案
    - 影响 scope、语义、归属、兼容性或实现成本的未确认项，不得被当成已确认需求
    - 若未确认项阻塞后端方案，询问用户；`--auto` 或无法询问时写入待确认事项和风险
-7. 读取 `.planning/features/{功能名}/api-contract.md`。在双轨模式下，后端方案必须以 API 契约和需求基线作为权威输入，不得等待 Track B 的 `功能点梳理.md` 才开始。
-8. 读取 `.planning/features/{功能名}/architecture-brief.md` 和 `.meta.json`，在文档开头记录消费的 `brief_revision`、`graph_revision` 和 `static_context_snapshot_revision`。`comparison_status=confirmed` 的选择可作为实现依据；其他状态只能作为风险或待确认前提，不得把 recommendation 写成已决定实现。若 `assessment_level=full` 但未 confirmed，停止并回到架构评估。
+7. 读取 `.devflow/planning/features/{功能名}/api-contract.md`。在双轨模式下，后端方案必须以 API 契约和需求基线作为权威输入，不得等待 Track B 的 `功能点梳理.md` 才开始。
+8. 读取 `.devflow/planning/features/{功能名}/architecture-brief.md` 和 `.meta.json`，在文档开头记录消费的 `brief_revision`、`graph_revision` 和 `static_context_snapshot_revision`。`comparison_status=confirmed` 的选择可作为实现依据；其他状态只能作为风险或待确认前提，不得把 recommendation 写成已决定实现。若 `assessment_level=full` 但未 confirmed，停止并回到架构评估。
 9. 若 `功能点梳理.md` 已存在，可作为测试可读上下文补充读取；若不存在，不阻塞 Track A。
 10. 若 baseline、api-contract 或 `功能点梳理.md` 包含 `SL-*` 切片计划，读取 `skill://workflow-pipeline/references/slice-safety-guide.md`，只为当前执行切片生成后端方案。后置切片只可作为依赖上下文或后续范围，不得生成库表、接口、任务或运行时设计。
 
@@ -86,9 +86,9 @@ allowed-tools:
 在设计前，探索相关实现：
 
 1. **读取 PROJECT.md 的 Project Layout 章节**，确定后端代码所在目录
-2. 按 `references/project-rule-contract.md` 的顺序读取项目规则包，优先使用 `.planning/rules/INDEX.md` 和 `.context/spec/index.md` 匹配 stack/codebase spec，兼容 `.context/spec/`、`.context/workflow/`、`.context/lessons/` 和根目录 `AGENTS.md` / `CLAUDE.md`
-3. 读取 `.planning/navigation/INDEX.md` → 筛选后端/服务类型代码库 → 加载对应 `{name}.md` 导航文件，按目标项目实际结构识别领域/模型、服务、持久化、接口、任务、集成、配置和迁移入口
-4. 若 `.planning/code-index/` 存在，用 Symbol Index 和 Relation Graph 查询相关入口、调用链、读写资源、测试和外部集成候选；读取 `evidence_path:evidence_line` 后再写现状结论
+2. 按 `references/project-rule-contract.md` 的顺序读取项目规则包，优先使用 `.devflow/planning/rules/INDEX.md` 和 `.devflow/context/spec/index.md` 匹配 stack/codebase spec，兼容 `.devflow/context/spec/`、`.devflow/context/workflow/`、`.devflow/context/lessons/` 和根目录 `AGENTS.md` / `CLAUDE.md`
+3. 读取 `.devflow/planning/navigation/INDEX.md` → 筛选后端/服务类型代码库 → 加载对应 `{name}.md` 导航文件，按目标项目实际结构识别领域/模型、服务、持久化、接口、任务、集成、配置和迁移入口
+4. 若 `.devflow/planning/code-index/` 存在，用 Symbol Index 和 Relation Graph 查询相关入口、调用链、读写资源、测试和外部集成候选；读取 `evidence_path:evidence_line` 后再写现状结论
 5. **现有功能复用检查**：编写任何新逻辑前，必须先在项目中搜索是否已有相同或相似功能的实现。优先使用 code-index 查询 symbols/relations；缺失或过期时再按导航和 `rg` 兜底。搜索范围包括：
    - `pkg/` 目录（已有外部集成封装，如支付、红包、短信、二维码等）
    - Service 层（已有业务能力）
@@ -160,12 +160,12 @@ allowed-tools:
 
 ### 第三阶段：生成文档
 
-1. 创建 `.planning/features/{功能名}/` 目录
+1. 创建 `.devflow/planning/features/{功能名}/` 目录
 2. 读取 `assets/backend-spec-template.md` 模板
 3. 按模板结构填充内容，并写入 `需求基线衔接`、`后端规范影响`、`能力抽象建议` 章节
-4. 文件名格式：`.planning/features/{功能名}/后端技术方案.md`
+4. 文件名格式：`.devflow/planning/features/{功能名}/后端技术方案.md`
 
-If an older baseline still points to root `features/{功能名}/`, treat that as a legacy read path. New backend tech-spec output stays under `.planning/features/{功能名}/`.
+If an older baseline still points to root `features/{功能名}/`, treat that as a legacy read path. New backend tech-spec output stays under `.devflow/planning/features/{功能名}/`.
 
 ### 第三阶段.5 — ADR 创建（按需）
 
@@ -201,7 +201,7 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 - 兼容性：无影响
 ```
 
-**ADR 存放路径**：`.planning/architecture/adr/{序号}-{主题}.md`
+**ADR 存放路径**：`.devflow/planning/architecture/adr/{序号}-{主题}.md`
 
 **不满足条件时不要创建 ADR。** 常规决策（字段名选择、参数顺序等）直接写在方案里即可。
 
@@ -213,9 +213,9 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 
 ### 第五阶段：结构化元数据
 
-完成后写入 `.planning/features/{功能名}/后端技术方案.meta.json`。必须从 `architecture-brief.meta.json` 原样复制：`brief_revision → architecture_brief_revision`、`graph_revision → architecture_graph_revision`、`static_context_snapshot_revision → architecture_static_context_snapshot_revision`、`comparison_status → architecture_comparison_status`。不得凭记忆填写或改写这些值。
+完成后写入 `.devflow/planning/features/{功能名}/后端技术方案.meta.json`。必须从 `architecture-brief.meta.json` 原样复制：`brief_revision → architecture_brief_revision`、`graph_revision → architecture_graph_revision`、`static_context_snapshot_revision → architecture_static_context_snapshot_revision`、`comparison_status → architecture_comparison_status`。不得凭记忆填写或改写这些值。
 
-完成后写入 `.planning/features/{功能名}/后端技术方案.meta.json`，字段定义见 `feature-development.yaml` 中 `steps[backend-tech-spec].meta_output.fields`：`api_count`, `table_count`, `migration_count`。
+完成后写入 `.devflow/planning/features/{功能名}/后端技术方案.meta.json`，字段定义见 `feature-development.yaml` 中 `steps[backend-tech-spec].meta_output.fields`：`api_count`, `table_count`, `migration_count`。
 
 ## 注意事项
 
@@ -227,8 +227,8 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 6. **必须描述现有功能** — 新功能如果影响现有功能，必须先描述现有功能的流程、字段、逻辑
 7. **统计类功能要详细** — 对于涉及统计表的变更，必须说明：现有字段及含义、现有统计 SQL/逻辑、Job 调度频率、新增字段及统计逻辑
 8. **只关注后端逻辑** — 流程图只描述后端服务的处理流程，不要包含前端行为
-9. **必须体现项目规则包** — 若目标项目存在 `.planning/rules/` 或 `.context/spec/`，后端方案必须列出适用规范、相关经验教训、工具链要求、测试策略和审查门禁
-10. **历史口径使用 `.planning`** — 与历史相关的判断优先来自 `.planning/milestones/`、`.planning/requirements/`、`.planning/lessons/` 和阶段 `CONTEXT.md`；`features/` 或 `.context/lessons/` 只作为目标项目存在时的兼容来源
+9. **必须体现项目规则包** — 若目标项目存在 `.devflow/planning/rules/` 或 `.devflow/context/spec/`，后端方案必须列出适用规范、相关经验教训、工具链要求、测试策略和审查门禁
+10. **历史口径使用 `.devflow/planning`** — 与历史相关的判断优先来自 `.devflow/planning/milestones/`、`.devflow/planning/requirements/`、`.devflow/planning/lessons/` 和阶段 `CONTEXT.md`；`features/` 或 `.devflow/context/lessons/` 只作为目标项目存在时的兼容来源
 11. **现有功能复用优先** — 编写任何新逻辑前，必须先在项目内搜索已有实现，避免重复造轮子。重点检查：`pkg/` 外部集成封装、Service 层业务能力、Repository 层数据访问模式、公共工具方法。发现已有封装时直接复用，严禁绕过直接写裸调用
 12. **遵循最佳实践标杆** — 新功能的设计（分层、命名、错误处理、参数封装、测试模式）必须与项目内已有标杆功能保持一致，不得引入与项目验证过的成熟模式相悖的新模式。若需偏离，必须在方案中说明理由
 13. **能力抽象** — 新功能中具有独立复用价值的部分（外部集成、通用业务能力），必须抽象为 `pkg/` 级模块，定义清晰的 Client 接口和参数/结果结构体，形成可被后续功能消费的项目能力资产
@@ -241,7 +241,7 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 - [ ] 涉及调用上游 API 的，是否已向用户索要接口文档并确认对接方案？（不可猜测 API 契约，包括 URL、认证、请求/响应结构、错误码）
 - [ ] 涉及的每个能力点（外部集成、业务逻辑、数据访问、工具方法），是否已在项目内完成复用搜索？**若已有封装却被绕过直接重写，方案不合格。**
 - [ ] `references/affected-module-exploration.md` 的探索产出检查是否全部通过？（现状流程图、字段/方法表格、集成点列表、复用/扩展/新增决策）**若不通过，必须先补充代码探索，不得继续写文档。**
-- [ ] 若 `.planning/code-index/` 存在，复用/影响范围/调用链/读写资源判断是否已查询 code-index 并回读源码 evidence？若未使用，是否说明缺失或过期原因？
+- [ ] 若 `.devflow/planning/code-index/` 存在，复用/影响范围/调用链/读写资源判断是否已查询 code-index 并回读源码 evidence？若未使用，是否说明缺失或过期原因？
 - [ ] 是否已找到项目内最佳实践标杆，并确认新功能的分层结构、命名、错误处理、参数封装模式与标杆一致？（若偏离，理由是否已写明？）
 - [ ] 新功能中具有独立复用价值的部分，是否已识别并抽象为 `pkg/` 级能力模块？接口定义、参数/结果结构体是否清晰？
 - [ ] 方案影响的现有功能是否已描述其**现状流程/字段/逻辑**？（先描述现状，再分析影响）
@@ -262,7 +262,7 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 
 - [ ] 方案包含：功能要点、影响范围、库表设计（DDL+ER）、流程设计、风险点
 - [ ] 不含前端组件、前端路由（那属于前端技术方案）
-- [ ] 若存在 `.planning/rules/` 或 `.context/spec/`，适用规范+经验教训+工具链+测试策略已列出
+- [ ] 若存在 `.devflow/planning/rules/` 或 `.devflow/context/spec/`，适用规范+经验教训+工具链+测试策略已列出
 - [ ] 审查结论已写入方案末尾
 
 **审查结论不通过时不得报告 "Step 3c 完成"。**