@guanlin4924/devflow-pi 0.1.93 → 0.1.94

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

@@ -38,9 +38,9 @@
 
 | 来源 | 结论 | 对本方案的影响 |
 |------|------|----------------|
-| `.planning/milestones/...` | {{结论}} | {{影响}} |
-| `.planning/requirements/...` | {{结论}} | {{影响}} |
-| `.planning/lessons/...` | {{结论}} | {{影响}} |
+| `.devflow/planning/milestones/...` | {{结论}} | {{影响}} |
+| `.devflow/planning/requirements/...` | {{结论}} | {{影响}} |
+| `.devflow/planning/lessons/...` | {{结论}} | {{影响}} |
 
 ## 四、现有功能说明
 
@@ -163,13 +163,13 @@ erDiagram
 
 | 规则来源 | 是否存在 | 影响说明 |
 |----------|----------|----------|
-| `.planning/rules/INDEX.md` | {{是/否}} | {{说明}} |
-| `.planning/execution-contract.md` | {{是/否}} | {{说明}} |
-| `.planning/toolchain.md` | {{是/否}} | {{说明}} |
-| `.planning/lessons/README.md` | {{是/否}} | {{说明}} |
-| `.context/spec/backend/index.md` | {{是/否}} | {{说明}} |
-| `.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/context/spec/backend/index.md` | {{是/否}} | {{说明}} |
+| `.devflow/context/workflow/` | {{是/否}} | {{说明}} |
+| `.devflow/context/lessons/README.md` | {{是/否}} | {{说明}} |
 | `AGENTS.md` / `CLAUDE.md` | {{是/否}} | {{说明}} |
 
 ### 9.2 适用规范

package/plugins/devflow-design/skills/workflow-backend-tech-spec/references/affected-module-exploration.md

@@ -14,7 +14,7 @@
 
 ### 步骤1：定位关键文件
 
-优先使用 `.planning/code-index/` 定位候选 symbol、entrypoint、calls、reads/writes 和 tested_by 关系；然后回读 `evidence_path:evidence_line` 附近源码。code-index 不存在或过期时，再按下表的目录约定和 `rg` 兜底。
+优先使用 `.devflow/planning/code-index/` 定位候选 symbol、entrypoint、calls、reads/writes 和 tested_by 关系；然后回读 `evidence_path:evidence_line` 附近源码。code-index 不存在或过期时，再按下表的目录约定和 `rg` 兜底。
 
 | 层级 | 定位方式 | 最少读取 |
 |------|----------|----------|
@@ -54,6 +54,6 @@
 - [ ] 是否有现有字段/方法/枚举的结构化表格（不是从 PRD 复制）？
 - [ ] 是否明确了每个模块是"复用"、"扩展"还是"新增"？
 - [ ] 是否实际读取了代码文件（不是仅靠文件名推断）？
-- [ ] 若 `.planning/code-index/` 存在，是否记录了用于定位的 symbol/relation evidence？
+- [ ] 若 `.devflow/planning/code-index/` 存在，是否记录了用于定位的 symbol/relation evidence？
 
 **此检查不通过，不得进入 Phase 3（生成文档）。**

package/plugins/devflow-design/skills/workflow-backend-tech-spec/references/code-explore-guide.md

@@ -4,7 +4,7 @@ Use this guide to explore the target backend without assuming outbound-call's Go
 
 ## Exploration Order
 
-1. Read `.planning/navigation/INDEX.md` → filter backend/service-type codebases → load their `{name}.md` navigation files to identify root, framework, entry points, layers, persistence, jobs, integrations, config, and commands.
+1. Read `.devflow/planning/navigation/INDEX.md` → filter backend/service-type codebases → load their `{name}.md` navigation files to identify root, framework, entry points, layers, persistence, jobs, integrations, config, and commands.
 2. Read the project rule package via `references/project-rule-contract.md`.
 3. Start from baseline `FP-*`, `BR-*`, `BC-*`, and confirmed `CR-*` decisions.
 4. Search only the relevant modules first; expand outward only when the call chain or data flow requires it.

