@guanlin4924/devflow-pi 0.1.0

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/tools/ui-ux-pro-max/scripts/search.py

@@ -0,0 +1,114 @@
+#!/usr/bin/env python3
+# -*- coding: utf-8 -*-
+"""
+UI/UX Pro Max Search - BM25 search engine for UI/UX style guides
+Usage: python search.py "<query>" [--domain <domain>] [--stack <stack>] [--max-results 3]
+       python search.py "<query>" --design-system [-p "Project Name"]
+       python search.py "<query>" --design-system --persist [-p "Project Name"] [--page "dashboard"]
+
+Domains: style, prompt, color, chart, landing, product, ux, typography
+Stacks: html-tailwind, react, nextjs
+
+Persistence (Master + Overrides pattern):
+  --persist    Save design system to design-system/MASTER.md
+  --page       Also create a page-specific override file in design-system/pages/
+"""
+
+import argparse
+import sys
+import io
+from core import CSV_CONFIG, AVAILABLE_STACKS, MAX_RESULTS, search, search_stack
+from design_system import generate_design_system, persist_design_system
+
+# Force UTF-8 for stdout/stderr to handle emojis on Windows (cp1252 default)
+if sys.stdout.encoding and sys.stdout.encoding.lower() != 'utf-8':
+    sys.stdout = io.TextIOWrapper(sys.stdout.buffer, encoding='utf-8')
+if sys.stderr.encoding and sys.stderr.encoding.lower() != 'utf-8':
+    sys.stderr = io.TextIOWrapper(sys.stderr.buffer, encoding='utf-8')
+
+
+def format_output(result):
+    """Format results for Claude consumption (token-optimized)"""
+    if "error" in result:
+        return f"Error: {result['error']}"
+
+    output = []
+    if result.get("stack"):
+        output.append(f"## UI Pro Max Stack Guidelines")
+        output.append(f"**Stack:** {result['stack']} | **Query:** {result['query']}")
+    else:
+        output.append(f"## UI Pro Max Search Results")
+        output.append(f"**Domain:** {result['domain']} | **Query:** {result['query']}")
+    output.append(f"**Source:** {result['file']} | **Found:** {result['count']} results\n")
+
+    for i, row in enumerate(result['results'], 1):
+        output.append(f"### Result {i}")
+        for key, value in row.items():
+            value_str = str(value)
+            if len(value_str) > 300:
+                value_str = value_str[:300] + "..."
+            output.append(f"- **{key}:** {value_str}")
+        output.append("")
+
+    return "\n".join(output)
+
+
+if __name__ == "__main__":
+    parser = argparse.ArgumentParser(description="UI Pro Max Search")
+    parser.add_argument("query", help="Search query")
+    parser.add_argument("--domain", "-d", choices=list(CSV_CONFIG.keys()), help="Search domain")
+    parser.add_argument("--stack", "-s", choices=AVAILABLE_STACKS, help="Stack-specific search (html-tailwind, react, nextjs)")
+    parser.add_argument("--max-results", "-n", type=int, default=MAX_RESULTS, help="Max results (default: 3)")
+    parser.add_argument("--json", action="store_true", help="Output as JSON")
+    # Design system generation
+    parser.add_argument("--design-system", "-ds", action="store_true", help="Generate complete design system recommendation")
+    parser.add_argument("--project-name", "-p", type=str, default=None, help="Project name for design system output")
+    parser.add_argument("--format", "-f", choices=["ascii", "markdown"], default="ascii", help="Output format for design system")
+    # Persistence (Master + Overrides pattern)
+    parser.add_argument("--persist", action="store_true", help="Save design system to design-system/MASTER.md (creates hierarchical structure)")
+    parser.add_argument("--page", type=str, default=None, help="Create page-specific override file in design-system/pages/")
+    parser.add_argument("--output-dir", "-o", type=str, default=None, help="Output directory for persisted files (default: current directory)")
+
+    args = parser.parse_args()
+
+    # Design system takes priority
+    if args.design_system:
+        result = generate_design_system(
+            args.query, 
+            args.project_name, 
+            args.format,
+            persist=args.persist,
+            page=args.page,
+            output_dir=args.output_dir
+        )
+        print(result)
+        
+        # Print persistence confirmation
+        if args.persist:
+            project_slug = args.project_name.lower().replace(' ', '-') if args.project_name else "default"
+            print("\n" + "=" * 60)
+            print(f"✅ Design system persisted to design-system/{project_slug}/")
+            print(f"   📄 design-system/{project_slug}/MASTER.md (Global Source of Truth)")
+            if args.page:
+                page_filename = args.page.lower().replace(' ', '-')
+                print(f"   📄 design-system/{project_slug}/pages/{page_filename}.md (Page Overrides)")
+            print("")
+            print(f"📖 Usage: When building a page, check design-system/{project_slug}/pages/[page].md first.")
+            print(f"   If exists, its rules override MASTER.md. Otherwise, use MASTER.md.")
+            print("=" * 60)
+    # Stack search
+    elif args.stack:
+        result = search_stack(args.query, args.stack, args.max_results)
+        if args.json:
+            import json
+            print(json.dumps(result, indent=2, ensure_ascii=False))
+        else:
+            print(format_output(result))
+    # Domain search
+    else:
+        result = search(args.query, args.domain, args.max_results)
+        if args.json:
+            import json
+            print(json.dumps(result, indent=2, ensure_ascii=False))
+        else:
+            print(format_output(result))

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

