zcf 3.4.3 → 3.5.1

package/dist/cli.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import cac from 'cac';
 import ansis from 'ansis';
-import { ak as ensureI18nInitialized, al as i18n, aO as readCcrConfig, aJ as isCcrInstalled, aK as installCcr, aP as configureCcrFeature, ao as promptBoolean, aQ as handleExitPromptError, aR as handleGeneralError, aS as COMETIX_COMMAND_NAME, aT as COMETIX_COMMANDS, aU as installCometixLine, am as addNumbersToChoices, aV as checkAndUpdateTools, aW as runCodexUpdate, aX as resolveCodeType$1, at as readJsonConfig, aY as writeJsonConfig, q as ZCF_CONFIG_FILE, aE as readZcfConfig, D as DEFAULT_CODE_TOOL_TYPE, u as isCodeToolType, aZ as displayBanner, aC as updateZcfConfig, a_ as version, a$ as resolveAiOutputLanguage, b0 as updatePromptOnly, b1 as selectAndInstallWorkflows, b2 as checkClaudeCodeVersionAndPrompt, w as resolveCodeToolType$1, b3 as displayBannerWithInfo, s as CODE_TOOL_BANNERS, b4 as runCodexUninstall, b5 as configureCodexMcp, b6 as configureCodexApi, b7 as runCodexWorkflowImportWithLanguageSelection, b8 as runCodexFullInit, i as init, b9 as switchCodexProvider, ba as listCodexProviders, ay as readCodexConfig, bb as switchToOfficialLogin, bc as switchToProvider, bd as readZcfConfigAsync, be as initI18n, bf as selectScriptLanguage, aD as changeLanguage } from './chunks/simple-config.mjs';
+import { ak as ensureI18nInitialized, al as i18n, aN as readCcrConfig, aI as isCcrInstalled, aJ as installCcr, aO as configureCcrFeature, ao as promptBoolean, aP as handleExitPromptError, aQ as handleGeneralError, aR as COMETIX_COMMAND_NAME, aS as COMETIX_COMMANDS, aT as installCometixLine, am as addNumbersToChoices, aU as checkAndUpdateTools, aV as runCodexUpdate, aW as resolveCodeType$1, at as readJsonConfig, aX as writeJsonConfig, q as ZCF_CONFIG_FILE, aD as readZcfConfig, D as DEFAULT_CODE_TOOL_TYPE, u as isCodeToolType, aY as displayBanner, aB as updateZcfConfig, aZ as version, a_ as resolveAiOutputLanguage, a$ as updatePromptOnly, b0 as selectAndInstallWorkflows, b1 as checkClaudeCodeVersionAndPrompt, w as resolveCodeToolType$1, b2 as displayBannerWithInfo, s as CODE_TOOL_BANNERS, b3 as runCodexUninstall, b4 as configureCodexMcp, b5 as configureCodexApi, b6 as runCodexWorkflowImportWithLanguageSelection, b7 as runCodexFullInit, i as init, b8 as switchCodexProvider, b9 as listCodexProviders, ay as readCodexConfig, ba as switchToOfficialLogin, bb as switchToProvider, bc as readZcfConfigAsync, bd as initI18n, be as selectScriptLanguage, aC as changeLanguage } from './chunks/simple-config.mjs';
 import { existsSync } from 'node:fs';
 import { homedir } from 'node:os';
 import inquirer from 'inquirer';
@@ -20,7 +20,7 @@ import 'node:url';
 import 'inquirer-toggle';
 import 'ora';
 import 'semver';
-import 'smol-toml';
+import '@rainbowatcher/toml-edit-js';
 import 'node:fs/promises';
 import 'i18next';
 import 'i18next-fs-backend';
@@ -1193,7 +1193,7 @@ async function update(options = {}) {
       }
       return;
     }