package/plugins/devflow-design/skills/workflow-backend-tech-spec/references/project-rule-contract.md

@@ -6,30 +6,30 @@ Use this contract when generating backend technical plans. A project rule packag
 
 Look for rule sources in the target project, in this order:
 
-1. `.planning/rules/INDEX.md`
-2. `.planning/execution-contract.md`
-3. `.planning/toolchain.md`
-4. `.planning/lessons/README.md`
-5. `.planning/milestones/`
-6. `.planning/requirements/`
-7. `.context/spec/index.md`
-8. matching `.context/spec/stacks/{stack_key}.md`
-9. matching `.context/spec/backend/{codebase}.md`
-10. `.context/spec/backend/index.md`
-11. `.context/spec/backend/`
-12. `.planning/code-index/` when source-level relation facts are needed
-13. `.context/workflow/tdd.md`
-14. `.context/workflow/verification.md`
-15. `.context/workflow/checklist.md`
-16. `.context/lessons/README.md`
+1. `.devflow/planning/rules/INDEX.md`
+2. `.devflow/planning/execution-contract.md`
+3. `.devflow/planning/toolchain.md`
+4. `.devflow/planning/lessons/README.md`
+5. `.devflow/planning/milestones/`
+6. `.devflow/planning/requirements/`
+7. `.devflow/context/spec/index.md`
+8. matching `.devflow/context/spec/stacks/{stack_key}.md`
+9. matching `.devflow/context/spec/backend/{codebase}.md`
+10. `.devflow/context/spec/backend/index.md`
+11. `.devflow/context/spec/backend/`
+12. `.devflow/planning/code-index/` when source-level relation facts are needed
+13. `.devflow/context/workflow/tdd.md`
+14. `.devflow/context/workflow/verification.md`
+15. `.devflow/context/workflow/checklist.md`
+16. `.devflow/context/lessons/README.md`
 17. root `AGENTS.md`, `CLAUDE.md`, or equivalent project instruction files
 
 If none exist, explicitly write `未发现项目规则包` and continue with code exploration and conservative assumptions.
 
 History rule:
 
-- Use `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, and phase `CONTEXT.md` files as the primary history model.
-- Treat `.context/lessons/` and `features/` as compatible legacy/project-rule evidence only when present in the target project.
+- Use `.devflow/planning/milestones/`, `.devflow/planning/requirements/`, `.devflow/planning/lessons/`, and phase `CONTEXT.md` files as the primary history model.
+- Treat `.devflow/context/lessons/` and `features/` as compatible legacy/project-rule evidence only when present in the target project.
 - Do not require outbound-call style history files.
 
 ## What To Extract
@@ -37,8 +37,8 @@ History rule:
 Extract only backend-relevant rules:
 
 - Technology stack and framework.
-- Matching stack spec and codebase spec from `.context/spec/index.md` when available.
-- Code-index symbols/relations for affected entrypoints, callers, callees, data/resource reads and writes, tests, and external integrations when `.planning/code-index/` exists.
+- Matching stack spec and codebase spec from `.devflow/context/spec/index.md` when available.
+- Code-index symbols/relations for affected entrypoints, callers, callees, data/resource reads and writes, tests, and external integrations when `.devflow/planning/code-index/` exists.
 - Layer model and dependency direction.
 - Naming, function signature, validation, error handling, logging, transaction, pagination, permission, and data access rules.
 - Required code generation, mock generation, dependency injection, migration, or build commands.

package/plugins/devflow-design/skills/workflow-design-rule-pack/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-design-rule-pack
-description: Use when workflow-ui-spec or workflow-frontend-tech-spec needs a reusable UI/UX design rule package, ui-ux-pro-max recommendations, or project installation of .context/spec/design across repositories.
+description: Use when workflow-ui-spec or workflow-frontend-tech-spec needs a reusable UI/UX design rule package, ui-ux-pro-max recommendations, or project installation of .devflow/context/spec/design across repositories.
 ---
 
 # Workflow Design Rule Pack
@@ -11,12 +11,12 @@ This skill provides the reusable source for the project design rule package cons
 
 Use this skill when:
 
-- A project lacks `.context/spec/design/index.md`.
+- A project lacks `.devflow/context/spec/design/index.md`.
 - UI workflow steps need the shared UI/UX recommendation pack.
 - `ui-ux-pro-max` should be available in a project without copying it by hand.
 - The same design rules need to be reused across repositories.
 
-`workflow-project-context` is the default lifecycle owner for frontend projects: it invokes this installer after the code index is ready, records the result in the initialization manifest, and owns `.context/spec/design/index.md`. Call this skill directly only to repair or deliberately refresh the shared recommendation assets.
+`workflow-project-context` is the default lifecycle owner for frontend projects: it invokes this installer after the code index is ready, records the result in the initialization manifest, and owns `.devflow/context/spec/design/index.md`. Call this skill directly only to repair or deliberately refresh the shared recommendation assets.
 
 Do not use this skill as a replacement for `workflow-ui-spec` or `workflow-frontend-tech-spec`. It only installs and documents shared references; workflow skills still decide how to apply them.
 
@@ -30,7 +30,7 @@ devflow_design_rule(args=[])
 
 Default behavior:
 
-- Copies `assets/design/` into `.context/spec/design/`.
+- Copies `assets/design/` into `.devflow/context/spec/design/`.
 - Creates missing directories.
 - Does not overwrite existing project files.
 - Keeps project-specific confirmed tokens in the target project.
@@ -64,7 +64,7 @@ for path in \
   recommendations/accessibility.md \
   recommendations/component-library.md \
   tools/ui-ux-pro-max/SKILL.md; do
-  test -s ".context/spec/design/$path"
+  test -s ".devflow/context/spec/design/$path"
 done
 ```
 
@@ -75,7 +75,7 @@ Pass only when every expected file exists and is non-empty. A missing file, a ze
 ## Source of Truth
 
 - Skill source: `skill://workflow-design-rule-pack/assets/design/`
-- Project installed copy: `.context/spec/design/`
+- Project installed copy: `.devflow/context/spec/design/`
 
 Workflow skills must read the installed project copy. The project copy is the place where local overrides and confirmed project tokens live.
 
@@ -85,7 +85,7 @@ Design conclusion priority remains:
 
 1. User decisions, design artifacts, confirmed requirement baseline
 2. Existing code, component library, current project tokens
-3. `.context/spec/design/tokens/project-tokens.md`
-4. `.context/spec/design/recommendations/` and `ui-ux-pro-max` query results
+3. `.devflow/context/spec/design/tokens/project-tokens.md`
+4. `.devflow/context/spec/design/recommendations/` and `ui-ux-pro-max` query results
 
 Recommendation sources are never authoritative project facts unless the user or project rules explicitly confirm them.

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/index.md

@@ -32,9 +32,9 @@
 工具位置：
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system -p "<Project Name>"
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --stack react
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system -p "<Project Name>"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --stack react
 ```
 
 常用域：

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/accessibility.md

@@ -26,6 +26,6 @@
 ## 查询辅助
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "accessibility aria focus keyboard form labels color contrast" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "aria focus keyboard semantic form" --domain web
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "accessibility aria focus keyboard form labels color contrast" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "aria focus keyboard semantic form" --domain web
 ```

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/component-library.md

@@ -26,6 +26,6 @@
 需要补充组件模式时，可查：
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "form button modal table accessibility" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "button form table" --stack shadcn
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "form button modal table accessibility" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "button form table" --stack shadcn
 ```

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/design-systems.md

@@ -13,7 +13,7 @@
 优先用动态工具生成完整建议：
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<product type> <industry> <style keywords>" --design-system -p "<Feature or Project Name>" --format markdown
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<product type> <industry> <style keywords>" --design-system -p "<Feature or Project Name>" --format markdown
 ```
 
 输出只能进入 UI-SPEC 的“推荐方案（待拍板）”或“待确认事项”，不能直接进入“设计稿事实”。

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/responsive-grid.md