@@ -0,0 +1,67 @@
+#!/usr/bin/env python3
+"""Install the workflow design rule pack into a target project."""
+
+from __future__ import annotations
+
+import argparse
+import shutil
+from pathlib import Path
+
+
+def copy_tree(src: Path, dst: Path, overwrite: bool, include_index: bool) -> tuple[int, int]:
+    copied = 0
+    skipped = 0
+
+    for source_file in src.rglob("*"):
+        if source_file.is_dir():
+            continue
+
+        relative = source_file.relative_to(src)
+        if relative == Path("index.md") and not include_index:
+            skipped += 1
+            continue
+        target_file = dst / relative
+        target_file.parent.mkdir(parents=True, exist_ok=True)
+
+        if target_file.exists() and not overwrite:
+            skipped += 1
+            continue
+
+        shutil.copy2(source_file, target_file)
+        copied += 1
+
+    return copied, skipped
+
+
+def main() -> int:
+    parser = argparse.ArgumentParser(description="Install .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(
+        "--without-index",
+        action="store_true",
+        help="Do not copy design/index.md when the caller owns the project design index",
+    )
+    args = parser.parse_args()
+
+    skill_root = Path(__file__).resolve().parents[1]
+    source = skill_root / "assets" / "design"
+    target_root = Path(args.target).resolve()
+    target = target_root / ".context" / "spec" / "design"
+
+    if not source.exists():
+        raise SystemExit(f"Source design rule pack not found: {source}")
+
+    copied, skipped = copy_tree(source, target, args.overwrite, not args.without_index)
+
+    print(f"Installed design rule pack into: {target}")
+    print(f"Copied files: {copied}")
+    print(f"Skipped existing files: {skipped}")
+    if skipped and not args.overwrite:
+        print("Run with --overwrite to replace existing files intentionally.")
+
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

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

