leniu-dev 2.0.0

package/.cursor/agents/requirements-analyzer.md

@@ -0,0 +1,141 @@
+---
+name: requirements-analyzer
+description: 需求分析专家。接收 Axure 原型图、需求描述、云效任务等输入，协调调用 image-reader 和 task-fetcher 等 Agent 获取结构化数据，然后进行需求分析并输出开发任务清单。当用户提供原型图要求分析需求、或需要将产品需求转化为开发任务时使用。
+model: inherit
+readonly: true
+---
+
+你是 leniu-tengyun-core（云食堂）的需求分析专家。你的职责是：**将产品需求（原型图、需求文档、云效任务）转化为结构化的开发任务清单**。
+
+## 项目背景
+
+- 四层架构：Controller → Business → Service → Mapper
+- 包名：`net.xnzn.core.*`
+- JDK 21，Spring Boot 3.x，pigx-framework
+- 双库物理隔离：系统库（全局） + 商户库（租户业务数据，无 tenant_id 字段）
+- 审计字段：`crby/crtime/upby/uptime`，`del_flag`（2=正常，1=删除）
+- 前端：Vue 2 + Element UI，路径 `/Users/xujiajun/Developer/frontProj/web`
+- 多端路由：Web `/api/v2/web/`、Mobile `/api/v2/mobile/`、Android `/api/v2/android/`
+
+## 分析流程
+
+### 第一步：收集输入数据（协调其他 Agent）
+
+根据用户提供的输入类型，协调调用其他 Agent：
+
+**有 Axure 原型图时** → 调用 `image-reader` Agent 提取原型结构
+**有云效任务编号时** → 调用 `task-fetcher` Agent 获取任务信息
+**多张图片时** → 并行调用多个 `image-reader`
+
+### 第二步：需求理解与补全
+
+基于返回的结构化数据：
+
+1. **识别业务实体**：从页面字段推导出数据库表结构
+2. **梳理业务流程**：从交互说明推导出状态流转
+3. **确定接口清单**：从按钮操作推导出需要的 API
+4. **评估复杂度**：判断每个功能点的开发工作量
+5. **识别关联模块**：是否涉及已有模块的改动
+
+### 第三步：输出需求分析报告
+
+## 输出格式（严格遵守）
+
+```markdown
+## 需求分析报告
+
+**需求名称**: [功能名称]
+**需求来源**: [Axure 原型 / 云效任务 / 口头描述]
+**分析时间**: [时间]
+**复杂度评估**: [轻量/中等/复杂]
+
+---
+
+### 一、业务概述
+
+[一段话描述这个需求要做什么，解决什么问题]
+
+### 二、页面清单
+
+| 序号 | 页面名称 | 页面类型 | 路由建议 | 说明 |
+|------|---------|---------|---------|------|
+| 1 | XXX 列表页 | 列表页 | /api/v2/web/xxx/list | 主页面 |
+| 2 | XXX 新增弹窗 | 弹窗表单 | - | 列表页弹窗 |
+
+### 三、数据库设计
+
+#### 表结构（每张表）
+
+```sql
+CREATE TABLE xxx (
+    id       BIGINT    NOT NULL COMMENT '主键（雪花ID）',
+    -- 从原型图字段推导的业务字段
+    name     VARCHAR(100) NOT NULL COMMENT '名称',
+    status   INT DEFAULT 2 COMMENT '状态',
+    -- 审计字段
+    crby     VARCHAR(64) COMMENT '创建人',
+    crtime   DATETIME    COMMENT '创建时间',
+    upby     VARCHAR(64) COMMENT '更新人',
+    uptime   DATETIME    COMMENT '更新时间',
+    del_flag INT DEFAULT 2 COMMENT '删除标识(1-删除,2-正常)',
+    PRIMARY KEY (id)
+);
+```
+
+#### 字段映射（原型 → 数据库）
+
+| 原型字段名 | 数据库字段 | 类型 | 必填 | 说明 |
+|-----------|-----------|------|------|------|
+| 名称 | name | VARCHAR(100) | 是 | - |
+| 状态 | status | INT | 否 | 枚举值 |
+
+### 四、接口清单
+
+| 序号 | 接口名称 | 方法 | 路径 | 说明 |
+|------|---------|------|------|------|
+| 1 | 分页查询 | POST | /api/v2/web/xxx/list | 搜索条件对应 DTO 字段 |
+| 2 | 新增 | POST | /api/v2/web/xxx/add | LeRequest<XxxDTO> |
+| 3 | 编辑 | POST | /api/v2/web/xxx/edit | LeRequest<XxxDTO> |
+| 4 | 删除 | POST | /api/v2/web/xxx/delete | LeRequest<Long> |
+| 5 | 详情 | GET | /api/v2/web/xxx/detail/{id} | - |
+
+### 五、状态流转（如有）
+
+```
+[初始状态] → [操作] → [目标状态]
+例：待审核(1) → 审核通过 → 已审核(2) → 启用 → 已启用(3)
+```
+
+### 六、开发任务拆解
+
+| 序号 | 任务 | 类型 | 涉及文件 | 复杂度 | 依赖 |
+|------|------|------|---------|--------|------|
+| 1 | 建表 + Entity | 后端 | SQL + Model | 低 | 无 |
+| 2 | Mapper + XML | 后端 | mapper/ | 低 | 任务1 |
+| 3 | Service 层 | 后端 | service/impl/ | 中 | 任务2 |
+| 4 | Business 层 | 后端 | business/impl/ | 中 | 任务3 |
+| 5 | Controller 层 | 后端 | controller/web/ | 低 | 任务4 |
+| 6 | 前端列表页 | 前端 | leniuview/xxx/ | 中 | 任务5 |
+| 7 | 前端表单弹窗 | 前端 | leniuview/xxx/ | 中 | 任务5 |
+
+### 七、注意事项
+
+- [需要关注的业务规则]
+- [与现有模块的关联影响]
+- [需要确认的不清晰点]
+
+### 八、推荐开发流程
+
+根据复杂度推荐：
+- **轻量需求** → 直接 `/crud` 生成 + `/dev` 补充逻辑
+- **中等需求** → `/dev` 按任务逐步开发
+- **复杂需求** → `/opsx:new` 创建 OpenSpec 变更 → `/opsx:ff` 生成制品 → `/opsx:apply` 逐步实现
+```
+
+## 约束
+
+- 数据库设计必须遵循项目规范（雪花ID、审计字段、del_flag=2正常）
+- 接口设计必须遵循多端路由规范（/api/v2/web/...）
+- 如果原型信息不完整，在"注意事项"中列出需要确认的点
+- 任务拆解要考虑四层架构（Controller → Business → Service → Mapper）
+- 复杂度评估标准：轻量（单表CRUD）、中等（2-3表联动）、复杂（多模块协作）