@@ -24,6 +24,6 @@
 ## 查询辅助
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive layout mobile horizontal scroll touch target" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive layout" --stack html-tailwind
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive layout mobile horizontal scroll touch target" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive layout" --stack html-tailwind
 ```

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/stack-guidelines.md

@@ -1,17 +1,17 @@
 # Stack Guidelines Recommendations
 
-本文件提供技术栈实现参考。项目 `.context/spec/stacks/`、前端代码约定和 workflow 内置 stack slots 优先。
+本文件提供技术栈实现参考。项目 `.devflow/context/spec/stacks/`、前端代码约定和 workflow 内置 stack slots 优先。
 
 ## 使用方式
 
 按项目实际栈调用动态工具补充：
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "layout form table accessibility performance" --stack react
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "image routing cache hydration" --stack nextjs
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "composition api form table state" --stack vue
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive utility accessibility" --stack html-tailwind
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "components theme form" --stack shadcn
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "layout form table accessibility performance" --stack react
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "image routing cache hydration" --stack nextjs
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "composition api form table state" --stack vue
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive utility accessibility" --stack html-tailwind
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "components theme form" --stack shadcn
 ```
 
 ## 前端技术方案使用边界

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/ux-patterns.md

@@ -35,6 +35,6 @@
 ## 查询辅助
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "loading error feedback duplicate submit animation" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "form validation feedback" --domain web
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "loading error feedback duplicate submit animation" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "form validation feedback" --domain web
 ```

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/tokens/project-tokens.md

@@ -4,7 +4,7 @@
 
 ## 状态
 
-当前项目尚未沉淀全局设计 token。workflow-ui-spec 生成某个功能的 token 时，应先写入对应功能的 `.planning/features/{功能名}/UI-SPEC.md`。
+当前项目尚未沉淀全局设计 token。workflow-ui-spec 生成某个功能的 token 时，应先写入对应功能的 `.devflow/planning/features/{功能名}/UI-SPEC.md`。
 
 ## 允许写入本文件的条件
 

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/tools/ui-ux-pro-max/SKILL.md

@@ -135,7 +135,7 @@ Extract key information from user request:
 **Always start with `--design-system`** to get comprehensive recommendations with reasoning:
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
 ```
 
 This command:
@@ -146,7 +146,7 @@ This command:
 
 **Example:**
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
 ```
 
 ### Step 2b: Persist Design System (Master + Overrides Pattern)
@@ -154,7 +154,7 @@ python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa w
 To save the design system for hierarchical retrieval across sessions, add `--persist`:
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
 ```
 
 This creates:
@@ -163,7 +163,7 @@ This creates:
 
 **With page-specific override:**
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"
 ```
 
 This also creates:
@@ -179,7 +179,7 @@ This also creates:
 After getting the design system, use domain searches to get additional details:
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
 ```
 
 **When to use detailed searches:**
@@ -197,7 +197,7 @@ python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" -
 Get implementation-specific best practices. If user doesn't specify a stack, **default to `html-tailwind`**.
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
 ```
 
 Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`, `react-native`, `flutter`, `shadcn`, `jetpack-compose`
@@ -251,7 +251,7 @@ Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`
 ### Step 2: Generate Design System (REQUIRED)
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"
 ```
 
 **Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.