-    const { resolveTemplateLanguage } = await import('./chunks/simple-config.mjs').then(function (n) { return n.bm; });
+    const { resolveTemplateLanguage } = await import('./chunks/simple-config.mjs').then(function (n) { return n.bl; });
     const configLang = await resolveTemplateLanguage(
       options.configLang,
       // Command line option

package/dist/i18n/locales/en/codex.json

@@ -80,7 +80,7 @@
   "copyingProvider": "Copying provider: {{name}}",
   "providerCopied": "✔ Successfully copied provider: {{name}}",
   "providerCopyFailed": "❌ Failed to copy provider: {{error}}",
-  "providerModelPrompt": "Model name (e.g. gpt-5-codex)",
+  "providerModelPrompt": "Model name (e.g. gpt-5.2)",
   "providerModelRequired": "Model name is required",
   "selectProvidersToDelete": "Select providers to delete (multiple)",
   "selectAtLeastOne": "Please select at least one provider",

package/dist/i18n/locales/en/configuration.json

@@ -70,8 +70,9 @@
   "updatingPrompts": "Updating Claude Code memory documents...",
   "enterCustomModel": "Enter custom model name",
   "systemPromptConfigured": "System prompt style configured",
-  "codexModelOptions.gpt5": "GPT-5 - General powerful model, suitable for complex tasks",
-  "codexModelOptions.gpt5Codex": "GPT-5-Codex - Code-optimized model, recommended for programming tasks",
+  "codexModelOptions.gpt51CodexMax": "GPT-5.1-Codex-Max - Codex-optimized flagship for deep and fast reasoning",
+  "codexModelOptions.gpt51CodexMini": "GPT-5.1-Codex-Mini - Optimized for codex. Cheaper, faster, but less capable",
+  "codexModelOptions.gpt52": "GPT-5.2 - Latest frontier model with improvements across knowledge, reasoning and coding (Recommended)",
   "codexModelOptions.custom": "Custom - Specify custom model names",
   "windowsMcpConfigFixed": "Windows MCP configuration fixed"
 }

package/dist/i18n/locales/en/menu.json

@@ -41,7 +41,7 @@
   "menuDescriptions.codexImportWorkflow": "Import/update Codex workflow-related files",
   "menuDescriptions.codexConfigureApi": "Configure Codex API providers",
   "menuDescriptions.codexConfigureMcp": "Configure Codex MCP services",
-  "menuDescriptions.codexConfigureModel": "Set default model (gpt-5/gpt-5-codex/custom)",
+  "menuDescriptions.codexConfigureModel": "Set default model (gpt-5.2/gpt-5.1-codex-max/gpt-5.1-codex-mini/custom)",
   "menuDescriptions.codexConfigureAiMemory": "Configure AI output language and system prompt style",
   "menuDescriptions.codexUninstall": "Remove Codex configuration and files",
   "menuDescriptions.codexCheckUpdates": "Check and update Codex",

package/dist/i18n/locales/zh-CN/codex.json

@@ -80,7 +80,7 @@
   "copyingProvider": "正在复制供应商：{{name}}",
   "providerCopied": "✔ 已成功复制供应商：{{name}}",
   "providerCopyFailed": "❌ 复制供应商失败：{{error}}",
-  "providerModelPrompt": "模型名称（如 gpt-5-codex）",
+  "providerModelPrompt": "模型名称（如 gpt-5.2）",
   "providerModelRequired": "必须填写模型名称",
   "selectProvidersToDelete": "选择要删除的供应商（多选）",
   "selectAtLeastOne": "请至少选择一个供应商",

package/dist/i18n/locales/zh-CN/configuration.json

@@ -70,8 +70,9 @@
   "updatingPrompts": "正在更新 Claude Code 记忆文档...",
   "enterCustomModel": "请输入自定义模型名称",
   "systemPromptConfigured": "系统提示词风格已配置",
-  "codexModelOptions.gpt5": "GPT-5 - 通用强力模型，适合复杂任务",
-  "codexModelOptions.gpt5Codex": "GPT-5-Codex - 专为代码优化的模型，推荐用于编程任务",
+  "codexModelOptions.gpt51CodexMax": "GPT-5.1-Codex-Max - Codex 优化旗舰模型，支持深度快速推理",
+  "codexModelOptions.gpt51CodexMini": "GPT-5.1-Codex-Mini - Codex 优化版，更便宜快速但能力稍弱",
+  "codexModelOptions.gpt52": "GPT-5.2 - 最新前沿模型，知识、推理和编码全面提升（推荐）",
   "codexModelOptions.custom": "自定义 - 指定自定义模型名称",
   "windowsMcpConfigFixed": "Windows MCP 配置已修复"
 }

package/dist/i18n/locales/zh-CN/menu.json

@@ -41,7 +41,7 @@
   "menuDescriptions.codexImportWorkflow": "仅导入/更新 Codex 工作流相关文件",
   "menuDescriptions.codexConfigureApi": "配置 Codex 的 API 提供商",
   "menuDescriptions.codexConfigureMcp": "配置 Codex 的 MCP 服务",