@@ -0,0 +1,370 @@
+---
+name: workflow-feature-breakdown
+description: "Use when a requirement baseline needs a test-readable feature breakdown across style, functionality, logic, pages, components, fields, actions, and dialogs."
+---
+
+## Legacy Command Metadata
+
+Original slash-command metadata retained only as workflow invocation guidance.
+
+```yaml
+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
+allowed-tools:
+- Read
+- Write
+- Bash
+- Grep
+- Glob
+- ask
+```
+
+# Feature Point Expansion
+
+This skill consumes the requirement baseline and creates a test-readable feature expansion document. Do not re-discuss requirements, generate technical plans, write code change lists, or create implementation tasks.
+
+## Outputs
+
+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`.
+
+Do not create by default:
+
+- `.planning/features/{功能名}/前端技术方案.md`
+- `.planning/features/{功能名}/后端技术方案.md`
+- `.planning/features/{功能名}/变更清单.md`
+- `.planning/requirements/baseline.md`
+
+## Argument Handling
+
+Parse `$ARGUMENTS` before reading files:
+
+- `<功能名>`: optional hint. When baseline exists, always use the baseline canonical 功能名 and output directory. If `$ARGUMENTS` provides a different name, record the mismatch in pending questions and do not change the output path.
+- `--auto`: do not ask for supplementary UI/interface documents. Mark missing style, enum, interface, or data-dictionary details as `待确认`.
+
+The canonical output directory must come from the baseline when available:
+
+```text
+.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.
+
+## Resource Loading
+
+Load bundled resources only when needed:
+
+- Read `references/writing-guide.md` before writing the three-dimensional descriptions.
+- Read `references/bug-rules.md` before expanding permissions, read-only fields, calculations, enums, and frontend/backend grouping.
+- Read `references/trace-integrity-guide.md` before expanding any migration, async job, notification, list/detail page, field replacement, permission, menu, external callback, or cross-codebase feature.
+- Read `skill://workflow-pipeline/references/slice-safety-guide.md` when baseline has a slice plan or the current feature has more than 8 FP.
+- Read `references/exception-checklist.md` when a feature involves user flows, payment, third-party callbacks, retries, async status, or data consistency.
+- Read `assets/output-template.md` before writing the final document.
+- Read `assets/admin-system-template.md` for backend/admin systems.
+- Read `assets/c-end-system-template.md` for consumer-facing flows.
+- Read `assets/api-service-template.md` for API/service-only features.
+
+## Phase 1 — Load Baseline And Context
+
+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
+
+The baseline is the source of truth. Use its:
+
+- 功能名称 and 功能名 / output directory
+- 当前执行切片 `SL-*` and slice plan
+- 当前功能切片中的 Feature points `FP-*`
+- 当前功能切片中的 Business rules `BR-*`
+- 当前功能切片中的 Boundary cases `BC-*`
+- `depends_on` 引用的历史 FP/BR/BC 详情（作为上下文、复用、兼容和约束来源，不默认展开为本轮范围）
+- Pending questions
+- Challenge review results and user decisions under `反向审视与用户拍板`
+- Scope control
+- Clarification and change log
+- Downstream input contract
+
+If baseline is missing, ask the user to run `workflow-requirement-baseline` first or provide an existing baseline path. Do not fall back to raw PRD parsing unless the user explicitly asks for it.
+
+Baseline section mapping:
+
+- `需求来源` -> source summary and canonical output directory.
+- `需求整理摘要` -> system shape and page/module grouping.
+- `当前功能切片` -> current scope. Expand only this section's current FP/BR/BC IDs.
+- `当前功能切片.跨功能依赖` -> `depends_on` historical context. Load referenced historical FP/BR/BC details, but do not generate standalone nodes for them unless the current slice explicitly modifies or impacts them.
+- `功能点拆解` and `功能点详情` -> lookup table for current slice and `depends_on` details.
+- `业务规则汇总` -> `逻辑` dimension only for current slice or referenced `depends_on` constraints.
+- `边界场景汇总` -> `功能` dimension exception and boundary handling for current slice or referenced `depends_on` constraints.
+- `代码现实对照` -> reuse/conflict/current-behavior context. Do not convert it into implementation tasks.
+- `与历史功能/里程碑的关联` -> compatibility, legacy behavior, milestone evidence, and affected-module notes.
+- `反向审视与用户拍板` -> confirmed conflict/reuse/priority/alternative decisions; pending decisions must not become confirmed UI or service nodes.
+- `下游输入契约` -> output directory and downstream consistency checks.
+- `待确认事项` -> pending questions; never treat as confirmed behavior.
+- `澄清与变更记录` -> source notes when an answer changed earlier requirements.
+- `范围控制` -> do not generate nodes for excluded or deferred scope.
+
+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.
+
+Current slice rule:
+
+- If `当前功能切片` exists, it is the only default expansion scope.
+- If `当前功能切片` contains a slice plan, expand only `3.0a 当前执行切片范围`. Deferred slices are context only and must appear in the "不纳入/暂不处理" table.
+- If the baseline is an older format without `当前功能切片`, derive scope from the canonical feature name/output directory and record the fallback in pending notes.
+- Never expand all historical FP/BR/BC merely because they are present in the cumulative baseline.
+- FP type must remain `新增` / `修改` / `影响`. Do not turn BR or BC rows into FP rows.
+
+## Phase 2 — Determine System Shape
+
+Classify each feature point into one or more output sections:
+
+- `后台`: admin, operation, management, configuration, review, data list, export, permission, audit, or internal workflow
+- `C端`: consumer page, user journey, mobile/web user flow, payment, registration, result page, or external-facing interaction
+- `API/服务`: non-UI capability. Include only when the requirement has no user-facing component; describe trigger, input/output, rule, status, and exception behavior instead of UI style.
+
+Only include sections that apply. Delete unused `后台`, `C端`, or `API/服务` sections from the final document, or mark them `不适用`; never leave template placeholders in unused sections.
+
+When a feature spans frontend and backend, place user-visible controls under `后台` or `C端`, and include backend-only logic in the component `逻辑` section only when the baseline explicitly supports it.
+
+## Phase 3 — Build Critical Trace Skeleton
+
+Before detailed three-dimensional expansion, create a concise trace skeleton for each current-slice FP. Keep it short; this section exists to prevent long leaf-node output from hiding broken chains.
+
+For every FP, record:
+
+- User/business outcome
+- Actor or system trigger
+- Entry point or caller
+- Write model / state changed
+- Read model / downstream consumer
+- State transition or side effect
+- Primary exception/idempotency rule
+- Affected codebases
+- Test anchor
+
+Use `references/trace-integrity-guide.md` to add a chain matrix for high-risk FPs:
+
+- Migration from an old system
+- Async job, scheduled task, callback, polling, or external platform side effect
+- Notification, message center, homepage entry, or menu route
+- Field/source replacement such as old field -> new field
+- List/detail page migration with old entry parameters
+- Permission or visibility rule
+- Cross-codebase contract between backend, admin frontend, and mobile app
+
+Rules:
+
+- If a high-risk FP cannot produce a complete chain matrix from baseline and code reality, mark the missing seam as `阻塞待确认` or `接口/数据待确认`; do not bury it in fine-grained UI nodes.
+- Do not expand broad placeholder modules into detailed CRUD nodes unless baseline explicitly confirms they are in this slice. Keep them as `范围占位` with source and downstream owner.
+- For “整体迁移” scope, identify old runtime seams that must disappear and true external-platform seams that may remain.
+- Preserve the active `SL-*` on trace cards and nodes. If a node belongs to a deferred slice, remove it from implementation scope and list it under out-of-scope/deferred.
+
+## Phase 3.5 — Expand Into Testable Nodes
+
+For each current-slice `FP-*`, expand from feature capability into the smallest testable UI or behavior nodes.
+
+Before writing nodes, use the examples in `references/writing-guide.md` as the required splitting pattern. In particular, apply its examples for:
+
+- filter areas: split every input, selector, date range, and action button into separate nodes
+- tables: split table-level behavior, every visible column, and every operation button
+- dialogs/forms: split dialog shell, every field, and every confirm/cancel/action button
+- buttons: give each button its own style and function nodes
+
+Use this hierarchy when applicable:
+
+```text
+# {功能名称}
+- 后台 / C端 / API/服务
+  - 页面或模块
+    - 页面区域
+      - 组件/字段/按钮/表格列/弹窗/流程节点
+        - 样式
+        - 功能
+        - 逻辑（可选）
+```
+
+Expansion rules:
+
+- Keep the original `FP-*`, `BR-*`, and `BC-*` references on relevant nodes by appending IDs to the node title, e.g. `按钮:确定 (FP-001/BR-002)`. Do not add a separate child line like `来源：FP-001`, because that pollutes the Xmind tree.
+- Keep related `CR-*` references when a node exists because of a conflict, reuse, over-engineering, history, or alternative-path decision.
+- Split filters into individual inputs, selectors, date ranges, and action buttons.
+- Split tables into table-level behavior, each visible column, and each operation button.
+- Split forms and dialogs into dialog shell, every field, and every action button.
+- Split consumer flows into entry, authorization, core action path, result states, cancellation, timeout, retry, and failure states when applicable.
+- For API/service-only requirements, split by trigger, input validation, rule execution, state change, output, idempotency, retry, and failure handling.
+- Do not aggregate lists of fields into one node when each field has different display, validation, source, or logic.
+- Preserve the Phase 3 trace skeleton while expanding nodes. If a leaf node contradicts or skips a skeleton seam, fix the skeleton or mark the gap before continuing.
+
+## Phase 4 — Write Three Dimensions
+
+Every leaf node must include:
+
+- `样式`: visible text, position, component type, display format, empty state, read-only display, or `UI待确认`
+- `功能`: user action, system response, validation, permission behavior, loading state, duplicate submission handling, exception handling
+- `逻辑`: only when baseline provides business rules, calculations, status mappings, data sources, compatibility, or state transitions
+
+Rules:
+
+- Follow `references/writing-guide.md` examples for how to phrase style/function/logic under each component. If a generated node aggregates multiple fields, columns, or buttons into one description, split it before continuing.
+- Unauthorized operation buttons are not displayed, unless baseline explicitly says otherwise.
+- Fields are read-only unless baseline explicitly says they are editable.
+- Calculations, amount signs, statistics, status transitions, and compatibility rules must cite baseline source. If missing, mark `待确认`.
+- Dropdowns and status options must list concrete enum values. If missing, mark `枚举待确认`.
+- Do not create business rules from UI guesses.
+
+## Phase 4.5 — 信息精简检查
+
+目标的：在进入 gap 处理之前，对已经展开的三维节点做一轮"必须性"检查，减少不必要的信息噪声。
+
+对着每个叶节点的 `样式` 和 `功能` 中的每项信息，问自己：
+
+| 检查 | 条件 | 处理 |
+|------|------|------|
+| 这个信息用户需要吗？ | 用户看到它时能据此决策或行动吗？ | 否→标记为"冗余，建议删除" |
+| 去掉影响决策吗？ | 如果去掉，用户能否完成核心任务？ | 不影响→标记为"非必要，建议移除" |
+| 能不能合并？ | 两个信息项内容相近或同时出现？ | 是→建议合并为一项 |
+| 是不是后台技术细节？ | 字段值/状态/日志等对用户无意义的信息 | 是→标记为"仅内部可见" |
+
+只对**面向用户展示的节点**做此检查（后台 / C 端的页面、组件、字段、列），不对 API/服务类的输出做此检查。
+
+如果发现可精简的项，在展开节点中标注 `精简建议: [删除/合并/降级]` 和原因。不直接删减，让下游（PM 或用户）拍板。
+
+## Phase 5 — Handle Gaps
+
+This skill should not restart workflow-requirement-baseline work.
+
+Ask only when a gap blocks a useful feature expansion, and ask one question at a time. After each user answer:
+
+1. Check whether the answer changes the baseline assumptions, feature points, rules, boundary cases, scope, or output directory.
+2. If it changes baseline-level requirements, stop and tell the user the baseline should be updated by `workflow-requirement-baseline` before continuing.
+3. If it only adds presentation detail for this document, apply it and record it in the feature expansion notes.
+
+In `--auto` mode, do not ask. Mark gaps as `待确认` in the output.
+
+Pending classification:
+
+- `阻塞待确认`: cannot produce a useful feature expansion without this answer.
+- `非阻塞待确认`: document can be generated, but downstream technical docs or tests need confirmation.
+- `UI待确认`: affects only visual layout, wording, or component choice.
+- `枚举待确认`: affects dropdown/status values or validation test cases.
+- `接口/数据待确认`: affects field source, API response, persistence, or data dictionary.
+
+If stopping because a user answer changes baseline-level requirements, report:
+
+- Source question and answer summary
+- Affected `FP-*`, `BR-*`, `BC-*`, scope item, or output directory
+- Why the baseline must be updated first
+- Recommended next action: rerun or resume `workflow-requirement-baseline`
+
+## Phase 6 — Generate Document
+
+Read `assets/output-template.md`.
+
+Create `.planning/features/{功能名}/` if needed and write `.planning/features/{功能名}/功能点梳理.md`.
+
+The document must include:
+
+1. Source summary: baseline path, feature name, output directory, generation date
+2. Scope summary: active Slice ID, included FP/BR/BC IDs, and excluded/deferred items
+3. Three-dimensional hierarchy by `后台`, `C端`, and/or `API/服务`
+4. Critical trace skeleton and high-risk chain matrices
+5. Pending UI/interface/data questions
+6. Traceability table mapping output sections back to FP/BR/BC IDs
+7. Challenge decision traceability mapping output sections back to confirmed `CR-*` decisions
+8. Trace-integrity review result
+9. Self-review result
+
+## Phase 7 — Review Gate (MANDATORY — do not skip)
+
+**审查方法论：baseline → 功能点梳理的展开审查，沿用 spec-writer 反问 + 反向对照模式。**
+
+### 7.1 反问审查（覆盖完整性）
+
+对当前功能切片的每个 FP 自查，发现缺失时回查 baseline 或标记为待确认：
+
+- 这个 FP 的三维展开（样式/功能/逻辑）是否完整？
+- 涉及的页面、组件、字段、按钮、列、弹窗是否均已列明？
+- 权限/状态/校验/计算是否均来自 baseline 规则，未捏造假设？
+
+### 7.2 反向对照审查（代码库对照）
+
+用 4 个嗅探检查展开后功能点与现有代码的关系：
+
+| 嗅探 | 检查 |
+|------|------|
+| 复用嗅探 | 梳理中涉及的页面/组件/接口，是否已有现成实现可复用？ |
+| 冲突嗅探 | 新增的页面路由、API 路径、组件命名是否与现有约定冲突？ |
+| 重叠嗅探 | 梳理的功能是否会与某个已有功能形成"两套并存"？ |
+| 历史嗅探 | `features/` 中是否有类似功能曾被做过？ |
+
+若 `.planning/code-index/` 存在，复用/冲突/重叠嗅探应优先查询 symbols/relations，再回读源码 evidence；缺失或过期时再用 navigation 和 `rg` 兜底。
+
+### 7.2a 链路完整性审查（MANDATORY）
+
+Read `references/trace-integrity-guide.md` and run the applicable chain gates. At minimum, check:
+
+- 写入点与读取点是否闭合：通知、消息、列表、卡片、详情使用同一真实数据流。
+- 调用方矩阵是否完整：字段/契约替换覆盖所有旧入口、新入口、校验、DTO、落库、执行链路。
+- 异步链路是否闭合：入口、命令、注册、数据库 seed、执行频率、运行状态、监控字段均有验收锚点。
+- 迁移链路是否闭合：旧系统页面入口参数、数据主表、操作列、运行时依赖移除均已写清。
+- 记录/任务/计划概念是否分清：平台作业记录和 CRM 业务记录不能混表。
+- 权限/菜单是否可达：页面文件、动态菜单/权限、首页或消息直达入口、本地或灰度兜底均有处理。
+- 外部调用是否幂等：重复回调、重复轮询、重复分析不会清空已有字段或重复消耗外部资源。
+
+If a gate applies but the output lacks a corresponding node, pending question, or out-of-scope statement, the review must fail.
+
+### 7.3 产物完整性检查
+
+```markdown
+- [ ] 每个当前切片 FP 均已展开或标记 out-of-scope
+- [ ] 当前 Slice ID 已写入范围摘要、链路骨架和追溯表
+- [ ] 未展开后置切片实现范围
+- [ ] 与 baseline 分片覆盖守恒一致：active FP 全部展开；deferred/out-of-scope FP 全部列入不纳入/暂不处理；无未解释缺口
+- [ ] 每个叶子节点有 样式 + 功能（逻辑仅在有规则/数据源时出现）
+- [ ] 权限使用 `不显示`（非删除/禁用），只读/可编辑不捏造
+- [ ] 下拉/状态值具体或标记待确认，计算/统计引用来源
+- [ ] 前后端/C端分组符合 baseline
+- [ ] 高风险 FP 已生成关键链路骨架和适用链路矩阵
+- [ ] 写入点/读取点、调用方矩阵、异步 seed、迁移运行时、记录模型、权限菜单、外部幂等等适用门禁已检查
+- [ ] 不存在 `阻塞待确认`
+- [ ] 不含技术方案、DDL、接口设计、代码任务
+```
+
+### 7.4 审查结论
+
+在 `功能点梳理.md` 末尾写入审查结论（通过 / 不通过 + 未通过项）。
+
+审查结论必须为 `不通过` when:
+
+- Any `阻塞待确认` remains.
+- Any current-slice FP is not expanded and not explicitly out of scope.
+- Any leaf node lacks `样式` or `功能`.
+- A node writes unconfirmed BR/BC/pending information as fact.
+- Any applicable trace-integrity gate has no output node, pending item, or explicit non-applicable reason.
+- Slice coverage does not balance against baseline active/deferred/out-of-scope counts.
+
+**Do not report "Step 3a complete" to the pipeline until 审查结论 = 通过.**

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