@@ -260,16 +260,16 @@ python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa w
 
 ```bash
 # Get UX guidelines for animation and accessibility
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
 
 # Get alternative typography options if needed
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
 ```
 
 ### Step 4: Stack Guidelines
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind
 ```
 
 **Then:** Synthesize design system + detailed searches and implement the design.
@@ -282,10 +282,10 @@ The `--design-system` flag supports two output formats:
 
 ```bash
 # ASCII box (default) - best for terminal display
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
 
 # Markdown - best for documentation
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
 ```
 
 ---

package/plugins/devflow-design/skills/workflow-design-rule-pack/scripts/install.py

@@ -34,7 +34,7 @@ def copy_tree(src: Path, dst: Path, overwrite: bool, include_index: bool) -> tup
 
 
 def main() -> int:
-    parser = argparse.ArgumentParser(description="Install .context/spec/design rule pack")
+    parser = argparse.ArgumentParser(description="Install .devflow/context/spec/design rule pack")
     parser.add_argument("--target", default=".", help="Target repository root, default current directory")
     parser.add_argument("--overwrite", action="store_true", help="Overwrite existing target files")
     parser.add_argument(
@@ -47,7 +47,7 @@ def main() -> int:
     skill_root = Path(__file__).resolve().parents[1]
     source = skill_root / "assets" / "design"
     target_root = Path(args.target).resolve()
-    target = target_root / ".context" / "spec" / "design"
+    target = target_root / ".devflow/context" / "spec" / "design"
 
     if not source.exists():
         raise SystemExit(f"Source design rule pack not found: {source}")

package/plugins/devflow-design/skills/workflow-feature-breakdown/SKILL.md

@@ -12,15 +12,15 @@ argument-hint: <功能名> [--auto]
 user-invocable: true
 pattern: generator+reviewer
 inputs:
-- .planning/requirements/baseline.md
-- .planning/features/{功能名}/UI-SPEC.md
-- .planning/PROJECT.md
-- .planning/navigation/INDEX.md
-- .planning/navigation/*.md
-- .planning/milestones/
-- .planning/requirements/
-- .planning/lessons/README.md
-output: .planning/features/{功能名}/功能点梳理.md
+- .devflow/planning/requirements/baseline.md
+- .devflow/planning/features/{功能名}/UI-SPEC.md
+- .devflow/planning/PROJECT.md
+- .devflow/planning/navigation/INDEX.md
+- .devflow/planning/navigation/*.md
+- .devflow/planning/milestones/
+- .devflow/planning/requirements/
+- .devflow/planning/lessons/README.md
+output: .devflow/planning/features/{功能名}/功能点梳理.md
 allowed-tools:
 - Read
 - Write
@@ -38,15 +38,15 @@ This skill consumes the requirement baseline and creates a test-readable feature
 
 Always create or update:
 
-- `.planning/features/{功能名}/功能点梳理.md`
-- `.planning/features/{功能名}/功能点梳理.meta.json` — structured metadata (fp_count, dimension_counts, page_count). Schema in `feature-development.yaml` under `steps[feature-breakdown].meta_output.fields`.
+- `.devflow/planning/features/{功能名}/功能点梳理.md`
+- `.devflow/planning/features/{功能名}/功能点梳理.meta.json` — structured metadata (fp_count, dimension_counts, page_count). Schema in `feature-development.yaml` under `steps[feature-breakdown].meta_output.fields`.
 
 Do not create by default:
 
-- `.planning/features/{功能名}/前端技术方案.md`
-- `.planning/features/{功能名}/后端技术方案.md`
-- `.planning/features/{功能名}/变更清单.md`
-- `.planning/requirements/baseline.md`
+- `.devflow/planning/features/{功能名}/前端技术方案.md`
+- `.devflow/planning/features/{功能名}/后端技术方案.md`
+- `.devflow/planning/features/{功能名}/变更清单.md`
+- `.devflow/planning/requirements/baseline.md`
 
 ## Argument Handling
 
@@ -58,11 +58,11 @@ Parse `$ARGUMENTS` before reading files:
 The canonical output directory must come from the baseline when available:
 
 ```text