-  "menuDescriptions.codexConfigureModel": "设置默认模型（gpt-5/gpt-5-codex/自定义）",
+  "menuDescriptions.codexConfigureModel": "设置默认模型（gpt-5.2/gpt-5.1-codex-max/gpt-5.1-codex-mini/自定义）",
   "menuDescriptions.codexConfigureAiMemory": "配置 AI 输出语言和系统提示词风格",
   "menuDescriptions.codexUninstall": "删除 Codex 配置和相关文件",
   "menuDescriptions.codexCheckUpdates": "检查并更新 Codex",

package/dist/index.mjs

@@ -13,7 +13,7 @@ import 'inquirer-toggle';
 import 'ora';
 import 'tinyexec';
 import 'semver';
-import 'smol-toml';
+import '@rainbowatcher/toml-edit-js';
 import 'node:fs/promises';
 import 'i18next';
 import 'i18next-fs-backend';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "zcf",
   "type": "module",
-  "version": "3.4.3",
+  "version": "3.5.1",
   "description": "Zero-Config Code Flow - One-click configuration tool for Code Cli",
   "author": {
     "name": "Miao Da",
@@ -43,6 +43,7 @@
     "templates"
   ],
   "dependencies": {
+    "@rainbowatcher/toml-edit-js": "^0.6.4",
     "@types/semver": "^7.7.1",
     "ansis": "^4.1.0",
     "cac": "^6.7.14",
@@ -56,7 +57,6 @@
     "ora": "^9.0.0",
     "pathe": "^2.0.3",
     "semver": "^7.7.2",
-    "smol-toml": "^1.4.2",
     "tinyexec": "^1.0.1",
     "trash": "^10.0.0"
   },

package/templates/CLAUDE.md

@@ -1,6 +1,6 @@
 # Templates Module
 
-**Last Updated**: Mon Oct 27 19:39:26 CST 2025
+**Last Updated**: Sun Dec 15 09:15:34 CST 2025
 [Root](../CLAUDE.md) > **templates**
 
 ## Module Responsibilities
@@ -20,18 +20,43 @@ Template system module providing multilingual configuration templates, AI person
 
 ```
 templates/
+├── common/                   # Shared templates (cross code-tool)
+│   ├── output-styles/       # AI personality styles
+│   │   ├── en/              # English output styles
+│   │   │   ├── engineer-professional.md
+│   │   │   ├── laowang-engineer.md
+│   │   │   ├── nekomata-engineer.md
+│   │   │   └── ojousama-engineer.md
+│   │   └── zh-CN/           # Chinese output styles
+│   │       ├── engineer-professional.md
+│   │       ├── laowang-engineer.md
+│   │       ├── nekomata-engineer.md
+│   │       └── ojousama-engineer.md
+│   └── workflow/
+│       ├── git/             # Git workflow
+│       │   ├── en/          # English git commands
+│       │   │   ├── git-commit.md
+│       │   │   ├── git-worktree.md
+│       │   │   ├── git-cleanBranches.md
+│       │   │   └── git-rollback.md
+│       │   └── zh-CN/       # Chinese git commands
+│       │       ├── git-commit.md
+│       │       ├── git-worktree.md
+│       │       ├── git-cleanBranches.md
+│       │       └── git-rollback.md
+│       └── sixStep/         # Six-step workflow
+│           ├── en/          # English workflow
+│           │   └── workflow.md
+│           └── zh-CN/       # Chinese workflow
+│               └── workflow.md
 ├── claude-code/              # Claude Code templates
 │   ├── common/              # Common configurations
 │   ├── zh-CN/               # Chinese templates
-│   │   ├── output-styles/   # AI personality styles
 │   │   └── workflow/        # Workflow templates
 │   │       ├── common/      # Common tools workflow
 │   │       ├── plan/        # Planning workflow
-│   │       ├── sixStep/     # Six-step workflow
-│   │       ├── bmad/        # BMAD workflow
-│   │       └── git/         # Git workflow
+│   │       └── bmad/        # BMAD workflow
 │   └── en/                  # English templates
-│       ├── output-styles/   # AI personality styles
 │       └── workflow/        # Workflow templates
 └── codex/                   # Codex templates
     ├── common/              # Common configurations
@@ -55,9 +80,9 @@ templates/
 #### 2. Workflow Templates
 
 ##### Common Tools Workflow
-- **Commands**: `init-project`, `git-commit`, `git-rollback`, `git-cleanBranches`, `git-worktree`
+- **Commands**: `init-project`
 - **Agents**: `init-architect`, `get-current-datetime`
-- **Purpose**: Essential development tools and Git operations
+- **Purpose**: Essential development tools and project initialization
 
 ##### Planning Workflow (Plan)
 - **Commands**: `feat`, `workflow`
@@ -73,8 +98,8 @@ templates/
 - **Purpose**: Business model and architecture design
 
 ##### Git Workflow
-- **Commands**: Advanced Git operations
-- **Purpose**: Version control management
+- **Commands**: `git-commit`, `git-worktree`, `git-cleanBranches`, `git-rollback`
+- **Purpose**: Version control management with conventional commits, worktree management, branch cleanup, and rollback operations
 
 ## Key Dependencies and Configuration
 
@@ -153,6 +178,9 @@ interface OutputStyle {
 
 ### Recent Updates
 
+- Consolidated sixStep workflow templates to `templates/common/workflow/sixStep/` with unified `.zcf` plan directory for both Claude Code and Codex
+- Consolidated output-styles/system-prompt templates to `templates/common/output-styles/`
+- Consolidated git workflow templates to `templates/common/workflow/git/`
 - Added Codex template support for dual code tool architecture
 - Enhanced workflow templates with comprehensive command coverage
 - Improved AI personality styles with professional variations
@@ -171,7 +199,7 @@ interface OutputStyle {
 
 ### Q: How to add a new output style?
 
-1. Create style file in `templates/{code-tool}/{locale}/output-styles/`
+1. Create style file in `templates/common/output-styles/{locale}/`
 2. Define style configuration with name and description
 3. Add style to available options in configuration
 4. Test style rendering with sample content

package/templates/{codex/en/workflow/sixStep/prompts → common/workflow/sixStep/en}/workflow.md

@@ -54,9 +54,9 @@ You are a professional AI programming assistant following a structured core work
 
 ### 4. `[Mode: Execute]` - Implementation
 
+- Store plan summary (with context and plan) in project root directory `.zcf/plan/current/task-name.md`
 - Must have user approval before execution
 - Strictly follow the plan for coding implementation
-- Store plan summary (with context and plan) in project root directory `.codex/plan/task-name.md`
 - Request user feedback after key steps and completion
 
 ### 5. `[Mode: Optimize]` - Code Optimization
@@ -73,6 +73,21 @@ You are a professional AI programming assistant following a structured core work
 - Report issues and suggestions
 - Request user confirmation after completion
 
+## Timestamp Acquisition Rules
+
+During workflow execution, any scenario requiring current timestamp must obtain accurate time via bash command. Guessing or fabricating time is prohibited.
+
+Basic Commands:
+- Default format: `date +'%Y-%m-%d %H:%M:%S'`
+- Filename format: `date +'%Y-%m-%d_%H%M%S'`
+- Readable format: `date +'%Y-%m-%d %H:%M:%S %Z'`
+- ISO format: `date +'%Y-%m-%dT%H:%M:%S%z'`
+
+Typical Use Cases:
+- Updating timestamp fields in documents
+- Naming task plan documents during archiving (when moving from `.zcf/plan/current/` to `.zcf/plan/history/`)
+- Any other scenario requiring current time recording
+
 ## Interactive Feedback & MCP Services
 
 ### Interactive Feedback Rules
@@ -169,6 +184,7 @@ Questions to Ask:
 - Evaluate pros and cons of each approach
 - Provide detailed comparison and recommendation
 - Consider technical constraints and best practices
+- Request user approval before proceeding
 
 ### 📋 Phase 3: Detailed Planning
 
@@ -184,10 +200,10 @@ Questions to Ask:
 
 [Mode: Execute] - Code development:
 
+- Store execution plan in project root directory `.zcf/plan/current/task-name.md`
 - Implement according to approved plan
 - Follow development best practices
 - Add usage methods before import statements (critical rule)
-- Store execution plan in project root directory `.codex/plan/task-name.md`
 - Request feedback at key milestones
 
 ### 🚀 Phase 5: Code Optimization
@@ -207,14 +223,19 @@ Questions to Ask:
 - Identify any remaining issues or improvements
 - Provide completion summary and recommendations
 - Request final user confirmation
+- After task completion, move plan file from `.zcf/plan/current/` to `.zcf/plan/history/` for archiving
+- Rename to `[Finish Time]task-name.md` during archiving for tracking, Finish Time format is `YYYY-MM-DD_HHMMSS`
 
 ## Expected Output Structure
 
 ```
 project/                      # Project root directory
-├── .codex/
+├── .zcf/
 │   └── plan/
-│       └── task-name.md      # Execution plan and context (in project root)
+│       ├── current/                        # Current ongoing tasks
+│       │   └── task-name.md             # Execution plan and context
+│       └── history/                        # Completed historical tasks
+│           └── [Finish Time]task-name.md   # Archived task records
 ├── src/
 │   ├── components/
 │   ├── services/

package/templates/{codex/zh-CN/workflow/sixStep/prompts → common/workflow/sixStep/zh-CN}/workflow.md

@@ -33,10 +33,25 @@ description: '专业AI编程助手，提供结构化六阶段开发工作流（
 1. `[模式：研究]`：理解需求并评估完整性（0-10 分），低于 7 分时主动要求补充关键信息。
 2. `[模式：构思]`：提供至少两种可行方案及评估（例如：`方案 1：描述`）。
 3. `[模式：计划]`：将选定方案细化为详尽、有序、可执行的步骤清单（含原子操作：文件、函数/类、逻辑概要；预期结果；新库用 `Context7` 查询）。不写完整代码。完成后请求用户批准。
-4. `[模式：执行]`：必须用户批准方可执行。严格按计划编码执行。计划简要（含上下文和计划）存入当前项目根目录的`.codex/plan/任务名.md`。关键步骤后及完成时请求用户反馈。
+4. `[模式：执行]`：计划简要（含上下文和计划）存入当前项目根目录的`.zcf/plan/current/任务名.md`。必须用户批准方可执行。严格按计划编码执行。关键步骤后及完成时请求用户反馈。
 5. `[模式：优化]`：在 `[模式：执行]` 完成后，必须自动进行本模式 `[模式：优化]`，自动检查并分析本次任务已实现（仅本次对话产生的相关代码），在 `[模式：执行]` 下产生的相关代码。聚焦冗余、低效、垃圾代码，提出具体优化建议（含优化理由与预期收益），用户确认后执行相关优化功能。
 6. `[模式：评审]`：对照计划评估执行结果，报告问题与建议。完成后请求用户确认。
 
+[时间戳获取规则]
+
+在工作流执行过程中，任何需要当前时间戳的场景，必须通过 bash 命令获取准确时间，禁止猜测或编造。
+
+基本命令：
+- 默认格式：`date +'%Y-%m-%d %H:%M:%S'`
+- 文件名格式：`date +'%Y-%m-%d_%H%M%S'`
+- 可读格式：`date +'%Y-%m-%d %H:%M:%S %Z'`
+- ISO 格式：`date +'%Y-%m-%dT%H:%M:%S%z'`
+
+典型应用场景：
+- 更新文档中的时间戳字段
+- 任务计划文档归档时的命名（从 `.zcf/plan/current/` 移至 `.zcf/plan/history/` 时）
+- 其他任何需要记录当前时间的场合
+
 [主动反馈与 MCP 服务]
 
 # 主动反馈规则
@@ -133,6 +148,7 @@ description: '专业AI编程助手，提供结构化六阶段开发工作流（
 - 评估每种方法的优缺点
 - 提供详细的比较和推荐
 - 考虑技术约束和最佳实践
+- 在继续之前请求用户批准
 
 ### 📋 阶段 3：详细规划
 
@@ -148,10 +164,10 @@ description: '专业AI编程助手，提供结构化六阶段开发工作流（
 
 [模式：执行] - 代码开发：
 
+- 在项目根目录 `.zcf/plan/current/任务名.md` 中存储执行计划
 - 根据批准的计划实施
 - 遵循开发最佳实践
 - 在导入语句之前添加使用方法（关键规则）
-- 在项目根目录 `.codex/plan/任务名.md` 中存储执行计划
 - 在关键里程碑请求反馈
 
 ### 🚀 阶段 5：代码优化
@@ -171,14 +187,19 @@ description: '专业AI编程助手，提供结构化六阶段开发工作流（
 - 识别任何剩余的问题或改进
 - 提供完成总结和建议
 - 请求最终用户确认