@@ -0,0 +1,57 @@
+# 后台系统层级模板
+
+```
+# 项目名称
+- 后台
+  - 一级菜单
+    - 二级菜单（页面）
+      - 页面头部
+        - 标题文案
+        - 新增按钮
+          - 样式
+          - 功能
+          - 逻辑（可选）
+        - 导出按钮
+          - 样式
+          - 功能
+          - 逻辑（可选）
+      - 筛选区
+        - 筛选条件组
+          - 字段A输入框
+            - 样式
+            - 功能
+            - 逻辑（可选）
+          - 字段B下拉选择
+            - 样式
+            - 功能
+            - 逻辑（可选）
+        - 操作按钮组
+          - 查询按钮
+          - 重置按钮
+      - 数据汇总区（可选）
+        - 汇总指标A
+          - 样式
+          - 功能
+          - 逻辑
+      - 列表区（表格）
+        - 表格整体
+          - 样式
+          - 功能
+        - 列:字段A
+          - 样式
+          - 功能
+          - 逻辑（可选）
+        - 列:字段B
+          - 样式
+          - 功能
+          - 逻辑（可选）
+        - 列:操作
+          - 编辑按钮
+          - 删除按钮
+      - 新增/编辑弹窗
+        - 弹窗整体
+        - 表单字段:字段A
+        - 表单字段:字段B
+        - 按钮:确定
+        - 按钮:取消
+```

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

@@ -0,0 +1,42 @@
+# API/服务能力层级模板
+
+```text
+# 项目名称
+- API/服务
+  - 服务能力或任务名称
+    - 触发方式
+      - 样式
+        - 不适用：非 UI 能力
+      - 功能
+        - 说明由接口调用、定时任务、消息、回调或人工触发
+      - 逻辑
+        - 触发条件来自 baseline 对应 FP/BR
+    - 输入与校验
+      - 样式
+        - 不适用：非 UI 能力
+      - 功能
+        - 校验必填、格式、权限、重复请求、非法状态
+      - 逻辑
+        - 字段来源、枚举值、校验规则
+    - 处理规则
+      - 样式
+        - 不适用：非 UI 能力
+      - 功能
+        - 执行业务规则并返回处理结果
+      - 逻辑
+        - 计算、状态流转、兼容旧数据、幂等规则
+    - 输出与状态
+      - 样式
+        - 不适用：非 UI 能力
+      - 功能
+        - 返回成功、失败、部分成功、处理中等结果
+      - 逻辑
+        - 状态映射、数据落库、事件发布
+    - 异常与重试
+      - 样式
+        - 不适用：非 UI 能力
+      - 功能
+        - 超时、回调失败、第三方失败、重试、补偿、告警
+      - 逻辑
+        - 重试次数、幂等键、补偿条件；无来源则标记待确认
+```

package/plugins/devflow-design/skills/workflow-feature-breakdown/assets/c-end-system-template.md

@@ -0,0 +1,25 @@
+# C端系统层级模板
+
+```
+# 项目名称
+- C端
+  - 页面名称
+    - 页面头部
+      - 标题区
+      - 返回按钮
+    - 内容区
+      - 功能模块A
+        - UI组件1
+          - 样式
+          - 功能
+          - 逻辑（可选）
+        - UI组件2
+          - 样式
+          - 功能
+          - 逻辑（可选）
+    - 底部操作区
+      - 提交按钮
+        - 样式
+        - 功能
+        - 逻辑（可选）
+```