-.planning/features/{功能名}/
+.devflow/planning/features/{功能名}/
 ```
 
 Do not invent another directory name from the project name, PRD title, or module name.
-If an older baseline still points to `features/{功能名}/`, treat it as a legacy path and prefer `.planning/features/{功能名}/` for new output unless the user explicitly requests legacy compatibility.
+If an older baseline still points to `features/{功能名}/`, treat it as a legacy path and prefer `.devflow/planning/features/{功能名}/` for new output unless the user explicitly requests legacy compatibility.
 
 ## Resource Loading
 
@@ -82,14 +82,14 @@ Load bundled resources only when needed:
 
 Read:
 
-1. `.planning/requirements/baseline.md`
-2. `.planning/PROJECT.md` if present
-3. `.planning/navigation/INDEX.md` if present
-4. `.planning/navigation/INDEX.md` — identify relevant codebases from the Codebase Registry, then load their navigation files (`{name}.md`)
-5. `.planning/code-index/` when present and the feature breakdown needs existing route/component/API/data-flow relation facts
-6. `.planning/milestones/` only when baseline historical impact references prior milestones
-7. `.planning/requirements/` and `.planning/lessons/` only when baseline historical impact or challenge review references them
-8. `.context/lessons/README.md` when present; load only lesson files whose title or summary matches current FP/BR/BC keywords
+1. `.devflow/planning/requirements/baseline.md`
+2. `.devflow/planning/PROJECT.md` if present
+3. `.devflow/planning/navigation/INDEX.md` if present
+4. `.devflow/planning/navigation/INDEX.md` — identify relevant codebases from the Codebase Registry, then load their navigation files (`{name}.md`)
+5. `.devflow/planning/code-index/` when present and the feature breakdown needs existing route/component/API/data-flow relation facts
+6. `.devflow/planning/milestones/` only when baseline historical impact references prior milestones
+7. `.devflow/planning/requirements/` and `.devflow/planning/lessons/` only when baseline historical impact or challenge review references them
+8. `.devflow/context/lessons/README.md` when present; load only lesson files whose title or summary matches current FP/BR/BC keywords
 
 The baseline is the source of truth. Use its:
 
@@ -126,9 +126,9 @@ Baseline section mapping:
 
 History model rule:
 
-- Use `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, and phase `CONTEXT.md` as primary history.
-- Treat `features/` or `.context/lessons/` as optional legacy/project-rule sources only when present and referenced by the baseline.
-- Treat matching `.context/lessons/` files as regression guards for review. They do not expand scope by themselves, but any current FP touching the same seam must carry the lesson as a constraint or explain why it is not applicable.
+- Use `.devflow/planning/milestones/`, `.devflow/planning/requirements/`, `.devflow/planning/lessons/`, and phase `CONTEXT.md` as primary history.
+- Treat `features/` or `.devflow/context/lessons/` as optional legacy/project-rule sources only when present and referenced by the baseline.
+- Treat matching `.devflow/context/lessons/` files as regression guards for review. They do not expand scope by themselves, but any current FP touching the same seam must carry the lesson as a constraint or explain why it is not applicable.
 
 Current slice rule:
 
@@ -284,7 +284,7 @@ If stopping because a user answer changes baseline-level requirements, report:
 
 Read `assets/output-template.md`.
 
-Create `.planning/features/{功能名}/` if needed and write `.planning/features/{功能名}/功能点梳理.md`.
+Create `.devflow/planning/features/{功能名}/` if needed and write `.devflow/planning/features/{功能名}/功能点梳理.md`.
 
 The document must include:
 
@@ -321,7 +321,7 @@ The document must include:
 | 重叠嗅探 | 梳理的功能是否会与某个已有功能形成"两套并存"？ |
 | 历史嗅探 | `features/` 中是否有类似功能曾被做过？ |
 
-若 `.planning/code-index/` 存在，复用/冲突/重叠嗅探应优先查询 symbols/relations，再回读源码 evidence；缺失或过期时再用 navigation 和 `rg` 兜底。
+若 `.devflow/planning/code-index/` 存在，复用/冲突/重叠嗅探应优先查询 symbols/relations，再回读源码 evidence；缺失或过期时再用 navigation 和 `rg` 兜底。
 
 ### 7.2a 链路完整性审查（MANDATORY）
 

package/plugins/devflow-design/skills/workflow-feature-breakdown/assets/output-template.md

@@ -2,10 +2,10 @@
 
 ## 一、来源信息
 
-- **需求基线**：`.planning/requirements/baseline.md`
+- **需求基线**：`.devflow/planning/requirements/baseline.md`
 - **功能名称**：{{功能名称}}
 - **功能名**：{{功能名}}
-- **输出目录**：`.planning/features/{{功能名}}/`
+- **输出目录**：`.devflow/planning/features/{{功能名}}/`
 - **生成时间**：{{日期}}
 - **当前执行切片**：{{SL-001}} — {{切片名称}}