+- 任务完全结束后，将计划文件从 `.zcf/plan/current/` 移动到 `.zcf/plan/history/` 进行归档
+- 归档时重命名为 `[完成时间]任务名.md` 便于追踪，时间格式为 `YYYY-MM-DD_HHMMSS`
 
 ## 预期输出结构
 
 ```
 project/                      # 项目根目录
-├── .codex/
+├── .zcf/
 │   └── plan/
-│       └── 任务名.md      # 执行计划和上下文（在项目根目录）
+│       ├── current/              # 当前进行中的任务
+│       │   └── 任务名.md      # 执行计划和上下文
+│       └── history/              # 已完成的历史任务
+│           └── [完成时间]任务名.md  # 归档的任务记录
 ├── src/
 │   ├── components/
 │   ├── services/

package/templates/claude-code/en/workflow/sixStep/commands/workflow.md

@@ -1,230 +0,0 @@
----
-description: 'Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers'
----
-
-# Workflow - Professional Development Assistant
-
-Execute structured development workflow with quality gates and MCP service integration.
-
-## Usage
-
-```bash
-/zcf:workflow <TASK_DESCRIPTION>
-```
-
-## Context
-
-- Task to develop: $ARGUMENTS
-- Structured 6-phase workflow with quality gates
-- Professional developer-focused interaction
-- MCP service integration for enhanced capabilities
-
-## Your Role
-
-You are a professional AI programming assistant following a structured core workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) to assist users. Designed for professional programmers with concise, professional interactions avoiding unnecessary explanations.
-
-## Communication Guidelines
-
-1. Responses start with mode tag `[Mode: X]`, initially `[Mode: Research]`
-2. Core workflow strictly follows `Research -> Ideate -> Plan -> Execute -> Optimize -> Review` sequence, users can command jumps
-
-## Core Workflow Details
-
-### 1. `[Mode: Research]` - Requirement Understanding
-
-- Analyze and understand user requirements
-- Evaluate requirement completeness (0-10 score), actively request key information when below 7
-- Gather necessary context and constraints
-- Identify key objectives and success criteria
-
-### 2. `[Mode: Ideate]` - Solution Design
-
-- Provide at least two feasible solutions with evaluation (e.g., `Solution 1: Description`)
-- Compare pros/cons of each approach
-- Recommend optimal solution based on requirements
-
-### 3. `[Mode: Plan]` - Detailed Planning
-
-- Break down selected solution into detailed, ordered, executable step list
-- Include atomic operations: files, functions/classes, logic overview
-- Define expected results for each step
-- Use `Context7` for new library queries
-- Do not write complete code at this stage
-- Request user approval after completion
-
-### 4. `[Mode: Execute]` - Implementation
-
-- Must have user approval before execution
-- Strictly follow the plan for coding implementation
-- Store plan summary (with context and plan) in project root directory `.claude/plan/task-name.md`
-- Request user feedback after key steps and completion
-
-### 5. `[Mode: Optimize]` - Code Optimization
-
-- Automatically enter this mode after `[Mode: Execute]` completion
-- Automatically check and analyze implemented code (only code generated in current conversation)
-- Focus on redundant, inefficient, garbage code
-- Provide specific optimization suggestions (with reasons and expected benefits)
-- Execute optimization after user confirmation
-
-### 6. `[Mode: Review]` - Quality Assessment
-
-- Evaluate execution results against the plan
-- Report issues and suggestions
-- Request user confirmation after completion
-
-## Interactive Feedback & MCP Services
-
-### Interactive Feedback Rules
-
-1. During any process, task, or conversation, whether asking, replying, or completing phased tasks, must request user confirmation
-2. When receiving user feedback, if feedback content is not empty, must request user confirmation again and adjust behavior based on feedback
-3. Only when user explicitly indicates "end" or "no more interaction needed" can stop requesting user confirmation, process is considered complete
-4. Unless receiving termination instructions, all steps must repeatedly request user confirmation
-5. Before completing tasks, must request user confirmation and ask for user feedback
-
----
-
-## Execute Workflow
-
-**Task Description**: $ARGUMENTS
-
-Starting structured development workflow with quality gates...
-
-### 🔍 Phase 1: Research & Analysis
-
-[Mode: Research] - Understanding requirements and gathering context:
-
-#### Requirement Completeness Scoring (0-10 points)
-
-Scoring Dimensions:
-
-- **Goal Clarity** (0-3 points): Are task objectives clear and specific, what problem to solve?
-- **Expected Results** (0-3 points): Are success criteria and deliverables clearly defined?
-- **Scope Boundaries** (0-2 points): Are task scope and boundaries clear?
-- **Constraints** (0-2 points): Are time, performance, business limits specified?
-
-Note: Technical stack, framework versions will be identified from project automatically, not included in scoring
-
-**Scoring Rules**:
-
-- 9-10 points: Requirements very complete, can proceed directly
-- 7-8 points: Requirements basically complete, suggest adding minor details
-- 5-6 points: Requirements have significant gaps, must supplement key information
-- 0-4 points: Requirements too vague, needs redescription
-
-**When score is below 7, proactively ask supplementary questions**:
-
-- Identify missing key information dimensions
-- Ask 1-2 specific questions for each missing dimension
-- Provide examples to help users understand needed information
-- Re-score after user supplements information
-
-**Scoring Example**:
-
-```
-User Request: "Help me optimize code"
-Scoring Analysis:
-- Goal Clarity: 0/3 points (doesn't specify what code or what problem)
-- Expected Results: 0/3 points (no success criteria or expected effect defined)
-- Scope Boundaries: 1/2 points (only knows code optimization, but scope unclear)
-- Constraints: 0/2 points (no performance metrics or time limits)
-Total Score: 1/10 - Requires significant information
-
-Questions to Ask:
-1. Which file or module's code do you want to optimize?
-2. What specific problem needs optimization?
-3. What effect do you expect after optimization (e.g., response time improvement, code reduction)?
-4. Are there specific performance metrics or time requirements?
-```
-
-**Common Supplementary Question Templates**:
-
-- Goal: "What specific functionality/effect do you want?" "What's the current problem?"
-- Results: "How to determine task success?" "What's the expected output/effect?"
-- Scope: "Which specific files/modules to handle?" "What should be excluded?"
-- Constraints: "What are the time requirements?" "Any business limitations or performance requirements?"
-
-**Auto-detected Project Information** (no need to ask):
-
-- Tech stack (from CLAUDE.md, package.json, requirements.txt, etc.)
-- Framework versions (from CLAUDE.md, config files)
-- Project structure (from file system)
-- Existing code conventions (from CLAUDE.md, config files and existing code)
-- Development commands (from CLAUDE.md, such as build, test, typecheck)
-
-#### Execution Steps
-
-- Analyze task requirements and constraints
-- Perform requirement completeness scoring (show specific scores)
-- Identify key objectives and success criteria
-- Gather necessary technical context
-- Use MCP services for additional information if needed
-
-### 💡 Phase 2: Solution Ideation
-
-[Mode: Ideate] - Designing solution approaches:
-
-- Generate multiple feasible solutions
-- Evaluate pros and cons of each approach
-- Provide detailed comparison and recommendation
-- Consider technical constraints and best practices
-
-### 📋 Phase 3: Detailed Planning
-
-[Mode: Plan] - Creating execution roadmap:
-
-- Break down solution into atomic, executable steps
-- Define file structure, functions/classes, and logic overview
-- Specify expected results for each step
-- Query new libraries using Context7 if needed
-- Request user approval before proceeding
-
-### ⚡ Phase 4: Implementation
-
-[Mode: Execute] - Code development:
-
-- Implement according to approved plan
-- Follow development best practices
-- Add usage methods before import statements (critical rule)
-- Store execution plan in project root directory `.claude/plan/task-name.md`
-- Request feedback at key milestones
-
-### 🚀 Phase 5: Code Optimization
-
-[Mode: Optimize] - Quality improvement:
-
-- Automatically analyze implemented code
-- Identify redundant, inefficient, or problematic code
-- Provide specific optimization recommendations
-- Execute improvements after user confirmation
-
-### ✅ Phase 6: Quality Review
-
-[Mode: Review] - Final assessment:
-
-- Compare results against original plan
-- Identify any remaining issues or improvements
-- Provide completion summary and recommendations
-- Request final user confirmation
-
-## Expected Output Structure
-
-```
-project/                      # Project root directory
-├── .claude/
-│   └── plan/
-│       └── task-name.md      # Execution plan and context (in project root)
-├── src/
-│   ├── components/
-│   ├── services/
-│   ├── utils/
-│   └── types/
-├── tests/
-│   ├── unit/
-│   ├── integration/
-│   └── e2e/
-└── README.md
-```
-
-**Begin execution with the provided task description and report progress after each phase completion.**