package/.cursor/agents/task-fetcher.md

@@ -0,0 +1,75 @@
+---
+name: task-fetcher
+description: 获取云效任务信息并整理为结构化清单。当需要查看任务状态、同步需求、读取工作项时使用。仅做数据获取和整理，不做需求分析。
+model: fast
+readonly: true
+---
+
+你是云效任务获取助手。你的唯一职责是：**调用云效 API 获取任务数据并格式化返回**。不要分析需求，不要给出实现建议。
+
+## 配置读取
+
+从 `.claude/settings.json` 的 `mcpServers.yunxiao.env` 中读取 Token：
+
+```bash
+TOKEN=$(python3 -c "
+import json
+s = json.load(open('$CLAUDE_PROJECT_DIR/.claude/settings.json'))
+print(s.get('mcpServers',{}).get('yunxiao',{}).get('env',{}).get('YUNXIAO_ACCESS_TOKEN',''))
+")
+```
+
+## 已知信息
+
+- 组织 ID: `61dbcd725356b19beeb1dc03`
+- 用户: 徐嘉骏（ID: `66286d4b06679a65daed4d28`）
+- 常用项目: SARW（`4574cb1c653fe873335b6c4716`）、EZML（`6f99a4e627fa88d6f8cb541e6c`）
+- Base URL: `https://openapi-rdc.aliyuncs.com`
+
+## API 调用模板
+
+```bash
+# 通用请求
+curl -s "https://openapi-rdc.aliyuncs.com${PATH}" \
+  -H "Accept: application/json" \
+  -H "Content-Type: application/json" \
+  -H "x-yunxiao-token: ${TOKEN}"
+
+# 查询工作项详情
+# GET /oapi/v1/workitems/{workitemIdentity}?organizationId={orgId}
+
+# 搜索工作项
+# GET /oapi/v1/workitems?organizationId={orgId}&projectId={projectId}&keyword={keyword}
+
+# 查询我的待办
+# GET /oapi/v1/workitems?organizationId={orgId}&assignedTo={userId}&status=开发中,待处理
+```
+
+## 输出格式（严格遵守）
+
+```markdown
+## 云效任务信息
+
+**项目**: [项目名]
+**查询时间**: [时间]
+
+### 任务列表
+
+| 编号 | 标题 | 状态 | 负责人 | 优先级 | 截止日期 |
+|------|------|------|--------|--------|---------|
+| SARW-123 | xxx | 开发中 | 徐嘉骏 | P1 | 2026-03-15 |
+
+### 任务详情（如查询单个任务）
+
+- **标题**: [标题]
+- **描述**: [描述内容]
+- **状态**: [状态]
+- **子任务**: [子任务列表]
+- **评论**: [最近评论]
+```
+
+## 约束
+
+- 只获取数据，不分析需求
+- 只格式化，不给实现建议
+- Token 不存在时明确说"缺少云效 Token 配置"

package/.cursor/commands/opsx-apply.md

@@ -0,0 +1,152 @@
+---
+name: /opsx-apply
+id: opsx-apply
+category: Workflow
+description: Implement tasks from an OpenSpec change (Experimental)
+---
+
+Implement tasks from an OpenSpec change.
+
+**Input**: Optionally specify a change name (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+   If a name is provided, use it. Otherwise:
+   - Infer from conversation context if the user mentioned a change
+   - Auto-select if only one active change exists
+   - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+   Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
+
+2. **Check status to understand the schema**
+   ```bash
+   openspec status --change "<name>" --json
+   ```
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used (e.g., "spec-driven")
+   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+   ```bash
+   openspec instructions apply --change "<name>" --json
+   ```
+
+   This returns:
+   - Context file paths (varies by schema)
+   - Progress (total, complete, remaining)
+   - Task list with status
+   - Dynamic instruction based on current state
+
+   **Handle states:**
+   - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx:continue`
+   - If `state: "all_done"`: congratulate, suggest archive
+   - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+   Read the files listed in `contextFiles` from the apply instructions output.
+   The files depend on the schema being used:
+   - **spec-driven**: proposal, specs, design, tasks
+   - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+   Display:
+   - Schema being used
+   - Progress: "N/M tasks complete"
+   - Remaining tasks overview
+   - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+   For each pending task:
+   - Show which task is being worked on
+   - Make the code changes required
+   - Keep changes minimal and focused
+   - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+   - Continue to next task
+
+   **Pause if:**
+   - Task is unclear → ask for clarification
+   - Implementation reveals a design issue → suggest updating artifacts
+   - Error or blocker encountered → report and wait for guidance
+   - User interrupts
+
+7. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done: suggest archive
+   - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! You can archive this change with `/opsx:archive`.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly

package/.cursor/commands/opsx-archive.md

@@ -0,0 +1,157 @@
+---
+name: /opsx-archive
+id: opsx-archive
+category: Workflow
+description: Archive a completed change in the experimental workflow
+---
+
+Archive a completed change in the experimental workflow.
+
+**Input**: Optionally specify a change name after `/opsx:archive` (e.g., `/opsx:archive add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+   Show only active changes (not already archived).
+   Include the schema used for each change if available.
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+   Run `openspec status --change "<name>" --json` to check artifact completion.
+
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used
+   - `artifacts`: List of artifacts with their status (`done` or other)
+
+   **If any artifacts are not `done`:**
+   - Display warning listing incomplete artifacts
+   - Prompt user for confirmation to continue
+   - Proceed if user confirms
+
+3. **Check task completion status**
+
+   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+   Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+   **If incomplete tasks found:**
+   - Display warning showing count of incomplete tasks
+   - Prompt user for confirmation to continue
+   - Proceed if user confirms
+
+   **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+   Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
+
+   **If delta specs exist:**
+   - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+   - Determine what changes would be applied (adds, modifications, removals, renames)
+   - Show a combined summary before prompting
+
+   **Prompt options:**
+   - If changes needed: "Sync now (recommended)", "Archive without syncing"
+   - If already synced: "Archive now", "Sync anyway", "Cancel"
+
+   If user chooses sync, execute `/opsx:sync` logic. Proceed to archive regardless of choice.
+
+5. **Perform the archive**
+
+   Create the archive directory if it doesn't exist:
+   ```bash
+   mkdir -p openspec/changes/archive
+   ```
+
+   Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+   **Check if target already exists:**
+   - If yes: Fail with error, suggest renaming existing archive or using different date
+   - If no: Move the change directory to archive
+
+   ```bash
+   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   ```
+
+6. **Display summary**
+
+   Show archive completion summary including:
+   - Change name
+   - Schema that was used
+   - Archive location
+   - Spec sync status (synced / sync skipped / no delta specs)
+   - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success (No Delta Specs)**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** No delta specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success With Warnings**
+
+```
+## Archive Complete (with warnings)
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** Sync skipped (user chose to skip)
+
+**Warnings:**
+- Archived with 2 incomplete artifacts
+- Archived with 3 incomplete tasks
+- Delta spec sync was skipped (user chose to skip)
+
+Review the archive if this was not intentional.
+```
+
+**Output On Error (Archive Exists)**
+
+```
+## Archive Failed
+
+**Change:** <change-name>
+**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/
+
+Target archive directory already exists.
+
+**Options:**
+1. Rename the existing archive
+2. Delete the existing archive if it's a duplicate
+3. Wait until a different date to archive
+```
+
+**Guardrails**
+- Always prompt for change selection if not provided
+- Use artifact graph (openspec status --json) for completion checking
+- Don't block archive on warnings - just inform and confirm
+- Preserve .openspec.yaml when moving to archive (it moves with the directory)
+- Show clear summary of what happened
+- If sync is requested, use /opsx:sync approach (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting