refactor(workflow): rename workflow-lite-plan to workflow-lite-planex and remove standalone lite-execute

- Rename skill directory from workflow-lite-plan to workflow-lite-planex (planex = plan + execute)
- Remove standalone lite-execute command entry from command.json and analyze_commands.py
- Update all 60+ files referencing workflow-lite-plan to use workflow-lite-planex
- Update descriptions to clarify Phase 1: plan → Phase 2: execute architecture
- Remove lite-execute as standalone command from orchestrator routing tables
- Update docs (EN/ZH) to reflect unified planex naming and phase descriptions
This commit is contained in:
catlog22
2026-03-02 14:03:17 +08:00
parent 71485b89e6
commit 0d5cc4a74f
60 changed files with 277 additions and 445 deletions

View File

@@ -155,7 +155,7 @@
},
"development_index": {
"type": "object",
"description": "Categorized development history (lite-plan/lite-execute)",
"description": "Categorized development history (lite-planex sessions)",
"properties": {
"feature": { "type": "array", "items": { "$ref": "#/$defs/devIndexEntry" } },
"enhancement": { "type": "array", "items": { "$ref": "#/$defs/devIndexEntry" } },

View File

@@ -783,7 +783,7 @@ All workflows use the same file structure definition regardless of complexity. *
**Examples**:
*Workflow Commands (lightweight):*
- `/workflow-lite-plan "feature idea"` (exploratory) → `.scratchpad/lite-plan-feature-idea-20250105-143110.md`
- `/workflow-lite-planex "feature idea"` (exploratory) → `.scratchpad/lite-plan-feature-idea-20250105-143110.md`
- `/workflow:lite-fix "bug description"` (bug fixing) → `.scratchpad/lite-fix-bug-20250105-143130.md`
> **Note**: Direct CLI commands (`/cli:analyze`, `/cli:execute`, etc.) have been replaced by semantic invocation and workflow commands.

View File

@@ -17,10 +17,10 @@ Interactive orchestration tool: analyze task → discover commands → recommend
| Skill | 包含操作 |
|-------|---------|
| `workflow-lite-plan` | lite-plan, lite-execute |
| `workflow-lite-planex` | lite-plan (includes execution phase internally) |
| `workflow-plan` | plan, plan-verify, replan |
| `workflow-execute` | execute |
| `workflow-multi-cli-plan` | multi-cli-plan |
| `workflow-multi-cli-plan` | multi-cli-plan (includes execution phase internally) |
| `workflow-test-fix` | test-fix-gen, test-cycle-execute |
| `workflow-tdd-plan` | tdd-plan, tdd-verify |
| `review-cycle` | review-session-cycle, review-module-cycle, review-cycle-fix |
@@ -49,9 +49,9 @@ Interactive orchestration tool: analyze task → discover commands → recommend
| Unit Name | Commands | Purpose | Output |
|-----------|----------|---------|--------|
| **Quick Implementation** | lite-plan → lite-execute | Lightweight plan and immediate execution | Working code |
| **Multi-CLI Planning** | multi-cli-plan → lite-execute | Multi-perspective analysis and execution | Working code |
| **Bug Fix** | lite-plan (--bugfix) → lite-execute | Quick bug diagnosis and fix execution | Fixed code |
| **Quick Implementation** | lite-plan (Phase 1: plan → Phase 2: execute) | Lightweight plan and immediate execution | Working code |
| **Multi-CLI Planning** | multi-cli-plan (Phase 1: plan → Phase 2: execute) | Multi-perspective analysis and execution | Working code |
| **Bug Fix** | lite-plan --bugfix (Phase 1: plan → Phase 2: execute) | Quick bug diagnosis and fix execution | Fixed code |
| **Full Planning + Execution** | plan → execute | Detailed planning and execution | Working code |
| **Verified Planning + Execution** | plan → plan-verify → execute | Planning with verification and execution | Working code |
| **Replanning + Execution** | replan → execute | Update plan and execute changes | Working code |
@@ -101,8 +101,8 @@ Interactive orchestration tool: analyze task → discover commands → recommend
| Command | Can Precede | Atomic Units |
|---------|-----------|--------------|
| lite-plan | lite-execute, convert-to-plan | Quick Implementation, Rapid-to-Issue, Bug Fix |
| multi-cli-plan | lite-execute | Multi-CLI Planning |
| lite-plan | convert-to-plan | Quick Implementation, Rapid-to-Issue, Bug Fix |
| multi-cli-plan | (execution is internal) | Multi-CLI Planning |
| plan | plan-verify, execute | Full Planning + Execution, Verified Planning + Execution |
| plan-verify | execute | Verified Planning + Execution |
| replan | execute | Replanning + Execution |
@@ -137,8 +137,8 @@ Interactive orchestration tool: analyze task → discover commands → recommend
**Example Pipeline with Units**:
```
需求 → 【lite-plan → lite-execute】→ 代码 → 【test-fix-gen → test-cycle-execute】→ 测试通过
└──── Quick Implementation ────┘ └────── Test Validation ──────┘
需求 → 【lite-plan】→ 代码 → 【test-fix-gen → test-cycle-execute】→ 测试通过
└── Quick Implementation ── └────── Test Validation ──────┘
```
## 3-Phase Workflow
@@ -234,13 +234,7 @@ const commandPorts = {
tags: ['planning'],
atomic_group: 'quick-implementation'
},
'lite-execute': {
name: 'lite-execute',
input: ['plan', 'multi-cli-plan'],
output: ['code'],
tags: ['execution'],
atomic_groups: ['quick-implementation', 'multi-cli-planning', 'bug-fix']
},
// lite-execute is now an internal phase of lite-plan and multi-cli-plan (not a standalone command)
'plan': {
name: 'plan',
input: ['requirement', 'specification'],
@@ -550,12 +544,11 @@ function determinePortFlow(taskType, constraints) {
Recommended Command Chain:
Pipeline (管道视图):
需求 → lite-plan → 计划 → lite-execute → 代码 → test-cycle-execute → 测试通过
需求 → lite-plan → 代码 → test-cycle-execute → 测试通过
Commands (命令列表):
1. /workflow-lite-plan
2. /workflow:lite-execute
3. /workflow-test-fix
1. /workflow-lite-planex
2. /workflow-test-fix
Proceed? [Confirm / Show Details / Adjust / Cancel]
```
@@ -690,9 +683,7 @@ function formatCommand(cmd, previousResults, analysis) {
if (['lite-plan', 'plan', 'tdd-plan', 'multi-cli-plan'].includes(name)) {
prompt += ` "${analysis.goal}"`;
} else if (name === 'lite-execute') {
const hasPlan = previousResults.some(r => r.command.includes('plan'));
prompt += hasPlan ? ' --in-memory' : ` "${analysis.goal}"`;
// lite-execute is now an internal phase of lite-plan (not invoked separately)
} else if (name === 'execute') {
const plan = previousResults.find(r => r.command.includes('plan'));
@@ -711,7 +702,7 @@ function formatCommand(cmd, previousResults, analysis) {
prompt = `/spec-generator -y "${analysis.goal}"`;
} else if (name === 'test-gen') {
const impl = previousResults.find(r => r.command.includes('execute') || r.command.includes('lite-execute'));
const impl = previousResults.find(r => r.command.includes('execute'));
prompt += impl?.session_id ? ` "${impl.session_id}"` : ` "${analysis.goal}"`;
} else if (name === 'test-fix-gen') {
@@ -860,7 +851,7 @@ workflow 操作通过 `Skill()` 调用对应的 Skill。
```javascript
// Skill 调用方式
Skill({ skill: 'workflow-lite-plan', args: '"task description"' });
Skill({ skill: 'workflow-lite-planex', args: '"task description"' });
Skill({ skill: 'workflow-execute', args: '--resume-session="WFS-xxx"' });
Skill({ skill: 'brainstorm', args: '"exploration topic"' });
Skill({ skill: 'spec-generator', args: '"product specification"' });
@@ -913,10 +904,10 @@ Task: <description>
| Skill | 包含操作 |
|-------|---------|
| `workflow-lite-plan` | lite-plan, lite-execute |
| `workflow-lite-planex` | lite-plan (includes execution phase internally) |
| `workflow-plan` | plan, plan-verify, replan |
| `workflow-execute` | execute |
| `workflow-multi-cli-plan` | multi-cli-plan |
| `workflow-multi-cli-plan` | multi-cli-plan (includes execution phase internally) |
| `workflow-test-fix` | test-fix-gen, test-cycle-execute |
| `workflow-tdd-plan` | tdd-plan, tdd-verify |
| `review-cycle` | review-session-cycle, review-module-cycle, review-cycle-fix |
@@ -948,7 +939,7 @@ Task: <description>
| Task Type | Pipeline | Minimum Units |
|-----------|----------|---|
| **feature** (simple) | 需求 →【lite-plan → lite-execute】→ 代码 →【test-fix-gen → test-cycle-execute】→ 测试通过 | Quick Implementation + Test Validation |
| **feature** (simple) | 需求 →【lite-plan】→ 代码 →【test-fix-gen → test-cycle-execute】→ 测试通过 | Quick Implementation + Test Validation |
| **feature** (complex) | 需求 →【plan → plan-verify】→ validate → execute → 代码 → review → fix | Full Planning + Code Review + Testing |
| **bugfix** | Bug报告 → lite-plan (--bugfix) → 修复代码 →【test-fix-gen → test-cycle-execute】→ 测试通过 | Bug Fix + Test Validation |
| **tdd** | 需求 → tdd-plan → TDD任务 → execute → 代码 → tdd-verify | TDD Planning + Execution |
@@ -956,11 +947,11 @@ Task: <description>
| **test-gen** | 代码/会话 →【test-gen → execute】→ 测试通过 | Test Generation + Execution |
| **review** | 代码 →【review-* → review-cycle-fix】→ 修复代码 →【test-fix-gen → test-cycle-execute】→ 测试通过 | Code Review + Testing |
| **brainstorm** | 探索主题 → brainstorm → 分析 →【plan → plan-verify】→ execute → test | Exploration + Planning + Execution |
| **multi-cli** | 需求 → multi-cli-plan → 对比分析 → lite-execute → test | Multi-Perspective + Testing |
| **multi-cli** | 需求 → multi-cli-plan → 对比分析 → 代码 → test | Multi-Perspective + Testing |
| **spec-driven** | 需求 →【spec-generator → plan → execute】→ 代码 →【test-fix-gen → test-cycle-execute】→ 测试通过 | Spec-Driven + Testing |
| **issue-batch** | 代码库 →【discover → plan → queue → execute】→ 完成 issues | Issue Workflow |
| **issue-transition** | 需求 →【lite-plan → convert-to-plan → queue → execute】→ 完成 issues | Rapid-to-Issue |
| **analyze-file** | 分析主题 →【analyze-with-file → lite-plan → lite-execute】→ 代码 | Analyze to Plan |
| **analyze-file** | 分析主题 →【analyze-with-file → lite-plan】→ 代码 | Analyze to Plan |
| **greenfield** | 需求 →【brainstorm-with-file → plan → execute】→ 代码 → test | Greenfield (0→1) |
| **brainstorm-file** | 主题 →【brainstorm-with-file → plan → execute】→ 代码 → test | Brainstorm to Plan |
| **brainstorm-to-issue** | brainstorm.md →【from-brainstorm → queue → execute】→ 完成 issues | Brainstorm to Issue |
@@ -972,8 +963,8 @@ Task: <description>
| **team-planex** | 需求 → team-planex → 代码 (自包含) | Team Plan+Execute |
| **bugfix-hotfix** | Bug报告(紧急) → lite-plan (--hotfix) → 修复代码 | Hotfix (skip tests) |
| **exploration** | 探索主题 → brainstorm →【plan → execute】→ 代码 → test | Exploration + Planning |
| **quick-task** | 需求 →【lite-plan → lite-execute】→ 代码 → test | Quick Implementation |
| **quick-task** | 需求 →【lite-plan】→ 代码 → test | Quick Implementation |
| **ui-design** | UI需求 → ui-design:explore → plan → execute → 代码 | UI Design |
| **documentation** | 文档需求 → lite-plan → lite-execute → 文档 | Documentation |
| **documentation** | 文档需求 → lite-plan → 文档 | Documentation |
Refer to the Skill 映射 section above for available Skills and Commands.

View File

@@ -15,7 +15,7 @@ Main process orchestrator: intent analysis → workflow selection → command ch
| Skill | 内部流水线 |
|-------|-----------|
| `workflow-lite-plan` | explore → plan → confirm → execute |
| `workflow-lite-planex` | explore → plan → confirm → execute |
| `workflow-plan` | session → context → convention → gen → verify/replan |
| `workflow-execute` | session discovery → task processing → commit |
| `workflow-tdd-plan` | 6-phase TDD plan → verify |
@@ -43,14 +43,14 @@ Main process orchestrator: intent analysis → workflow selection → command ch
| 单元类型 | Skill | 说明 |
|---------|-------|------|
| 轻量 Plan+Execute | `workflow-lite-plan` | 内部完成 plan→execute |
| 轻量 Plan+Execute | `workflow-lite-planex` | 内部完成 plan→execute |
| 标准 Planning | `workflow-plan``workflow-execute` | plan 和 execute 是独立 Skill |
| TDD Planning | `workflow-tdd-plan``workflow-execute` | tdd-plan 和 execute 是独立 Skill |
| 规格驱动 | `spec-generator``workflow-plan``workflow-execute` | 规格文档驱动完整开发 |
| 测试流水线 | `workflow-test-fix` | 内部完成 gen→cycle |
| 代码审查 | `review-cycle` | 内部完成 review→fix |
| 多CLI协作 | `workflow-multi-cli-plan` | ACE context → CLI discussion → plan → execute |
| 分析→规划 | `workflow:analyze-with-file``workflow-lite-plan` | 协作分析产物自动传递给 lite-plan |
| 分析→规划 | `workflow:analyze-with-file``workflow-lite-planex` | 协作分析产物自动传递给 lite-plan |
| 头脑风暴→规划 | `workflow:brainstorm-with-file``workflow-plan``workflow-execute` | 头脑风暴产物自动传递给正式规划 |
| 0→1 开发(小) | `workflow:brainstorm-with-file``workflow-plan``workflow-execute` | 小规模从零开始,探索+正式规划+实现 |
| 0→1 开发(中/大) | `workflow:brainstorm-with-file``workflow-plan``workflow-execute` | 探索后正式规划+执行 |
@@ -231,7 +231,7 @@ function buildCommandChain(workflow, analysis) {
const chains = {
// Level 2 - Lightweight
'rapid': [
{ cmd: 'workflow-lite-plan', args: `"${analysis.goal}"` },
{ cmd: 'workflow-lite-planex', args: `"${analysis.goal}"` },
...(analysis.constraints?.includes('skip-tests') ? [] : [
{ cmd: 'workflow-test-fix', args: '' }
])
@@ -239,21 +239,21 @@ function buildCommandChain(workflow, analysis) {
// Level 2 Bridge - Lightweight to Issue Workflow
'rapid-to-issue': [
{ cmd: 'workflow-lite-plan', args: `"${analysis.goal}" --plan-only` },
{ cmd: 'workflow-lite-planex', args: `"${analysis.goal}" --plan-only` },
{ cmd: 'issue:convert-to-plan', args: '--latest-lite-plan -y' },
{ cmd: 'issue:queue', args: '' },
{ cmd: 'issue:execute', args: '--queue auto' }
],
'bugfix.standard': [
{ cmd: 'workflow-lite-plan', args: `--bugfix "${analysis.goal}"` },
{ cmd: 'workflow-lite-planex', args: `--bugfix "${analysis.goal}"` },
...(analysis.constraints?.includes('skip-tests') ? [] : [
{ cmd: 'workflow-test-fix', args: '' }
])
],
'bugfix.hotfix': [
{ cmd: 'workflow-lite-plan', args: `--hotfix "${analysis.goal}"` }
{ cmd: 'workflow-lite-planex', args: `--hotfix "${analysis.goal}"` }
],
'multi-cli-plan': [
@@ -264,13 +264,13 @@ function buildCommandChain(workflow, analysis) {
],
'docs': [
{ cmd: 'workflow-lite-plan', args: `"${analysis.goal}"` }
{ cmd: 'workflow-lite-planex', args: `"${analysis.goal}"` }
],
// With-File → Auto Chain to lite-plan
'analyze-to-plan': [
{ cmd: 'workflow:analyze-with-file', args: `"${analysis.goal}"` },
{ cmd: 'workflow-lite-plan', args: '' } // auto receives analysis artifacts (discussion.md)
{ cmd: 'workflow-lite-planex', args: '' } // auto receives analysis artifacts (discussion.md)
],
'brainstorm-to-plan': [
@@ -476,7 +476,7 @@ function setupTodoTracking(chain, workflow, analysis) {
```
**Output**:
- TODO: `-> CCW:rapid: [1/2] workflow-lite-plan | CCW:rapid: [2/2] workflow-test-fix | ...`
- TODO: `-> CCW:rapid: [1/2] workflow-lite-planex | CCW:rapid: [2/2] workflow-test-fix | ...`
- Status File: `.workflow/.ccw/{session_id}/status.json`
---
@@ -628,10 +628,10 @@ Phase 5: Execute Command Chain
| Input | Type | Level | Pipeline |
|-------|------|-------|----------|
| "Add API endpoint" | feature (low) | 2 | workflow-lite-plan → workflow-test-fix |
| "Fix login timeout" | bugfix | 2 | workflow-lite-plan → workflow-test-fix |
| "Use issue workflow" | issue-transition | 2.5 | workflow-lite-plan(plan-only) → convert-to-plan → queue → execute |
| "协作分析: 认证架构" | analyze-file | 3 | analyze-with-file → workflow-lite-plan |
| "Add API endpoint" | feature (low) | 2 | workflow-lite-planex → workflow-test-fix |
| "Fix login timeout" | bugfix | 2 | workflow-lite-planex → workflow-test-fix |
| "Use issue workflow" | issue-transition | 2.5 | workflow-lite-planex(plan-only) → convert-to-plan → queue → execute |
| "协作分析: 认证架构" | analyze-file | 3 | analyze-with-file → workflow-lite-planex |
| "深度调试 WebSocket" | debug-file | 3 | workflow:debug-with-file |
| "从零开始: 用户系统" | greenfield (medium) | 3 | brainstorm-with-file → workflow-plan → workflow-execute → workflow-test-fix |
| "greenfield: 大型平台" | greenfield (high) | 4 | brainstorm-with-file → workflow-plan → workflow-execute → review-cycle → workflow-test-fix |
@@ -673,13 +673,13 @@ Phase 5: Execute Command Chain
```javascript
// Initial state (rapid workflow: 2 steps)
todos = [
{ content: "CCW:rapid: [1/2] workflow-lite-plan", status: "in_progress" },
{ content: "CCW:rapid: [1/2] workflow-lite-planex", status: "in_progress" },
{ content: "CCW:rapid: [2/2] workflow-test-fix", status: "pending" }
];
// After step 1 completes
todos = [
{ content: "CCW:rapid: [1/2] workflow-lite-plan", status: "completed" },
{ content: "CCW:rapid: [1/2] workflow-lite-planex", status: "completed" },
{ content: "CCW:rapid: [2/2] workflow-test-fix", status: "in_progress" }
];
```
@@ -704,7 +704,7 @@ todos = [
"complexity": "medium"
},
"command_chain": [
{ "index": 0, "command": "workflow-lite-plan", "status": "completed" },
{ "index": 0, "command": "workflow-lite-planex", "status": "completed" },
{ "index": 1, "command": "workflow-test-fix", "status": "running" }
],
"current_index": 1
@@ -724,11 +724,11 @@ todos = [
|----------|---------|------------|---------------|
| **brainstorm-with-file** | Multi-perspective ideation | → workflow-plan → workflow-execute (auto) | `.workflow/.brainstorm/` |
| **debug-with-file** | Hypothesis-driven debugging | Standalone (self-contained) | `.workflow/.debug/` |
| **analyze-with-file** | Collaborative analysis | → workflow-lite-plan (auto) | `.workflow/.analysis/` |
| **analyze-with-file** | Collaborative analysis | → workflow-lite-planex (auto) | `.workflow/.analysis/` |
| **collaborative-plan-with-file** | Multi-agent collaborative planning | → unified-execute-with-file | `.workflow/.planning/` |
| **roadmap-with-file** | Strategic requirement roadmap | → team-planex | `.workflow/.planning/` |
**Auto Chain Mechanism**: When `analyze-with-file` completes, its artifacts (discussion.md) are automatically passed to `workflow-lite-plan`. When `brainstorm-with-file` completes, its artifacts (brainstorm.md) are passed to `workflow-plan` for formal planning. No user intervention needed.
**Auto Chain Mechanism**: When `analyze-with-file` completes, its artifacts (discussion.md) are automatically passed to `workflow-lite-planex`. When `brainstorm-with-file` completes, its artifacts (brainstorm.md) are passed to `workflow-plan` for formal planning. No user intervention needed.
**Detection Keywords**:
- **brainstorm**: 头脑风暴, 创意, 发散思维, multi-perspective, compare perspectives
@@ -793,7 +793,7 @@ todos = [
/ccw "全新开发: 实时通知系统" # → brainstorm-with-file → workflow-plan → workflow-execute → review-cycle → workflow-test-fix
# With-File workflows → auto chain
/ccw "协作分析: 理解现有认证架构的设计决策" # → analyze-with-file → workflow-lite-plan
/ccw "协作分析: 理解现有认证架构的设计决策" # → analyze-with-file → workflow-lite-planex
/ccw "头脑风暴: 用户通知系统重新设计" # → brainstorm-with-file → workflow-plan → workflow-execute → workflow-test-fix
/ccw "深度调试: 系统随机崩溃问题" # → debug-with-file (standalone)
/ccw "从头脑风暴 BS-通知系统-2025-01-28 创建 issue" # → brainstorm-to-issue (bridge)

View File

@@ -378,7 +378,7 @@ docker-compose.override.yml
## Integration Points
### Workflow Commands
- **After `workflow-lite-plan` skill**: Suggest running cli-init for better analysis
- **After `workflow-lite-planex` skill**: Suggest running cli-init for better analysis
- **Before analysis**: Recommend updating ignore patterns for cleaner results
### CLI Tool Integration

View File

@@ -86,7 +86,7 @@ async function selectCommandCategory() {
header: "Category",
options: [
{ label: "Planning", description: "lite-plan, plan, multi-cli-plan, tdd-plan, quick-plan-with-file" },
{ label: "Execution", description: "lite-execute, execute, unified-execute-with-file" },
{ label: "Execution", description: "execute, unified-execute-with-file" },
{ label: "Testing", description: "test-fix-gen, test-cycle-execute, test-gen, tdd-verify" },
{ label: "Review", description: "review-session-cycle, review-module-cycle, review-cycle-fix" },
{ label: "Bug Fix", description: "lite-plan --bugfix, debug-with-file" },
@@ -107,7 +107,7 @@ async function selectCommandCategory() {
async function selectCommand(category) {
const commandOptions = {
'Planning': [
{ label: "/workflow-lite-plan", description: "Lightweight merged-mode planning" },
{ label: "/workflow-lite-planex", description: "Lightweight merged-mode planning" },
{ label: "/workflow-plan", description: "Full planning with architecture design" },
{ label: "/workflow-multi-cli-plan", description: "Multi-CLI collaborative planning (Gemini+Codex+Claude)" },
{ label: "/workflow-tdd-plan", description: "TDD workflow planning with Red-Green-Refactor" },
@@ -116,7 +116,6 @@ async function selectCommand(category) {
{ label: "/workflow:replan", description: "Update plan and execute changes" }
],
'Execution': [
{ label: "/workflow:lite-execute", description: "Execute from in-memory plan" },
{ label: "/workflow-execute", description: "Execute from planning session" },
{ label: "/workflow:unified-execute-with-file", description: "Universal execution engine" }
],
@@ -133,7 +132,7 @@ async function selectCommand(category) {
{ label: "/workflow:review", description: "Post-implementation review" }
],
'Bug Fix': [
{ label: "/workflow-lite-plan", description: "Lightweight bug diagnosis and fix (with --bugfix flag)" },
{ label: "/workflow-lite-planex", description: "Lightweight bug diagnosis and fix (with --bugfix flag)" },
{ label: "/workflow:debug-with-file", description: "Hypothesis-driven debugging with documentation" }
],
'Brainstorm': [
@@ -181,8 +180,8 @@ async function selectExecutionUnit() {
header: "Unit",
options: [
// Planning + Execution Units
{ label: "quick-implementation", description: "【lite-plan → lite-execute】" },
{ label: "multi-cli-planning", description: "【multi-cli-plan → lite-execute】" },
{ label: "quick-implementation", description: "【lite-plan】" },
{ label: "multi-cli-planning", description: "【multi-cli-plan】" },
{ label: "full-planning-execution", description: "【plan → execute】" },
{ label: "verified-planning-execution", description: "【plan → plan-verify → execute】" },
{ label: "replanning-execution", description: "【replan → execute】" },
@@ -193,7 +192,7 @@ async function selectExecutionUnit() {
// Review Units
{ label: "code-review", description: "【review-*-cycle → review-cycle-fix】" },
// Bug Fix Units
{ label: "bug-fix", description: "【lite-plan --bugfix → lite-execute】" },
{ label: "bug-fix", description: "【lite-plan --bugfix】" },
// Issue Units
{ label: "issue-workflow", description: "【discover → plan → queue → execute】" },
{ label: "rapid-to-issue", description: "【lite-plan → convert-to-plan → queue → execute】" },
@@ -303,8 +302,7 @@ async function defineSteps(templateDesign) {
"description": "Quick implementation with testing",
"level": 2,
"steps": [
{ "cmd": "/workflow-lite-plan", "args": "\"{{goal}}\"", "unit": "quick-implementation", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Create lightweight implementation plan" },
{ "cmd": "/workflow:lite-execute", "args": "--in-memory", "unit": "quick-implementation", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Execute implementation based on plan" },
{ "cmd": "/workflow-lite-planex", "args": "\"{{goal}}\"", "unit": "quick-implementation", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Create lightweight implementation plan (includes execution)" },
{ "cmd": "/workflow-test-fix", "unit": "test-validation", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Generate test tasks" },
{ "cmd": "/workflow-test-fix", "unit": "test-validation", "execution": { "type": "slash-command", "mode": "async" }, "contextHint": "Execute test-fix cycle until pass rate >= 95%" }
]
@@ -336,8 +334,7 @@ async function defineSteps(templateDesign) {
"description": "Bug diagnosis and fix with testing",
"level": 2,
"steps": [
{ "cmd": "/workflow-lite-plan", "args": "--bugfix \"{{goal}}\"", "unit": "bug-fix", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Diagnose and plan bug fix" },
{ "cmd": "/workflow:lite-execute", "args": "--in-memory", "unit": "bug-fix", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Execute bug fix" },
{ "cmd": "/workflow-lite-planex", "args": "--bugfix \"{{goal}}\"", "unit": "bug-fix", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Diagnose, plan, and execute bug fix" },
{ "cmd": "/workflow-test-fix", "unit": "test-validation", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Generate regression tests" },
{ "cmd": "/workflow-test-fix", "unit": "test-validation", "execution": { "type": "slash-command", "mode": "async" }, "contextHint": "Verify fix with tests" }
]
@@ -351,7 +348,7 @@ async function defineSteps(templateDesign) {
"description": "Urgent production bug fix (no tests)",
"level": 2,
"steps": [
{ "cmd": "/workflow-lite-plan", "args": "--hotfix \"{{goal}}\"", "unit": "standalone", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Emergency hotfix mode" }
{ "cmd": "/workflow-lite-planex", "args": "--hotfix \"{{goal}}\"", "unit": "standalone", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Emergency hotfix mode" }
]
}
```
@@ -420,7 +417,7 @@ async function defineSteps(templateDesign) {
"description": "Bridge lightweight planning to issue workflow",
"level": 2,
"steps": [
{ "cmd": "/workflow-lite-plan", "args": "\"{{goal}}\"", "unit": "rapid-to-issue", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Create lightweight plan" },
{ "cmd": "/workflow-lite-planex", "args": "\"{{goal}}\"", "unit": "rapid-to-issue", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Create lightweight plan" },
{ "cmd": "/issue:convert-to-plan", "args": "--latest-lite-plan -y", "unit": "rapid-to-issue", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Convert to issue plan" },
{ "cmd": "/issue:queue", "unit": "rapid-to-issue", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Form execution queue" },
{ "cmd": "/issue:execute", "args": "--queue auto", "unit": "rapid-to-issue", "execution": { "type": "slash-command", "mode": "async" }, "contextHint": "Execute issue queue" }
@@ -503,7 +500,7 @@ async function defineSteps(templateDesign) {
"level": 3,
"steps": [
{ "cmd": "/workflow-multi-cli-plan", "args": "\"{{goal}}\"", "unit": "multi-cli-planning", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Gemini+Codex+Claude collaborative planning" },
{ "cmd": "/workflow:lite-execute", "args": "--in-memory", "unit": "multi-cli-planning", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Execute converged plan" },
// lite-execute is now an internal phase of multi-cli-plan (not invoked separately)
{ "cmd": "/workflow-test-fix", "unit": "test-validation", "execution": { "type": "slash-command", "mode": "mainprocess" }, "contextHint": "Generate tests" },
{ "cmd": "/workflow-test-fix", "unit": "test-validation", "execution": { "type": "slash-command", "mode": "async" }, "contextHint": "Execute test cycle" }
]
@@ -530,7 +527,7 @@ Each command has input/output ports for pipeline composition:
| tdd-plan | requirement | tdd-tasks | tdd-planning-execution |
| replan | session, feedback | replan | replanning-execution |
| **Execution** |
| lite-execute | plan, multi-cli-plan | code | (multiple) |
| ~~lite-execute~~ | _(internal phase of lite-plan/multi-cli-plan, not standalone)_ | code | — |
| execute | detailed-plan, verified-plan, replan, tdd-tasks | code | (multiple) |
| **Testing** |
| test-fix-gen | failing-tests, session | test-tasks | test-validation |
@@ -563,9 +560,9 @@ Each command has input/output ports for pipeline composition:
| Unit Name | Commands | Purpose |
|-----------|----------|---------|
| **quick-implementation** | lite-plan → lite-execute | Lightweight plan and execution |
| **multi-cli-planning** | multi-cli-plan → lite-execute | Multi-perspective planning and execution |
| **bug-fix** | lite-plan --bugfix → lite-execute | Bug diagnosis and fix |
| **quick-implementation** | lite-plan (Phase 1: plan → Phase 2: execute) | Lightweight plan and execution |
| **multi-cli-planning** | multi-cli-plan (Phase 1: plan → Phase 2: execute) | Multi-perspective planning and execution |
| **bug-fix** | lite-plan --bugfix (Phase 1: plan → Phase 2: execute) | Bug diagnosis and fix |
| **full-planning-execution** | plan → execute | Detailed planning and execution |
| **verified-planning-execution** | plan → plan-verify → execute | Planning with verification |
| **replanning-execution** | replan → execute | Update plan and execute |

View File

@@ -15,16 +15,16 @@ When `--yes` or `-y`: Auto-skip interrupted task, continue with remaining.
```javascript
const SKILL_CHAIN_MAP = {
'bugfix': ['workflow-lite-plan', 'workflow-test-fix'],
'bugfix-hotfix': ['workflow-lite-plan'],
'feature': ['workflow-lite-plan', 'workflow-test-fix'],
'bugfix': ['workflow-lite-planex', 'workflow-test-fix'],
'bugfix-hotfix': ['workflow-lite-planex'],
'feature': ['workflow-lite-planex', 'workflow-test-fix'],
'feature-complex': ['workflow-plan', 'workflow-execute', 'workflow-test-fix'],
'refactor': ['workflow:refactor-cycle'],
'tdd': ['workflow-tdd-plan', 'workflow-execute'],
'test': ['workflow-test-fix'],
'test-fix': ['workflow-test-fix'],
'review': ['review-cycle'],
'docs': ['workflow-lite-plan']
'docs': ['workflow-lite-planex']
};
```

View File

@@ -26,16 +26,16 @@ Coordinator variant of `/idaw:run`: external CLI execution with background tasks
```javascript
const SKILL_CHAIN_MAP = {
'bugfix': ['workflow-lite-plan', 'workflow-test-fix'],
'bugfix-hotfix': ['workflow-lite-plan'],
'feature': ['workflow-lite-plan', 'workflow-test-fix'],
'bugfix': ['workflow-lite-planex', 'workflow-test-fix'],
'bugfix-hotfix': ['workflow-lite-planex'],
'feature': ['workflow-lite-planex', 'workflow-test-fix'],
'feature-complex': ['workflow-plan', 'workflow-execute', 'workflow-test-fix'],
'refactor': ['workflow:refactor-cycle'],
'tdd': ['workflow-tdd-plan', 'workflow-execute'],
'test': ['workflow-test-fix'],
'test-fix': ['workflow-test-fix'],
'review': ['review-cycle'],
'docs': ['workflow-lite-plan']
'docs': ['workflow-lite-planex']
};
```
@@ -472,11 +472,11 @@ function assembleCliPrompt(skillName, task, previousResult, autoYes) {
const yFlag = autoYes ? ' -y' : '';
// Map skill to command invocation
if (skillName === 'workflow-lite-plan') {
if (skillName === 'workflow-lite-planex') {
const goal = sanitize(`${task.title}\n${task.description}`);
prompt = `/workflow-lite-plan${yFlag} "${goal}"`;
if (task.task_type === 'bugfix') prompt = `/workflow-lite-plan${yFlag} --bugfix "${goal}"`;
if (task.task_type === 'bugfix-hotfix') prompt = `/workflow-lite-plan${yFlag} --hotfix "${goal}"`;
prompt = `/workflow-lite-planex${yFlag} "${goal}"`;
if (task.task_type === 'bugfix') prompt = `/workflow-lite-planex${yFlag} --bugfix "${goal}"`;
if (task.task_type === 'bugfix-hotfix') prompt = `/workflow-lite-planex${yFlag} --hotfix "${goal}"`;
} else if (skillName === 'workflow-plan') {
prompt = `/workflow-plan${yFlag} "${sanitize(task.title)}"`;
@@ -608,8 +608,8 @@ Phase 5: handleStepCompletion()
{
"task_id": "IDAW-001",
"skill_index": 0,
"skill": "workflow-lite-plan",
"prompt": "/workflow-lite-plan -y \"Fix login timeout\"",
"skill": "workflow-lite-planex",
"prompt": "/workflow-lite-planex -y \"Fix login timeout\"",
"timestamp": "ISO"
}
]

View File

@@ -15,16 +15,16 @@ When `--yes` or `-y`: Skip all confirmations, auto-skip on failure, proceed with
```javascript
const SKILL_CHAIN_MAP = {
'bugfix': ['workflow-lite-plan', 'workflow-test-fix'],
'bugfix-hotfix': ['workflow-lite-plan'],
'feature': ['workflow-lite-plan', 'workflow-test-fix'],
'bugfix': ['workflow-lite-planex', 'workflow-test-fix'],
'bugfix-hotfix': ['workflow-lite-planex'],
'feature': ['workflow-lite-planex', 'workflow-test-fix'],
'feature-complex': ['workflow-plan', 'workflow-execute', 'workflow-test-fix'],
'refactor': ['workflow:refactor-cycle'],
'tdd': ['workflow-tdd-plan', 'workflow-execute'],
'test': ['workflow-test-fix'],
'test-fix': ['workflow-test-fix'],
'review': ['review-cycle'],
'docs': ['workflow-lite-plan']
'docs': ['workflow-lite-planex']
};
```

View File

@@ -545,8 +545,8 @@ CONSTRAINTS: ${perspective.constraints}
3. **Post-Completion Options** (⚠️ TERMINAL — analyze-with-file ends after user selection)
> **WORKFLOW BOUNDARY**: After user selects any option below, the analyze-with-file workflow is **COMPLETE**.
> If "生成任务" is selected, workflow-lite-plan takes over exclusively — do NOT return to any analyze-with-file phase.
> The "Phase" numbers in workflow-lite-plan (Phase 1-5) are SEPARATE from analyze-with-file phases.
> If "生成任务" is selected, workflow-lite-planex takes over exclusively — do NOT return to any analyze-with-file phase.
> The "Phase" numbers in workflow-lite-planex (Phase 1-5) are SEPARATE from analyze-with-file phases.
```javascript
const hasActionableRecs = conclusions.recommendations?.some(r => r.priority === 'high' || r.priority === 'medium')
@@ -557,7 +557,7 @@ CONSTRAINTS: ${perspective.constraints}
header: "Next Step",
multiSelect: false,
options: [
{ label: hasActionableRecs ? "生成任务 (Recommended)" : "生成任务", description: "Launch workflow-lite-plan with analysis context" },
{ label: hasActionableRecs ? "生成任务 (Recommended)" : "生成任务", description: "Launch workflow-lite-planex with analysis context" },
{ label: "创建Issue", description: "Launch issue-discover with conclusions" },
{ label: "导出报告", description: "Generate standalone analysis report" },
{ label: "完成", description: "No further action" }
@@ -590,7 +590,7 @@ CONSTRAINTS: ${perspective.constraints}
}
// 3. Hand off to lite-plan — analyze-with-file COMPLETE, do NOT return to any analyze phase
Skill(skill="workflow-lite-plan", args=`"${taskDescription}\n\n${contextLines.join('\n')}"`)
Skill(skill="workflow-lite-planex", args=`"${taskDescription}\n\n${contextLines.join('\n')}"`)
return // ⛔ analyze-with-file terminates here
}
```
@@ -769,7 +769,7 @@ User agrees with current direction, wants deeper code analysis
- Quick information gathering without multi-round iteration
- Follow-up analysis building on existing session
**Use `Skill(skill="workflow-lite-plan", args="\"task description\"")` when:**
**Use `Skill(skill="workflow-lite-planex", args="\"task description\"")` when:**
- Ready to implement (past analysis phase)
- Need simple task breakdown
- Focus on quick execution planning

View File

@@ -769,7 +769,7 @@ See full markdown template in original file (lines 955-1161).
- Want shared collaborative planning document
- Need structured task breakdown with agent coordination
**Use `Skill(skill="workflow-lite-plan", args="\"task description\"")` when:**
**Use `Skill(skill="workflow-lite-planex", args="\"task description\"")` when:**
- Direction is already clear
- Ready to move from ideas to execution
- Need simple implementation breakdown

View File

@@ -651,6 +651,6 @@ if (autoYes) {
| Empty debug.log | Verify reproduction triggered the code path |
| All hypotheses rejected | Use Gemini to generate new hypotheses based on disproven assumptions |
| Fix doesn't work | Document failed fix attempt, iterate with refined understanding |
| >5 iterations | Review consolidated understanding, escalate to `workflow-lite-plan` skill with full context |
| >5 iterations | Review consolidated understanding, escalate to `workflow-lite-planex` skill with full context |
| Gemini unavailable | Fallback to manual hypothesis generation, document without Gemini insights |
| Understanding too long | Consolidate aggressively, archive old iterations to separate file |

View File

@@ -827,7 +827,7 @@ AskUserQuestion({
- Need regression-safe iterative refactoring with rollback
- Want documented reasoning for each refactoring decision
**Use `workflow-lite-plan` skill when:**
**Use `workflow-lite-planex` skill when:**
- Single specific bug or issue to fix
- No systematic debt analysis needed

View File

@@ -534,10 +534,10 @@ ${selectedMode === 'progressive' ? `**Progressive Mode**:
| Scenario | Recommended Command |
|----------|-------------------|
| Strategic planning, need issue tracking | `/workflow:roadmap-with-file` |
| Quick task breakdown, immediate execution | `/workflow-lite-plan` |
| Quick task breakdown, immediate execution | `/workflow-lite-planex` |
| Collaborative multi-agent planning | `/workflow:collaborative-plan-with-file` |
| Full specification documents | `spec-generator` skill |
| Code implementation from existing plan | `/workflow:lite-execute` |
| Code implementation from existing plan | `/workflow-lite-planex` (Phase 1: plan → Phase 2: execute) |
---

View File

@@ -45,9 +45,9 @@ const COMMAND_TO_SKILL_MAP = {
// workflow commands → skills
'/workflow-plan': 'workflow-plan',
'/workflow-execute': 'workflow-execute',
'/workflow-lite-plan': 'workflow-lite-plan',
'/workflow:lite-execute': 'workflow-lite-plan', // lite-execute is part of lite-plan skill
'/workflow:lite-fix': 'workflow-lite-plan', // lite-fix is part of lite-plan skill
'/workflow-lite-planex': 'workflow-lite-planex',
'/workflow:lite-execute': 'workflow-lite-planex', // lite-execute is part of lite-plan skill
'/workflow:lite-fix': 'workflow-lite-planex', // lite-fix is part of lite-plan skill
'/workflow-multi-cli-plan': 'workflow-multi-cli-plan',
'/workflow-plan-verify': 'workflow-plan', // plan-verify is a phase of workflow-plan
'/workflow:replan': 'workflow-plan', // replan is a phase of workflow-plan
@@ -87,7 +87,7 @@ const COMMAND_TO_SKILL_MAP = {
// general commands
'/ccw-debug': null, // deleted, no replacement
'/ccw view': null, // deleted, no replacement
'/workflow:lite-lite-lite': 'workflow-lite-plan',
'/workflow:lite-lite-lite': 'workflow-lite-planex',
// ui-design (these still exist as commands)
'/workflow:ui-design:auto': '/workflow:ui-design:explore-auto',
'/workflow:ui-design:update': '/workflow:ui-design:generate',
@@ -302,8 +302,8 @@ function fixBrokenReferences() {
"skill='compact'": "skill='memory-capture'",
'skill="workflow:brainstorm:role-analysis"': 'skill="brainstorm"',
"skill='workflow:brainstorm:role-analysis'": "skill='brainstorm'",
'skill="workflow:lite-execute"': 'skill="workflow-lite-plan"',
"skill='workflow:lite-execute'": "skill='workflow-lite-plan'",
'skill="workflow:lite-execute"': 'skill="workflow-lite-planex"',
"skill='workflow:lite-execute'": "skill='workflow-lite-planex'",
};
for (const [oldCall, newCall] of Object.entries(skillCallFixes)) {
@@ -321,8 +321,8 @@ function fixBrokenReferences() {
const proseRefFixes = {
'`/workflow-plan`': '`workflow-plan` skill',
'`/workflow-execute`': '`workflow-execute` skill',
'`/workflow:lite-execute`': '`workflow-lite-plan` skill',
'`/workflow:lite-fix`': '`workflow-lite-plan` skill',
'`/workflow:lite-execute`': '`workflow-lite-planex` skill',
'`/workflow:lite-fix`': '`workflow-lite-planex` skill',
'`/workflow-plan-verify`': '`workflow-plan` skill (plan-verify phase)',
'`/workflow:replan`': '`workflow-plan` skill (replan phase)',
'`/workflow-tdd-plan`': '`workflow-tdd-plan` skill',
@@ -347,8 +347,8 @@ function fixBrokenReferences() {
'`/workflow:ui-design:auto`': '`/workflow:ui-design:explore-auto`',
'`/workflow:ui-design:update`': '`/workflow:ui-design:generate`',
'`/workflow-multi-cli-plan`': '`workflow-multi-cli-plan` skill',
'`/workflow-lite-plan`': '`workflow-lite-plan` skill',
'`/cli:plan`': '`workflow-lite-plan` skill',
'`/workflow-lite-planex`': '`workflow-lite-planex` skill',
'`/cli:plan`': '`workflow-lite-planex` skill',
'`/test-cycle-execute`': '`workflow-test-fix` skill',
};

View File

@@ -361,17 +361,6 @@
"difficulty": "Intermediate",
"source": "../../commands/workflow/init.md"
},
{
"name": "lite-execute",
"command": "/workflow:lite-execute",
"description": "Execute tasks based on in-memory plan, prompt description, or file content",
"arguments": "[-y|--yes] [--in-memory] [\\\"task description\\\"|file-path]",
"category": "workflow",
"subcategory": null,
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"source": "../../commands/workflow/lite-execute.md"
},
{
"name": "lite-fix",
"command": "/workflow:lite-fix",
@@ -396,8 +385,8 @@
},
{
"name": "lite-plan",
"command": "/workflow-lite-plan",
"description": "Lightweight interactive planning workflow with in-memory planning, code exploration, and execution execute to lite-execute after user confirmation",
"command": "/workflow-lite-planex",
"description": "Lightweight interactive planning and execution workflow (Phase 1: plan, Phase 2: execute) with in-memory planning, code exploration, and automatic execution after user confirmation",
"arguments": "[-y|--yes] [-e|--explore] \\\"task description\\\"|file.md",
"category": "workflow",
"subcategory": null,

View File

@@ -176,21 +176,17 @@ def build_command_relationships() -> Dict[str, Any]:
"alternatives": ["workflow:resume"],
"related": ["workflow:session:list", "workflow:status"]
},
"workflow-lite-plan": {
"calls_internally": ["workflow:lite-execute"],
"next_steps": ["workflow:lite-execute", "workflow:status"],
"workflow-lite-planex": {
"calls_internally": [],
"next_steps": ["workflow:status"],
"alternatives": ["workflow-plan"],
"prerequisites": []
},
"workflow:lite-fix": {
"next_steps": ["workflow:lite-execute", "workflow:status"],
"alternatives": ["workflow-lite-plan"],
"next_steps": ["workflow:status"],
"alternatives": ["workflow-lite-planex"],
"related": ["workflow-test-fix"]
},
"workflow:lite-execute": {
"prerequisites": ["workflow-lite-plan", "workflow:lite-fix"],
"related": ["workflow-execute", "workflow:status"]
},
"workflow:review-session-cycle": {
"prerequisites": ["workflow-execute"],
"next_steps": ["workflow:review-fix"],
@@ -213,7 +209,7 @@ def build_command_relationships() -> Dict[str, Any]:
def identify_essential_commands(all_commands: List[Dict]) -> List[Dict]:
"""Identify the most essential commands for beginners."""
essential_names = [
"workflow-lite-plan", "workflow:lite-fix", "workflow-plan",
"workflow-lite-planex", "workflow:lite-fix", "workflow-plan",
"workflow-execute", "workflow:status", "workflow:session:start",
"workflow:review-session-cycle", "cli:analyze", "cli:chat",
"memory:docs", "workflow:brainstorm:artifacts",

View File

@@ -67,7 +67,7 @@ spec-generator/
## Handoff
After Phase 6, choose execution path:
- `workflow-lite-plan` - Execute per Epic
- `workflow-lite-planex` - Execute per Epic
- `workflow:req-plan-with-file` - Roadmap decomposition
- `workflow-plan` - Full planning
- `issue:new` - Create issues per Epic

View File

@@ -210,7 +210,7 @@ AskUserQuestion({
options: [
{
label: "Execute via lite-plan",
description: "Start implementing with /workflow-lite-plan, one Epic at a time"
description: "Start implementing with /workflow-lite-planex, one Epic at a time"
},
{
label: "Create roadmap",
@@ -242,7 +242,7 @@ if (selection === "Execute via lite-plan") {
const epicContent = Read(firstMvpFile);
const title = extractTitle(epicContent); // First # heading
const description = extractSection(epicContent, "Description");
Skill(skill="workflow-lite-plan", args=`"${title}: ${description}"`)
Skill(skill="workflow-lite-planex", args=`"${title}: ${description}"`)
}
if (selection === "Full planning" || selection === "Create roadmap") {

View File

@@ -332,7 +332,7 @@ EXPLORE-001 → ANALYZE-001 → SYNTH-001
| Option | Description |
|--------|-------------|
| 创建Issue | 基于结论创建 Issue |
| 生成任务 | 启动 workflow-lite-plan 规划实施 |
| 生成任务 | 启动 workflow-lite-planex 规划实施 |
| 导出报告 | 生成独立分析报告 |
| 关闭团队 | 关闭所有 teammate 并清理 |

View File

@@ -1,27 +1,26 @@
---
name: workflow-lite-plan
description: Lightweight planning and execution skill - route to lite-plan or lite-execute with prompt enhancement. Triggers on "workflow-lite-plan", "workflow:lite-execute".
name: workflow-lite-planex
description: Lightweight planning and execution skill (Phase 1: plan, Phase 2: execute). Triggers on "workflow-lite-planex".
allowed-tools: Skill, Task, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep
---
# Workflow Lite-Plan
# Workflow Lite-Planex
Unified lightweight planning and execution skill. Routes to lite-plan (planning pipeline) or lite-execute (execution engine) based on trigger, with prompt enhancement for both modes.
Unified lightweight planning and execution skill (planex = plan + execute). Phase 1 handles planning pipeline, Phase 2 handles execution.
## Architecture Overview
```
┌─────────────────────────────────────────────────────┐
│ SKILL.md (Router + Prompt Enhancement)
│ → Detect mode → Enhance prompt → Dispatch to phase │
│ SKILL.md (Prompt Enhancement + Dispatch)
│ → Enhance prompt → Dispatch to Phase 1 (lite-plan)
└──────────────────────┬──────────────────────────────┘
┌───────────┼───────────┐
↓ ↓
┌───────────┐ ┌───────────┐
│ lite-plan │ │lite-execute│
│ Phase 1 │ │ Phase 2 │
│ Plan+Exec │─direct──→│ Standalone
│ Phase 1 │──handoff─→│ Phase 2 │
│ Plan │ │ Execute
└───────────┘ └───────────┘
```
@@ -33,24 +32,14 @@ Multi-phase execution (lite-plan → lite-execute) spans long conversations that
> The phase currently marked `in_progress` is the active execution phase — preserve its FULL content.
> Only compress phases marked `completed` or `pending`.
## Mode Detection & Routing
## Routing
```javascript
const args = $ARGUMENTS
const mode = detectMode()
Trigger `workflow-lite-planex` → dispatches to Phase 1 (lite-plan). Phase 1 internally hands off to Phase 2 (lite-execute) after plan confirmation.
function detectMode() {
if (skillName === 'workflow:lite-execute') return 'execute'
return 'plan' // default: workflow-lite-plan
}
```
**Routing Table**:
| Trigger | Mode | Phase Document | Description |
|---------|------|----------------|-------------|
| `workflow-lite-plan` | plan | [phases/01-lite-plan.md](phases/01-lite-plan.md) | Full planning pipeline (explore → plan → confirm → execute) |
| `workflow:lite-execute` | execute | [phases/02-lite-execute.md](phases/02-lite-execute.md) | Standalone execution (in-memory / prompt / file) |
| Phase | Document | Description |
|-------|----------|-------------|
| Phase 1 | [phases/01-lite-plan.md](phases/01-lite-plan.md) | Planning pipeline (explore → plan → confirm → handoff to Phase 2) |
| Phase 2 | [phases/02-lite-execute.md](phases/02-lite-execute.md) | Execution engine (internal, called by Phase 1 Phase 5) |
## Interactive Preference Collection
@@ -90,25 +79,6 @@ if (autoYes) {
autoYes: prefResponse.autoMode === 'Auto',
forceExplore: prefResponse.exploration === 'Force explore'
}
} else if (mode !== 'plan') {
// Execute mode (standalone, not in-memory)
const prefResponse = AskUserQuestion({
questions: [
{
question: "是否跳过所有确认步骤(自动模式)?",
header: "Auto Mode",
multiSelect: false,
options: [
{ label: "Interactive (Recommended)", description: "交互模式,包含确认步骤" },
{ label: "Auto", description: "跳过所有确认,自动执行" }
]
}
]
})
workflowPreferences = {
autoYes: prefResponse.autoMode === 'Auto',
forceExplore: false
}
}
```
@@ -125,12 +95,9 @@ Bash('ccw spec load --category planning')
// Step 2: Log available context
console.log('Project context loaded via: ccw spec load --category planning')
// Step 3: Dispatch to phase (workflowPreferences available as context)
if (mode === 'plan') {
// Read phases/01-lite-plan.md and execute
} else {
// Read phases/02-lite-execute.md and execute
}
// Step 3: Dispatch to Phase 1 (workflowPreferences available as context)
// Read phases/01-lite-plan.md and execute
// Phase 1 internally hands off to Phase 2 (lite-execute) after plan confirmation
```
## Execution Flow
@@ -145,21 +112,11 @@ if (mode === 'plan') {
5. lite-plan Phase 5 directly reads and executes Phase 2 (lite-execute) with executionContext
```
### Execute Mode
```
1. Collect preferences via AskUserQuestion (autoYes)
2. Enhance prompt with project context availability
3. Read phases/02-lite-execute.md
4. Execute lite-execute pipeline (input detection → execution → review)
```
## Usage
Plan mode and execute mode are triggered by skill name routing (see Mode Detection). Workflow preferences (auto mode, force explore) are collected interactively via AskUserQuestion before dispatching to phases.
Task description provided as arguments → interactive preference collection → planning pipeline → execution.
**Plan mode**: Task description provided as arguments → interactive preference collection → planning pipeline
**Execute mode**: Task description, file path, or in-memory context → interactive preference collection → execution pipeline
**Plan mode only**: lite-plan handles planning (Phase 1) and automatically hands off to lite-execute (Phase 2) for execution. There is no standalone execute mode.
## Phase Reference Documents

View File

@@ -1,27 +1,26 @@
---
name: workflow-multi-cli-plan
description: Multi-CLI collaborative planning and execution skill - route to multi-cli-plan or lite-execute with prompt enhancement. Triggers on "workflow-multi-cli-plan", "workflow:lite-execute".
description: Multi-CLI collaborative planning and execution skill with integrated execution phase. Triggers on "workflow-multi-cli-plan".
allowed-tools: Skill, Task, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep, mcp__ace-tool__search_context
---
# Workflow Multi-CLI Plan
Unified multi-CLI collaborative planning and execution skill. Routes to multi-cli-plan (ACE context + multi-CLI discussion + plan generation) or lite-execute (execution engine) based on trigger, with prompt enhancement for both modes.
Unified multi-CLI collaborative planning and execution skill. Routes to multi-cli-plan (ACE context + multi-CLI discussion + plan generation) which then hands off to lite-execute (Phase 2) internally for execution.
## Architecture Overview
```
┌─────────────────────────────────────────────────────────┐
│ SKILL.md (Router + Prompt Enhancement) │
│ → Detect mode → Enhance prompt → Dispatch to phase │
│ → Enhance prompt → Dispatch to Phase 1
└──────────────────────┬──────────────────────────────────┘
┌───────────┼───────────┐
↓ ↓
┌──────────────┐ ┌───────────┐
│multi-cli-plan│ │lite-execute│
│ Phase 1 │ │ Phase 2 │
│ Plan+Exec │─handoff→│ Standalone
│ Phase 1 │─handoff→│ Phase 2 │
│ Plan+Exec │ │ (internal)
└──────────────┘ └───────────┘
```
@@ -29,12 +28,7 @@ Unified multi-CLI collaborative planning and execution skill. Routes to multi-cl
```javascript
const args = $ARGUMENTS
const mode = detectMode()
function detectMode() {
if (skillName === 'workflow:lite-execute') return 'execute'
return 'plan' // default: workflow-multi-cli-plan
}
const mode = 'plan' // workflow-multi-cli-plan always starts with planning
```
**Routing Table**:
@@ -42,7 +36,6 @@ function detectMode() {
| Trigger | Mode | Phase Document | Description |
|---------|------|----------------|-------------|
| `workflow-multi-cli-plan` | plan | [phases/01-multi-cli-plan.md](phases/01-multi-cli-plan.md) | Multi-CLI collaborative planning (ACE context → discussion → plan → execute) |
| `workflow:lite-execute` | execute | [phases/02-lite-execute.md](phases/02-lite-execute.md) | Standalone execution (in-memory / prompt / file) |
## Interactive Preference Collection
@@ -72,24 +65,6 @@ if (autoYes) {
workflowPreferences = {
autoYes: prefResponse.autoMode === 'Auto'
}
} else {
// Execute mode
const prefResponse = AskUserQuestion({
questions: [
{
question: "是否跳过所有确认步骤(自动模式)?",
header: "Auto Mode",
multiSelect: false,
options: [
{ label: "Interactive (Recommended)", description: "交互模式,包含确认步骤" },
{ label: "Auto", description: "跳过所有确认,自动执行" }
]
}
]
})
workflowPreferences = {
autoYes: prefResponse.autoMode === 'Auto'
}
}
```
@@ -106,12 +81,9 @@ Bash('ccw spec load --category planning')
// Step 2: Log available context
console.log('Project context loaded via: ccw spec load --category planning')
// Step 3: Dispatch to phase (workflowPreferences available as context)
if (mode === 'plan') {
// Read phases/01-multi-cli-plan.md and execute
} else {
// Read phases/02-lite-execute.md and execute
}
// Step 3: Dispatch to Phase 1 (workflowPreferences available as context)
// Read phases/01-multi-cli-plan.md and execute
// Phase 1 internally hands off to Phase 2 (lite-execute) after plan approval
```
## Compact Recovery (Phase Persistence)
@@ -134,21 +106,9 @@ Multi-phase execution (multi-cli-plan → lite-execute) spans long conversations
5. Phase 5 directly reads and executes Phase 2 (lite-execute) with executionContext
```
### Execute Mode (workflow:lite-execute)
```
1. Collect preferences via AskUserQuestion (autoYes)
2. Enhance prompt with project context availability
3. Read phases/02-lite-execute.md
4. Execute lite-execute pipeline (input detection → execution → review)
```
## Usage
Plan mode and execute mode are triggered by skill name routing (see Mode Detection). Workflow preferences (auto mode) are collected interactively via AskUserQuestion before dispatching to phases.
**Plan mode**: Task description provided as arguments → interactive preference collection → multi-CLI planning pipeline
**Execute mode**: Task description, file path, or in-memory context → interactive preference collection → execution pipeline
Task description provided as arguments → interactive preference collection → multi-CLI planning pipeline → internal execution handoff to Phase 2 (lite-execute).
## Phase Reference Documents

View File

@@ -24,7 +24,7 @@ When `workflowPreferences.autoYes` is true: Auto-approve plan, use recommended s
**Output Directory**: `.workflow/.multi-cli-plan/{session-id}/`
**Default Max Rounds**: 3 (convergence may complete earlier)
**CLI Tools**: @cli-discuss-agent (analysis), @cli-lite-planning-agent (plan generation)
**Execution**: Auto-hands off to `/workflow:lite-execute --in-memory` after plan approval
**Execution**: Auto-hands off to Phase 2 (lite-execute) after plan approval
## What & Why
@@ -81,7 +81,7 @@ Phase 4: User Decision
Phase 5: Plan Generation & Execution Handoff
├─ Generate plan.json + .task/*.json (via @cli-lite-planning-agent, two-layer output)
├─ Build executionContext with user selections and taskFiles
└─ Execute to /workflow:lite-execute --in-memory
└─ Execute via Phase 2 (lite-execute)
```
### Agent Roles
@@ -598,7 +598,7 @@ TodoWrite({ todos: [
```bash
# Simpler single-round planning
/workflow-lite-plan "task description"
/workflow-lite-planex "task description"
# Issue-driven discovery
/issue:discover-by-prompt "find issues"
@@ -609,7 +609,7 @@ cat .workflow/.multi-cli-plan/{session-id}/rounds/1/synthesis.json
cat .workflow/.multi-cli-plan/{session-id}/context-package.json
# Direct execution (if you have plan.json)
/workflow:lite-execute plan.json
# Use workflow-lite-planex or workflow-multi-cli-plan (execution is integrated)
```
## Next Phase

View File

@@ -26,22 +26,13 @@ Flexible task execution command supporting three input modes: in-memory plan (fr
## Usage
### Command Syntax
```bash
/workflow:lite-execute [FLAGS] <INPUT>
# Flags
--in-memory Use plan from memory (called by lite-plan)
# Arguments
<input> Task description string, or path to file (required)
```
> **Note**: This is an internal phase, not a standalone command. It is called by Phase 1 (multi-cli-plan) after plan approval, or by lite-plan after Phase 4 approval.
## Input Modes
### Mode 1: In-Memory Plan
**Trigger**: Called by lite-plan after Phase 4 approval with `--in-memory` flag
**Trigger**: Called by multi-cli-plan Phase 5 after plan approval, or by lite-plan after Phase 4 approval
**Input Source**: `executionContext` global variable set by lite-plan

View File

@@ -141,7 +141,7 @@ Read("phases/02-lite-execute.md")
// Execute with executionContext (Mode 1)
// WRONG: Skill routing (unnecessary round-trip)
Skill(skill="workflow-lite-plan", args="--in-memory")
Skill(skill="workflow-lite-planex", args="--in-memory")
```
### Pattern 8: Phase File Hygiene

View File

@@ -60,7 +60,7 @@ Read("phases/02-lite-execute.md")
// Execute with executionContext (Mode 1)
// WRONG: Skill routing (unnecessary round-trip)
Skill(skill="workflow-lite-plan", args="--in-memory")
Skill(skill="workflow-lite-planex", args="--in-memory")
```
### Content Restriction Enforcement

View File

@@ -204,7 +204,7 @@ Brief summary:
## Post-Exploration: Exploration Notes (Generated by Orchestrator)
**Note**: This section is executed by the orchestrator (workflow-lite-plan) after all cli-explore-agents complete, NOT by this agent.
**Note**: This section is executed by the orchestrator (workflow-lite-planex) after all cli-explore-agents complete, NOT by this agent.
**Trigger**: After all exploration-{angle}.json files are generated

View File

@@ -800,7 +800,7 @@ Offer user follow-up actions based on brainstorming results.
| Option | Purpose | Action |
|--------|---------|--------|
| **创建实施计划** | Plan implementation of top idea | Launch `workflow-lite-plan` |
| **创建实施计划** | Plan implementation of top idea | Launch `workflow-lite-planex` |
| **创建Issue** | Track top ideas for later | Launch `issue:new` with ideas |
| **深入分析** | Analyze top idea in detail | Launch `workflow:analyze-with-file` |
| **导出分享** | Generate shareable report | Create formatted report document |

View File

@@ -903,4 +903,4 @@ Wave 3 agents:
| Linear pipeline (A→B→C) | `$csv-wave-pipeline -c 1` — 3 waves, serial, full context |
| Diamond dependency (A→B,C→D) | `$csv-wave-pipeline` — 3 waves, B+C concurrent in wave 2 |
| Complex requirement, unclear tasks | Use `$roadmap-with-file` first for planning, then feed issues here |
| Single complex task | Use `$lite-execute` instead |
| Single complex task | Use `$workflow-lite-planex` instead |

View File

@@ -896,4 +896,4 @@ To execute later:
| Quick task breakdown, immediate execution | `$lite-plan` |
| Collaborative multi-agent planning | `$collaborative-plan-with-file` |
| Full specification documents | `$spec-generator` |
| Code implementation from existing plan | `$lite-execute` |
| Code implementation from existing plan | `$workflow-lite-planex` |

View File

@@ -93,7 +93,7 @@ CCW uses two types of invocations:
| Type | Format | Examples |
|------|--------|----------|
| **Skills** | Trigger phrase (no slash) | `workflow-lite-plan`, `brainstorm`, `workflow-plan` |
| **Skills** | Trigger phrase (no slash) | `workflow-lite-planex`, `brainstorm`, `workflow-plan` |
| **Commands** | Slash command | `/ccw`, `/workflow/session:start`, `/issue/new` |
### Choose Your Workflow Skill
@@ -101,7 +101,7 @@ CCW uses two types of invocations:
<div align="center">
<table>
<tr><th>Skill Trigger</th><th>Use Case</th></tr>
<tr><td><code>workflow-lite-plan</code></td><td>Lightweight planning, single-module features</td></tr>
<tr><td><code>workflow-lite-planex</code></td><td>Lightweight planning, single-module features</td></tr>
<tr><td><code>workflow-multi-cli-plan</code></td><td>Multi-CLI collaborative analysis</td></tr>
<tr><td><code>workflow-plan</code></td><td>Full planning with session persistence</td></tr>
<tr><td><code>workflow-tdd-plan</code></td><td>Test-driven development</td></tr>
@@ -114,7 +114,7 @@ CCW uses two types of invocations:
```bash
# Skill triggers (no slash - just describe what you want)
workflow-lite-plan "Add JWT authentication"
workflow-lite-planex "Add JWT authentication"
workflow-plan "Implement payment gateway integration"
workflow-execute
@@ -278,7 +278,7 @@ ccw upgrade -a # Upgrade all installations
```
┌─────────────────────────────────────────────────────────────────┐
│ Workflow Skills │
│ 📝 workflow-lite-plan / workflow-multi-cli-plan (lightweight) │
│ 📝 workflow-lite-planex / workflow-multi-cli-plan (lightweight) │
│ 📊 workflow-plan / workflow-tdd-plan (session-based) │
│ 🧪 workflow-test-fix / workflow-test-fix │
│ 🧠 brainstorm (multi-role analysis) │
@@ -322,7 +322,7 @@ Claude-Code-Workflow/
│ │ ├── memory/ # Memory commands (prepare, style-skill-memory)
│ │ └── workflow/ # Workflow commands (session, ui-design, etc.)
│ └── skills/ # 37 modular skills
│ ├── workflow-lite-plan/
│ ├── workflow-lite-planex/
│ ├── workflow-plan/
│ ├── workflow-tdd-plan/
│ ├── workflow-test-fix/

View File

@@ -93,7 +93,7 @@ CCW 使用两种调用方式:
| 类型 | 格式 | 示例 |
|------|------|------|
| **Skills** | 触发短语(无斜杠) | `workflow-lite-plan`, `brainstorm`, `workflow-plan` |
| **Skills** | 触发短语(无斜杠) | `workflow-lite-planex`, `brainstorm`, `workflow-plan` |
| **Commands** | 斜杠命令 | `/ccw`, `/workflow/session:start`, `/issue/new` |
### 选择工作流 Skill
@@ -101,7 +101,7 @@ CCW 使用两种调用方式:
<div align="center">
<table>
<tr><th>Skill 触发词</th><th>使用场景</th></tr>
<tr><td><code>workflow-lite-plan</code></td><td>轻量规划、单模块功能</td></tr>
<tr><td><code>workflow-lite-planex</code></td><td>轻量规划、单模块功能</td></tr>
<tr><td><code>workflow-multi-cli-plan</code></td><td>多 CLI 协同分析</td></tr>
<tr><td><code>workflow-plan</code></td><td>完整规划与会话持久化</td></tr>
<tr><td><code>workflow-tdd-plan</code></td><td>测试驱动开发</td></tr>
@@ -114,7 +114,7 @@ CCW 使用两种调用方式:
```bash
# Skill 触发(无斜杠 - 直接描述你想做什么)
workflow-lite-plan "添加 JWT 认证"
workflow-lite-planex "添加 JWT 认证"
workflow-plan "实现支付网关集成"
workflow-execute
@@ -278,7 +278,7 @@ ccw upgrade -a # 升级所有安装
```
┌─────────────────────────────────────────────────────────────────┐
│ 工作流 Skills │
│ 📝 workflow-lite-plan / workflow-multi-cli-plan (轻量级) │
│ 📝 workflow-lite-planex / workflow-multi-cli-plan (轻量级) │
│ 📊 workflow-plan / workflow-tdd-plan (会话式) │
│ 🧪 workflow-test-fix / workflow-test-fix │
│ 🧠 brainstorm (多角色分析) │
@@ -322,7 +322,7 @@ Claude-Code-Workflow/
│ │ ├── memory/ # 内存命令 (prepare, style-skill-memory)
│ │ └── workflow/ # 工作流命令 (session, ui-design 等)
│ └── skills/ # 37 个模块化技能
│ ├── workflow-lite-plan/
│ ├── workflow-lite-planex/
│ ├── workflow-plan/
│ ├── workflow-tdd-plan/
│ ├── workflow-test-fix/

View File

@@ -21,7 +21,7 @@ CCW uses two types of invocations:
| Type | Format | Examples |
|------|--------|----------|
| **Skills** | Trigger phrase (no slash) | `workflow-lite-plan`, `brainstorm`, `workflow-plan` |
| **Skills** | Trigger phrase (no slash) | `workflow-lite-planex`, `brainstorm`, `workflow-plan` |
| **Commands** | Slash command | `/ccw`, `/workflow/session:start`, `/issue/new` |
---
@@ -32,8 +32,7 @@ CCW uses two types of invocations:
| Skill Trigger | Purpose | Phases |
|---------------|---------|--------|
| `workflow-lite-plan` | Lightweight planning with exploration | 5 phases |
| `workflow:lite-execute` | Execute lite-plan output | Execution |
| `workflow-lite-planex` | Lightweight planning with exploration (includes execution) | 5 phases |
**5-Phase Interactive Workflow**:
```
@@ -232,7 +231,7 @@ Phase 6: Next cycle
| Skill | Trigger |
|-------|---------|
| workflow-lite-plan | `workflow-lite-plan`, `workflow:lite-execute` |
| workflow-lite-planex | `workflow-lite-planex` |
| workflow-multi-cli-plan | `workflow-multi-cli-plan` |
| workflow-plan | `workflow-plan`, `workflow-plan-verify`, `workflow:replan` |
| workflow-execute | `workflow-execute` |
@@ -293,10 +292,10 @@ New System ─┼────────────┼─────
Start
├─ Is it a quick fix or config change?
│ └─> Yes: workflow-lite-plan
│ └─> Yes: workflow-lite-planex
├─ Is it a single module feature?
│ └─> Yes: workflow-lite-plan
│ └─> Yes: workflow-lite-planex
├─ Does it need multi-CLI analysis?
│ └─> Yes: workflow-multi-cli-plan
@@ -348,7 +347,7 @@ Start
| Skill | When to Use |
|-------|-------------|
| `workflow-lite-plan` | Quick fixes, single features |
| `workflow-lite-planex` | Quick fixes, single features |
| `workflow-plan` | Multi-module development |
| `brainstorm` | Architecture, new features |
| `workflow-execute` | Execute planned work |

View File

@@ -22,7 +22,7 @@ CCW 使用两种调用方式:
| 类型 | 格式 | 示例 |
|------|------|------|
| **Skills** | 触发短语(无斜杠) | `workflow-lite-plan`, `brainstorm`, `workflow-plan` |
| **Skills** | 触发短语(无斜杠) | `workflow-lite-planex`, `brainstorm`, `workflow-plan` |
| **Commands** | 斜杠命令 | `/ccw`, `/workflow/session:start`, `/issue/new` |
---
@@ -33,8 +33,7 @@ CCW 使用两种调用方式:
| Skill 触发词 | 用途 | 阶段 |
|--------------|------|------|
| `workflow-lite-plan` | 轻量规划与探索 | 5 阶段 |
| `workflow:lite-execute` | 执行 lite-plan 输出 | 执行 |
| `workflow-lite-planex` | 轻量规划与探索(包含执行) | 5 阶段 |
**5 阶段交互式工作流**
```
@@ -233,7 +232,7 @@ CCW 使用两种调用方式:
| Skill | 触发词 |
|-------|--------|
| workflow-lite-plan | `workflow-lite-plan`, `workflow:lite-execute` |
| workflow-lite-planex | `workflow-lite-planex` |
| workflow-multi-cli-plan | `workflow-multi-cli-plan` |
| workflow-plan | `workflow-plan`, `workflow-plan-verify`, `workflow:replan` |
| workflow-execute | `workflow-execute` |
@@ -294,10 +293,10 @@ CCW 使用两种调用方式:
开始
├─ 是快速修复或配置变更?
│ └─> 是workflow-lite-plan
│ └─> 是workflow-lite-planex
├─ 是单模块功能?
│ └─> 是workflow-lite-plan
│ └─> 是workflow-lite-planex
├─ 需要多 CLI 分析?
│ └─> 是workflow-multi-cli-plan
@@ -349,7 +348,7 @@ CCW 使用两种调用方式:
| Skill | 何时使用 |
|-------|----------|
| `workflow-lite-plan` | 快速修复、单功能 |
| `workflow-lite-planex` | 快速修复、单功能 |
| `workflow-plan` | 多模块开发 |
| `brainstorm` | 架构、新功能 |
| `workflow-execute` | 执行已规划的工作 |

View File

@@ -225,7 +225,7 @@ invalid yaml content without colons
expect(result).toEqual({
name: 'lite-plan',
command: '/workflow-lite-plan',
command: '/workflow-lite-planex',
description: 'Quick planning for simple features',
argumentHint: '"feature description"',
allowedTools: ['Task(*)', 'Read(*)', 'Write(*)', 'Bash(*)'],
@@ -239,7 +239,7 @@ invalid yaml content without colons
mockReadFileSync.mockReturnValue(sampleLitePlanYaml);
const registry = new CommandRegistry(cmdDir);
const result = registry.getCommand('/workflow-lite-plan');
const result = registry.getCommand('/workflow-lite-planex');
expect(result?.name).toBe('lite-plan');
});
@@ -330,7 +330,7 @@ description: Minimal command
const result = registry.getCommands(['lite-plan', 'execute', 'nonexistent']);
expect(result.size).toBe(2);
expect(result.has('/workflow-lite-plan')).toBe(true);
expect(result.has('/workflow-lite-planex')).toBe(true);
expect(result.has('/workflow-execute')).toBe(true);
});
@@ -362,7 +362,7 @@ description: Minimal command
const result = registry.getAllCommandsSummary();
expect(result.size).toBe(3);
expect(result.get('/workflow-lite-plan')).toEqual({
expect(result.get('/workflow-lite-planex')).toEqual({
name: 'lite-plan',
description: 'Quick planning for simple features'
});
@@ -483,9 +483,9 @@ allowed-tools: Task(*)
const json = registry.toJSON();
expect(json['/workflow-lite-plan']).toEqual({
expect(json['/workflow-lite-planex']).toEqual({
name: 'lite-plan',
command: '/workflow-lite-plan',
command: '/workflow-lite-planex',
description: 'Quick planning for simple features',
argumentHint: '"feature description"',
allowedTools: ['Task(*)', 'Read(*)', 'Write(*)', 'Bash(*)'],
@@ -508,7 +508,7 @@ allowed-tools: Task(*)
const json = registry.toJSON();
expect(Object.keys(json).length).toBe(1);
expect(json['/workflow-lite-plan']).toBeDefined();
expect(json['/workflow-lite-planex']).toBeDefined();
expect(json['/workflow-execute']).toBeUndefined();
});
});

View File

@@ -118,7 +118,7 @@ export class CommandRegistry {
/**
* Get single command metadata
* @param commandName Command name (e.g., "lite-plan" or "/workflow-lite-plan")
* @param commandName Command name (e.g., "lite-plan" or "/workflow-lite-planex")
* @returns Command metadata or null
*/
public getCommand(commandName: string): CommandMetadata | null {

View File

@@ -30,8 +30,7 @@
| 命令 | 功能 | 难度 |
| --- | --- | --- |
| [`/workflow:lite-lite-lite`](./workflow.md#lite-lite-lite) | 超轻量级多工具分析和直接执行 | Intermediate |
| [`/workflow-lite-plan`](./workflow.md#lite-plan) | 轻量级交互式规划工作流 | Intermediate |
| [`/workflow:lite-execute`](./workflow.md#lite-execute) | 基于内存计划执行任务 | Intermediate |
| [`/workflow-lite-planex`](./workflow.md#lite-plan) | 轻量级交互式规划工作流 | Intermediate |
| [`/workflow:lite-fix`](./workflow.md#lite-fix) | 轻量级 Bug 诊断和修复 | Intermediate |
| [`/workflow-plan`](./workflow.md#plan) | 5 阶段规划工作流 | Intermediate |
| [`/workflow-execute`](./workflow.md#execute) | 协调代理执行工作流任务 | Intermediate |

View File

@@ -45,9 +45,9 @@ High-level orchestrators for complex, multi-phase development processes.
/workflow-plan "Create a simple Express API that returns Hello World"
```
### **/workflow-lite-plan** ⚡ NEW
### **/workflow-lite-planex** ⚡ NEW
- **Syntax**: `/workflow-lite-plan [--tool claude|gemini|qwen|codex] [-e|--explore] "task description"|file.md`
- **Syntax**: `/workflow-lite-planex [--tool claude|gemini|qwen|codex] [-e|--explore] "task description"|file.md`
- **Parameters**:
- `--tool` (Optional, String): Preset CLI tool for execution (claude|gemini|qwen|codex). If not provided, user selects during confirmation.
- `-e, --explore` (Optional, Flag): Force code exploration phase (overrides auto-detection logic).
@@ -74,13 +74,13 @@ High-level orchestrators for complex, multi-phase development processes.
- **Example**:
```bash
# Basic usage with auto-detection
/workflow-lite-plan "Add JWT authentication to user login"
/workflow-lite-planex "Add JWT authentication to user login"
# Force code exploration
/workflow-lite-plan -e "Refactor logging module for better performance"
/workflow-lite-planex -e "Refactor logging module for better performance"
# Basic usage
/workflow-lite-plan "Add unit tests for auth service"
/workflow-lite-planex "Add unit tests for auth service"
```
### **/workflow-execute**
@@ -202,7 +202,7 @@ CLI tool configuration commands.
/cli:cli-init
```
> **Note**: For analysis, planning, and bug fixing, use workflow commands (`/workflow-lite-plan`, `/workflow:lite-fix`) or semantic invocation through natural language. Claude will automatically use appropriate CLI tools (Gemini/Qwen/Codex) with templates as needed.
> **Note**: For analysis, planning, and bug fixing, use workflow commands (`/workflow-lite-planex`, `/workflow:lite-fix`) or semantic invocation through natural language. Claude will automatically use appropriate CLI tools (Gemini/Qwen/Codex) with templates as needed.
---

View File

@@ -31,7 +31,7 @@ Complete reference for all **43 CCW commands** organized by category, with **7 w
- `-y, --yes` - Skip all confirmations
**Mapped Skills**:
- workflow-lite-plan, workflow-plan, workflow-execute, workflow-tdd-plan
- workflow-lite-planex, workflow-plan, workflow-execute, workflow-tdd-plan
- workflow-test-fix, workflow-multi-cli-plan, review-cycle, brainstorm
- team-planex, team-iterdev, team-lifecycle, team-issue
- team-testing, team-quality-assurance, team-brainstorm, team-uidesign

View File

@@ -88,9 +88,9 @@ graph TD
| Unit Name | Command Chain | Output |
|-----------|---------------|--------|
| **Quick Implementation** | lite-plan -> lite-execute | Working code |
| **Multi-CLI Planning** | multi-cli-plan -> lite-execute | Working code |
| **Bug Fix** | lite-plan (--bugfix) -> lite-execute | Fixed code |
| **Quick Implementation** | lite-plan (Phase 1: plan → Phase 2: execute) | Working code |
| **Multi-CLI Planning** | multi-cli-plan (Phase 1: plan → Phase 2: execute) | Working code |
| **Bug Fix** | lite-plan --bugfix (Phase 1: plan → Phase 2: execute) | Fixed code |
| **Full Plan+Execute** | plan -> execute | Working code |
| **Verified Plan+Execute** | plan -> plan-verify -> execute | Working code |
| **TDD Plan+Execute** | tdd-plan -> execute | Working code |
@@ -143,7 +143,7 @@ Both commands support the `--yes` flag for auto mode:
| Skill | Function |
|-------|----------|
| `workflow-lite-plan` | Lightweight planning workflow |
| `workflow-lite-planex` | Lightweight planning workflow |
| `workflow-plan` | Full planning workflow |
| `workflow-execute` | Execution workflow |
| `workflow-tdd-plan` | TDD workflow |

View File

@@ -31,8 +31,7 @@
| Command | Function | Difficulty |
|---------|----------|------------|
| [`/workflow:lite-lite-lite`](./workflow.md#lite-lite-lite) | Ultra-lightweight multi-tool analysis and direct execution | Intermediate |
| [`/workflow-lite-plan`](./workflow.md#lite-plan) | Lightweight interactive planning workflow | Intermediate |
| [`/workflow:lite-execute`](./workflow.md#lite-execute) | Execute tasks based on in-memory plan | Intermediate |
| [`/workflow-lite-planex`](./workflow.md#lite-plan) | Lightweight interactive planning workflow | Intermediate |
| [`/workflow:lite-fix`](./workflow.md#lite-fix) | Lightweight bug diagnosis and fix | Intermediate |
| [`/workflow-plan`](./workflow.md#plan) | 5-phase planning workflow | Intermediate |
| [`/workflow-execute`](./workflow.md#execute) | Coordinate agent execution of workflow tasks | Intermediate |

View File

@@ -11,8 +11,7 @@
| Command | Function | Syntax |
|---------|----------|--------|
| [`lite-lite-lite`](#lite-lite-lite) | Ultra-lightweight multi-tool analysis and direct execution | `/workflow:lite-lite-lite [-y] <task>` |
| [`lite-plan`](#lite-plan) | Lightweight interactive planning workflow | `/workflow-lite-plan [-y] [-e] "task"` |
| [`lite-execute`](#lite-execute) | Execute tasks based on in-memory plan | `/workflow:lite-execute [-y] [--in-memory] [task]` |
| [`lite-plan`](#lite-plan) | Lightweight interactive planning workflow | `/workflow-lite-planex [-y] [-e] "task"` |
| [`lite-fix`](#lite-fix) | Lightweight bug diagnosis and fix | `/workflow:lite-fix [-y] [--hotfix] "bug description"` |
### Standard Workflows
@@ -92,11 +91,11 @@
### lite-plan
**Function**: Lightweight interactive planning workflow, supporting in-memory planning, code exploration, and execution to lite-execute.
**Function**: Lightweight interactive planning and execution workflow (Phase 1: plan, Phase 2: execute), supporting in-memory planning, code exploration, and automatic execution after confirmation.
**Syntax**:
```bash
/workflow-lite-plan [-y|--yes] [-e|--explore] "task description" | file.md
/workflow-lite-planex [-y|--yes] [-e|--explore] "task description" | file.md
```
**Options**:
@@ -105,31 +104,10 @@
**Examples**:
```bash
# Basic planning
/workflow-lite-plan "add user avatar feature"
/workflow-lite-planex "add user avatar feature"
# With exploration
/workflow-lite-plan -e "refactor authentication module"
```
### lite-execute
**Function**: Execute tasks based on in-memory plan, prompt description, or file content.
**Syntax**:
```bash
/workflow:lite-execute [-y|--yes] [--in-memory] ["task description" | file-path]
```
**Options**:
- `--in-memory`: Use in-memory plan
**Examples**:
```bash
# Execute task
/workflow:lite-execute "implement avatar upload API"
# Use in-memory plan
/workflow:lite-execute --in-memory
/workflow-lite-planex -e "refactor authentication module"
```
### lite-fix

View File

@@ -21,7 +21,7 @@
| 命令 | 类型 | 输出 | 适用场景 | 特点 |
|------|------|------|----------|------|
| **workflow-plan** | 4阶段规划 | IMPL_PLAN.md, task JSONs, TODO_LIST.md | 标准功能开发 | 完整规划流程,支持冲突检测,可选验证 |
| **workflow-lite-plan** | 轻量规划 | task JSONs | 快速任务 | 精简流程,直接执行,无验证阶段 |
| **workflow-lite-planex** | 轻量规划 | task JSONs | 快速任务 | 精简流程,直接执行,无验证阶段 |
| **workflow-tdd-plan** | TDD规划 | IMPL_PLAN.md (含Red-Green-Refactor) | 测试驱动开发 | 强制TDD结构测试先行 |
| **brainstorm** | 头脑风暴 | guidance-specification.md, role分析, feature-specs | 需求探索 | 多角色分析,角色扮演,创意生成 |
| **issue:plan** | Issue规划 | solution JSON per issue | Issue驱动开发 | 批量规划,自动绑定,冲突检测 |
@@ -39,7 +39,7 @@
```
┌─────────────────┬───────────────────┬───────────────────┬───────────────────┐
│ │ workflow-plan │ workflow-lite-plan│ issue:plan │
│ │ workflow-plan │ workflow-lite-planex│ issue:plan │
├─────────────────┼───────────────────┼───────────────────┼───────────────────┤
│ 复杂度 │ 高 (4-6阶段) │ 低 (1-2阶段) │ 中 (3阶段) │
│ 验证阶段 │ ✓ (Phase 5) │ ✗ │ ✗ │
@@ -61,7 +61,7 @@
| 命令 | 类型 | 执行方式 | 适用场景 | 特点 |
|------|------|----------|----------|------|
| **workflow-execute** | 任务执行器 | code-developer agent | 规划后执行 | 会话发现,并行任务,进度跟踪 |
| **workflow-lite-plan** (执行模式) | 轻量执行 | code-developer / CLI | 快速实现 | 内置执行,无会话 |
| **workflow-lite-planex** (执行模式) | 轻量执行 | code-developer / CLI | 快速实现 | 内置执行,无会话 |
| **review-code** | 代码审查 | read-only | 质量检查 | 多维度审查,自动修复建议 |
### Team 执行 Skill
@@ -188,7 +188,7 @@ if (task_count > 3) → Codex
| 任务类型 | 推荐命令 | 备选命令 |
|----------|----------|----------|
| **新功能开发** | workflow-plan → workflow-execute | team-lifecycle-v5 |
| **快速修复** | workflow-lite-plan | issue:plan → issue:execute |
| **快速修复** | workflow-lite-planex | issue:plan → issue:execute |
| **TDD开发** | workflow-tdd-plan → workflow-execute | - |
| **需求探索** | brainstorm | team-brainstorm |
| **Issue处理** | issue:plan → issue:queue → issue:execute | team-issue |
@@ -201,7 +201,7 @@ if (task_count > 3) → Codex
| 规模 | 推荐命令 | 原因 |
|------|----------|------|
| **单人快速** | workflow-lite-plan | 轻量,直接执行 |
| **单人快速** | workflow-lite-planex | 轻量,直接执行 |
| **单人完整** | workflow-plan → workflow-execute | 完整流程,有验证 |
| **多人协作** | team-coordinate-v2 | 动态角色,灵活分工 |
| **专项团队** | team-* (按领域) | 领域专家角色 |
@@ -210,7 +210,7 @@ if (task_count > 3) → Codex
```
复杂度低 (1-2任务)
└─ workflow-lite-plan (推荐)
└─ workflow-lite-planex (推荐)
└─ issue:plan (Issue驱动)
复杂度中 (3-10任务)
@@ -258,7 +258,7 @@ tdd-plan plan issue plan brainstorm
| 命令 | 调用方式 |
|------|----------|
| workflow-plan | `Skill(skill="workflow-plan", args="任务描述")` |
| workflow-lite-plan | `Skill(skill="workflow-lite-plan", args="任务描述")` |
| workflow-lite-planex | `Skill(skill="workflow-lite-planex", args="任务描述")` |
| workflow-tdd-plan | `Skill(skill="workflow-tdd-plan", args="TDD任务描述")` |
| brainstorm | `Skill(skill="brainstorm", args="主题 --count 3")` |
| issue:plan | `/issue:plan GH-123,GH-124` |
@@ -300,7 +300,7 @@ tdd-plan plan issue plan brainstorm
|------|------|--------|
| **规划** | workflow-plan | 6阶段 |
| **执行** | workflow-execute | 6阶段 |
| **轻量** | workflow-lite-plan | 2阶段 |
| **轻量** | workflow-lite-planex | 2阶段 |
| **TDD** | workflow-tdd-plan | 7阶段 |
| **测试修复** | workflow-test-fix | 4阶段 |
| **多CLI** | workflow-multi-cli-plan | - |

View File

@@ -181,7 +181,7 @@ memory/
```bash
# Quick task
/workflow-lite-plan "Fix login bug"
/workflow-lite-planex "Fix login bug"
# Full development
/workflow-plan "Add user notifications"
@@ -234,7 +234,7 @@ memory/
- Test coverage → `team-testing`
2. **Workflow Selection**:
- Super simple → `workflow-lite-plan`
- Super simple → `workflow-lite-planex`
- Complex features → `workflow-plan``workflow-execute`
- TDD → `workflow-tdd-plan`
- Test fixes → `workflow-test-fix`

View File

@@ -19,7 +19,7 @@
|-------|----------|---------|
| `workflow-plan` | Unified planning skill (4-stage workflow) | `/workflow-plan` |
| `workflow-execute` | Agent-coordinated execution | `/workflow-execute` |
| `workflow-lite-plan` | Lightweight quick planning | `/workflow-lite-plan` |
| `workflow-lite-planex` | Lightweight quick planning | `/workflow-lite-planex` |
| `workflow-multi-cli-plan` | Multi-CLI collaborative planning | `/workflow-multi-cli-plan` |
| `workflow-tdd-plan` | TDD workflow | `/workflow-tdd-plan` |
| `workflow-test-fix` | Test-fix workflow | `/workflow-test-fix` |
@@ -182,13 +182,13 @@ Phase 5: Completion
---
### workflow-lite-plan
### workflow-lite-planex
**One-Liner**: Lightweight quick planning — Quick planning and execution for super simple tasks
**Trigger**:
```shell
/workflow-lite-plan <simple-task>
/workflow-lite-planex <simple-task>
```
**Features**:
@@ -331,7 +331,7 @@ Wave 2: Issue 6-10 → Parallel planning → Parallel execution
## Best Practices
1. **Choose the right workflow**:
- Super simple tasks → `workflow-lite-plan`
- Super simple tasks → `workflow-lite-planex`
- Complex features → `workflow-plan``workflow-execute`
- TDD development → `workflow-tdd-plan`
- Test fixes → `workflow-test-fix`

View File

@@ -679,24 +679,24 @@ Skill(skill="workflow-plan")
---
### workflow-lite-plan
### workflow-lite-planex
**Purpose**: Lightweight planning and execution skill
**Triggers**: `workflow-lite-plan`, `workflow:lite-execute`
**Triggers**: `workflow-lite-planex`
**Description**: Route to lite-plan or lite-execute with prompt enhancement.
**Description**: Unified planning and execution skill (Phase 1: plan, Phase 2: execute) with prompt enhancement.
**Phases**:
1. Phase 1: Lite Plan
2. Phase 2: Lite Execute
1. Phase 1: Lite Plan (planning pipeline)
2. Phase 2: Lite Execute (execution engine, internal)
**Modes**: `lite-plan`, `lite-execute`
**Modes**: `plan` (Phase 1 → Phase 2 automatically)
**Artifacts**: LITE_PLAN.md, execution results
```bash
Skill(skill="workflow-lite-plan")
Skill(skill="workflow-lite-planex")
```
---
@@ -707,7 +707,7 @@ Skill(skill="workflow-lite-plan")
**Triggers**: `workflow-multi-cli-plan`, `workflow:multi-cli-plan`
**Description**: Route to multi-cli-plan or lite-execute with prompt enhancement.
**Description**: Multi-CLI collaborative planning and execution skill (Phase 1: plan, Phase 2: execute) with prompt enhancement.
**Phases**:
1. Phase 1: Multi-CLI Plan (ACE context → discussion → plan → execute)
@@ -851,7 +851,7 @@ Skill(skill="review-cycle")
**Use Case**: Quick iterations and rapid prototyping
```bash
Skill(skill="workflow-lite-plan")
Skill(skill="workflow-lite-planex")
Skill(skill="workflow-execute")
```
@@ -1039,7 +1039,7 @@ Skill(skill="skill-tuning")
| Level | Skills |
|-------|--------|
| Meta Skills | skill-generator, skill-tuning, workflow-skill-designer |
| Orchestrators | workflow-plan, workflow-lite-plan, workflow-multi-cli-plan |
| Orchestrators | workflow-plan, workflow-lite-planex, workflow-multi-cli-plan |
| Executors | workflow-execute |
| Team Leads | team-lifecycle (v5) |
@@ -1085,7 +1085,7 @@ Quick reference for skill triggers:
| `manage issue` | issue-manage |
| `workflow-plan`, `workflow-plan-verify`, `workflow:replan` | workflow-plan |
| `workflow-execute` | workflow-execute |
| `workflow-lite-plan` | workflow-lite-plan |
| `workflow-lite-planex` | workflow-lite-planex |
| `workflow-multi-cli-plan`, `workflow:multi-cli-plan` | workflow-multi-cli-plan |
| `workflow-tdd-plan` | workflow-tdd-plan |
| `workflow-test-fix`, `test fix workflow` | workflow-test-fix |

View File

@@ -56,7 +56,7 @@ Skills are reusable, domain-specific capabilities that CCW can execute. Each ski
| Skill | Triggers | Description |
|-------|----------|-------------|
| [workflow-plan](./core-skills.md#workflow-plan) | `workflow-plan`, `workflow-plan-verify`, `workflow:replan` | 4-phase planning with verification |
| [workflow-lite-plan](./core-skills.md#workflow-lite-plan) | `workflow-lite-plan` | Lightweight planning |
| [workflow-lite-planex](./core-skills.md#workflow-lite-planex) | `workflow-lite-planex` | Lightweight planning |
| [workflow-multi-cli-plan](./core-skills.md#workflow-multi-cli-plan) | `workflow-multi-cli-plan`, `workflow:multi-cli-plan` | Multi-CLI collaborative planning |
| [workflow-execute](./core-skills.md#workflow-execute) | `workflow-execute` | Task execution coordination |
| [workflow-tdd-plan](./core-skills.md#workflow-tdd-plan) | `workflow-tdd-plan` | TDD with Red-Green-Refactor |
@@ -79,7 +79,7 @@ Skill(skill="review-cycle")
#### Quick Iteration
```bash
Skill(skill="workflow-lite-plan")
Skill(skill="workflow-lite-planex")
Skill(skill="workflow-execute")
```
@@ -187,7 +187,7 @@ ccw workflow-plan "Build user dashboard with configurable widgets"
# Step 3: Execute with team
ccw team lifecycle
# Or use quick iteration:
ccw workflow-lite-plan && ccw workflow-execute
ccw workflow-lite-planex && ccw workflow-execute
# Step 4: Review and refine
ccw review-code
@@ -250,7 +250,7 @@ ccw review-cycle --max-iterations 3
### Tips for Best Results
1. **Start Small**: Begin with `workflow-lite-plan` for simple tasks
1. **Start Small**: Begin with `workflow-lite-planex` for simple tasks
2. **Use Memory**: Capture insights with `memory:capture` for future reference
3. **Verify Plans**: Always review generated plans before execution
4. **Iterate**: Use `review-cycle` for continuous improvement

View File

@@ -28,7 +28,7 @@ Quick reference guide for all **33 CCW built-in skills**.
| Skill | Trigger | Purpose |
|-------|---------|---------|
| **workflow-plan** | `workflow-plan`, `workflow-plan-verify`, `workflow:replan` | 4-phase planning workflow with verification and interactive replanning |
| **workflow-lite-plan** | `workflow-lite-plan`, `workflow:lite-execute` | Lightweight planning and execution skill |
| **workflow-lite-planex** | `workflow-lite-planex` | Lightweight planning and execution skill |
| **workflow-multi-cli-plan** | `workflow-multi-cli-plan`, `workflow:multi-cli-plan` | Multi-CLI collaborative planning with ACE context engine |
| **workflow-execute** | `workflow-execute` | Coordinate agent execution for workflow tasks |
| **workflow-tdd-plan** | `workflow-tdd-plan`, `workflow-tdd-verify` | TDD workflow with Red-Green-Refactor task chain |
@@ -103,7 +103,7 @@ team lifecycle
| `review code`, `code review`, `审查代码` | review-code |
| `workflow:review-cycle` | review-cycle |
| `workflow-plan` | workflow-plan |
| `workflow-lite-plan` | workflow-lite-plan |
| `workflow-lite-planex` | workflow-lite-planex |
| `workflow-multi-cli-plan`, `workflow:multi-cli-plan` | workflow-multi-cli-plan |
| `workflow-execute` | workflow-execute |
| `workflow-tdd-plan` | workflow-tdd-plan |
@@ -163,7 +163,7 @@ The latest team-lifecycle (v5) uses the team-worker agent with dynamic role assi
| Generator-Critic Loop | team-iterdev |
| Wave Pipeline | team-planex |
| Red-Green-Refactor | workflow-tdd-plan |
| Pure Orchestrator | workflow-plan, workflow-lite-plan |
| Pure Orchestrator | workflow-plan, workflow-lite-planex |
| Progressive Phase Loading | workflow-plan, workflow-tdd-plan, team-lifecycle |
::: info See Also

View File

@@ -7,7 +7,7 @@ This page provides practical examples of CCW workflow artifacts with sensitive i
## Example 1: Lite Plan Output
### plan.json
This is an output from `workflow-lite-plan` command.
This is an output from `workflow-lite-planex` command.
```json
{

View File

@@ -31,7 +31,7 @@
- `-y, --yes` - 跳过所有确认
**映射技能**
- workflow-lite-plan, workflow-plan, workflow-execute, workflow-tdd-plan
- workflow-lite-planex, workflow-plan, workflow-execute, workflow-tdd-plan
- workflow-test-fix, workflow-multi-cli-plan, review-cycle, brainstorm
- team-planex, team-iterdev, team-lifecycle, team-issue
- team-testing, team-quality-assurance, team-brainstorm, team-uidesign

View File

@@ -23,14 +23,14 @@
| 单元类型 | Skill | 说明 |
|---------|-------|------|
| 轻量 Plan+Execute | `workflow-lite-plan` | 内部完成 plan→execute |
| 轻量 Plan+Execute | `workflow-lite-planex` | 内部完成 plan→execute |
| 标准 Planning | `workflow-plan``workflow-execute` | plan 和 execute 是独立 Skill |
| TDD Planning | `workflow-tdd-plan``workflow-execute` | tdd-plan 和 execute 是独立 Skill |
| 规格驱动 | `spec-generator``workflow-plan``workflow-execute` | 规格文档驱动完整开发 |
| 测试流水线 | `workflow-test-fix` | 内部完成 gen→cycle |
| 代码审查 | `review-cycle` | 内部完成 review→fix |
| 分析→规划 | `workflow:analyze-with-file``workflow-lite-plan` | 协作分析产物自动传递给 lite-plan |
| 头脑风暴→规划 | `workflow:brainstorm-with-file``workflow-lite-plan` | 头脑风暴产物自动传递给 lite-plan |
| 分析→规划 | `workflow:analyze-with-file``workflow-lite-planex` | 协作分析产物自动传递给 lite-plan |
| 头脑风暴→规划 | `workflow:brainstorm-with-file``workflow-lite-planex` | 头脑风暴产物自动传递给 lite-plan |
| 协作规划 | `workflow:collaborative-plan-with-file``workflow:unified-execute-with-file` | 多 agent 协作规划→通用执行 |
| 需求路线图 | `workflow:roadmap-with-file``team-planex` | 需求拆解→issue 创建→wave pipeline 执行 |
| 集成测试循环 | `workflow:integration-test-cycle` | 自迭代集成测试闭环 |
@@ -109,12 +109,12 @@ graph TD
**With-File 自动链式机制**:
`analyze-with-file``brainstorm-with-file` 完成时其产物discussion.md / brainstorm.md**自动传递**给 `workflow-lite-plan` 作为上下文输入。
`analyze-with-file``brainstorm-with-file` 完成时其产物discussion.md / brainstorm.md**自动传递**给 `workflow-lite-planex` 作为上下文输入。
| 工作流 | 自动链目标 | 产物传递 |
|--------|-----------|---------|
| analyze-with-file | → workflow-lite-plan | discussion.md |
| brainstorm-with-file | → workflow-lite-plan | brainstorm.md |
| analyze-with-file | → workflow-lite-planex | discussion.md |
| brainstorm-with-file | → workflow-lite-planex | brainstorm.md |
**Cycle 工作流自迭代模式**:
@@ -177,9 +177,9 @@ graph TD
| 单元名称 | 命令链 | 输出 |
| --- | --- | --- |
| **快速实现** | lite-plan → lite-execute | 工作代码 |
| **多 CLI 规划** | multi-cli-plan → lite-execute | 工作代码 |
| **Bug 修复** | lite-plan (--bugfix) → lite-execute | 修复的代码 |
| **快速实现** | lite-planPhase 1: 规划 → Phase 2: 执行) | 工作代码 |
| **多 CLI 规划** | multi-cli-planPhase 1: 规划 → Phase 2: 执行) | 工作代码 |
| **Bug 修复** | lite-plan --bugfixPhase 1: 规划 → Phase 2: 执行) | 修复的代码 |
| **完整规划+执行** | plan → execute | 工作代码 |
| **验证规划+执行** | plan → plan-verify → execute | 工作代码 |
| **重规划+执行** | replan → execute | 工作代码 |
@@ -235,7 +235,7 @@ graph TD
**流水线可视化示例**:
```
需求 → 【lite-plan → lite-execute】→ 代码 → 【test-fix-gen → test-cycle-execute】→ 测试通过
需求 → 【lite-planex (Phase 1→2)】→ 代码 → 【test-fix-gen → test-cycle-execute】→ 测试通过
└──── 快速实现 ────┘ └────── 测试验证 ──────┘
```
@@ -371,7 +371,7 @@ Task: <description>
| Skill | 包含操作 |
| --- | --- |
| `workflow-lite-plan` | lite-plan, lite-execute |
| `workflow-lite-planex` | lite-plan (Phase 1: 规划 → Phase 2: 执行) |
| `workflow-plan` | plan, plan-verify, replan |
| `workflow-execute` | execute |
| `workflow-tdd-plan` | tdd-plan, tdd-verify |

View File

@@ -31,8 +31,7 @@
| 命令 | 功能 | 难度 |
| --- | --- | --- |
| [`/workflow:lite-lite-lite`](./workflow.md#lite-lite-lite) | 超轻量级多工具分析和直接执行 | Intermediate |
| [`/workflow-lite-plan`](./workflow.md#lite-plan) | 轻量级交互式规划工作流 | Intermediate |
| [`/workflow:lite-execute`](./workflow.md#lite-execute) | 基于内存计划执行任务 | Intermediate |
| [`/workflow-lite-planex`](./workflow.md#lite-plan) | 轻量级交互式规划工作流 | Intermediate |
| [`/workflow:lite-fix`](./workflow.md#lite-fix) | 轻量级 Bug 诊断和修复 | Intermediate |
| [`/workflow-plan`](./workflow.md#plan) | 5 阶段规划工作流 | Intermediate |
| [`/workflow-execute`](./workflow.md#execute) | 协调代理执行工作流任务 | Intermediate |

View File

@@ -11,8 +11,7 @@
| 命令 | 功能 | 语法 |
| --- | --- | --- |
| [`lite-lite-lite`](#lite-lite-lite) | 超轻量级多工具分析和直接执行 | `/workflow:lite-lite-lite [-y] <任务>` |
| [`lite-plan`](#lite-plan) | 轻量级交互式规划工作流 | `/workflow-lite-plan [-y] [-e] "任务"` |
| [`lite-execute`](#lite-execute) | 基于内存计划执行任务 | `/workflow:lite-execute [-y] [--in-memory] [任务]` |
| [`lite-plan`](#lite-plan) | 轻量级交互式规划工作流 | `/workflow-lite-planex [-y] [-e] "任务"` |
| [`lite-fix`](#lite-fix) | 轻量级 Bug 诊断和修复 | `/workflow:lite-fix [-y] [--hotfix] "Bug 描述"` |
### 标准工作流
@@ -92,11 +91,11 @@
### lite-plan
**功能**: 轻量级交互式规划工作流,支持内存规划、代码探索和执行到 lite-execute
**功能**: 轻量级交互式规划和执行工作流Phase 1: 规划Phase 2: 执行),支持内存规划、代码探索和确认后自动执行
**语法**:
```bash
/workflow-lite-plan [-y|--yes] [-e|--explore] "任务描述" | file.md
/workflow-lite-planex [-y|--yes] [-e|--explore] "任务描述" | file.md
```
**选项**:
@@ -105,31 +104,10 @@
**示例**:
```bash
# 基础规划
/workflow-lite-plan "添加用户头像功能"
/workflow-lite-planex "添加用户头像功能"
# 带探索
/workflow-lite-plan -e "重构认证模块"
```
### lite-execute
**功能**: 基于内存计划、提示描述或文件内容执行任务。
**语法**:
```bash
/workflow:lite-execute [-y|--yes] [--in-memory] ["任务描述" | file-path]
```
**选项**:
- `--in-memory`: 使用内存计划
**示例**:
```bash
# 执行任务
/workflow:lite-execute "实现头像上传 API"
# 使用内存计划
/workflow:lite-execute --in-memory
/workflow-lite-planex -e "重构认证模块"
```
### lite-fix

View File

@@ -176,7 +176,7 @@ memory/
```bash
# 快速任务
/workflow-lite-plan "Fix login bug"
/workflow-lite-planex "Fix login bug"
# 完整开发
/workflow-plan "Add user notifications"
@@ -229,7 +229,7 @@ memory/
- 测试覆盖 → `team-testing`
2. **工作流选择**:
- 超简单 → `workflow-lite-plan`
- 超简单 → `workflow-lite-planex`
- 复杂功能 → `workflow-plan``workflow-execute`
- TDD → `workflow-tdd-plan`
- 测试修复 → `workflow-test-fix`

View File

@@ -19,7 +19,7 @@
| --- | --- | --- |
| `workflow-plan` | 统一规划技能4 阶段工作流) | `/workflow-plan` |
| `workflow-execute` | 代理协调执行 | `/workflow-execute` |
| `workflow-lite-plan` | 轻量级快速规划 | `/workflow-lite-plan` |
| `workflow-lite-planex` | 轻量级快速规划 | `/workflow-lite-planex` |
| `workflow-multi-cli-plan` | 多 CLI 协作规划 | `/workflow-multi-cli-plan` |
| `workflow-tdd-plan` | TDD 工作流 | `/workflow-tdd-plan` |
| `workflow-test-fix` | 测试修复工作流 | `/workflow-test-fix` |
@@ -182,13 +182,13 @@ Phase 5: 完成
---
### workflow-lite-plan
### workflow-lite-planex
**一句话定位**: 轻量级快速规划 — 超简单任务的快速规划和执行
**触发**:
```shell
/workflow-lite-plan <simple-task>
/workflow-lite-planex <simple-task>
```
**功能**:
@@ -331,7 +331,7 @@ Wave 2: Issue 6-10 → 并行规划 → 并行执行
## 最佳实践
1. **选择合适的工作流**:
- 超简单任务 → `workflow-lite-plan`
- 超简单任务 → `workflow-lite-planex`
- 复杂功能 → `workflow-plan``workflow-execute`
- TDD 开发 → `workflow-tdd-plan`
- 测试修复 → `workflow-test-fix`

View File

@@ -679,24 +679,24 @@ Skill(skill="workflow-plan")
---
### workflow-lite-plan
### workflow-lite-planex
**用途**:轻量级规划和执行技能
**触发器**`workflow-lite-plan``workflow:lite-execute`
**触发器**`workflow-lite-planex`
**说明**路由到 lite-plan 或 lite-execute,带提示增强。
**说明**统一的规划和执行技能Phase 1: 规划Phase 2: 执行),带提示增强。
**阶段**
1. 阶段 1轻量级计划
2. 阶段 2轻量级执行
1. 阶段 1轻量级计划(规划管道)
2. 阶段 2轻量级执行(执行引擎,内部)
**模式**`lite-plan``lite-execute`
**模式**`plan`Phase 1 → Phase 2 自动衔接)
**产物**LITE_PLAN.md、执行结果
```bash
Skill(skill="workflow-lite-plan")
Skill(skill="workflow-lite-planex")
```
---
@@ -707,7 +707,7 @@ Skill(skill="workflow-lite-plan")
**触发器**`workflow-multi-cli-plan``workflow:multi-cli-plan`
**说明**路由到 multi-cli-plan 或 lite-execute,带提示增强。
**说明**多 CLI 协作规划和执行技能Phase 1: 规划Phase 2: 执行),带提示增强。
**阶段**
1. 阶段 1多 CLI 计划ACE 上下文 → 讨论 → 计划 → 执行)
@@ -851,7 +851,7 @@ Skill(skill="review-cycle")
**使用场景**:快速迭代和快速原型
```bash
Skill(skill="workflow-lite-plan")
Skill(skill="workflow-lite-planex")
Skill(skill="workflow-execute")
```
@@ -1039,7 +1039,7 @@ Skill(skill="skill-tuning")
| 层级 | 技能 |
|------|------|
| 元技能 | skill-generator、skill-tuning、workflow-skill-designer |
| 编排器 | workflow-plan、workflow-lite-plan、workflow-multi-cli-plan |
| 编排器 | workflow-plan、workflow-lite-planex、workflow-multi-cli-plan |
| 执行器 | workflow-execute |
| 团队负责人 | team-lifecycle (v5) |
@@ -1085,7 +1085,7 @@ Skill(skill="skill-tuning")
| `manage issue` | issue-manage |
| `workflow-plan``workflow-plan-verify``workflow:replan` | workflow-plan |
| `workflow-execute` | workflow-execute |
| `workflow-lite-plan` | workflow-lite-plan |
| `workflow-lite-planex` | workflow-lite-planex |
| `workflow-multi-cli-plan``workflow:multi-cli-plan` | workflow-multi-cli-plan |
| `workflow-tdd-plan` | workflow-tdd-plan |
| `workflow-test-fix``test fix workflow` | workflow-test-fix |

View File

@@ -56,7 +56,7 @@ Skills 是 CCW 可执行的、可复用的、领域特定的能力。每个技
| 技能 | 触发器 | 说明 |
|------|--------|------|
| [workflow-plan](./core-skills.md#workflow-plan) | `workflow-plan`, `workflow-plan-verify`, `workflow:replan` | 4 阶段规划带验证 |
| [workflow-lite-plan](./core-skills.md#workflow-lite-plan) | `workflow-lite-plan` | 轻量级规划 |
| [workflow-lite-planex](./core-skills.md#workflow-lite-planex) | `workflow-lite-planex` | 轻量级规划 |
| [workflow-multi-cli-plan](./core-skills.md#workflow-multi-cli-plan) | `workflow-multi-cli-plan`, `workflow:multi-cli-plan` | 多 CLI 协作规划 |
| [workflow-execute](./core-skills.md#workflow-execute) | `workflow-execute` | 任务执行协调 |
| [workflow-tdd-plan](./core-skills.md#workflow-tdd-plan) | `workflow-tdd-plan` | TDD 红-绿-重构 |
@@ -79,7 +79,7 @@ Skill(skill="review-cycle")
#### 快速迭代
```bash
Skill(skill="workflow-lite-plan")
Skill(skill="workflow-lite-planex")
Skill(skill="workflow-execute")
```
@@ -187,7 +187,7 @@ ccw workflow-plan "Build user dashboard with configurable widgets"
# 步骤 3团队执行
ccw team lifecycle
# 或使用快速迭代:
ccw workflow-lite-plan && ccw workflow-execute
ccw workflow-lite-planex && ccw workflow-execute
# 步骤 4审查和优化
ccw review-code
@@ -250,7 +250,7 @@ ccw review-cycle --max-iterations 3
### 最佳效果提示
1. **从小开始**:简单任务使用 `workflow-lite-plan`
1. **从小开始**:简单任务使用 `workflow-lite-planex`
2. **使用记忆**:用 `memory:capture` 捕获见解供将来参考
3. **验证计划**:执行前始终审查生成的计划
4. **迭代**:使用 `review-cycle` 持续改进

View File

@@ -28,7 +28,7 @@
| 技能 | 触发器 | 用途 |
|------|--------|------|
| **workflow-plan** | `workflow-plan``workflow-plan-verify``workflow:replan` | 4 阶段规划工作流,带验证和交互式重新规划 |
| **workflow-lite-plan** | `workflow-lite-plan``workflow:lite-execute` | 轻量级规划和执行技能 |
| **workflow-lite-planex** | `workflow-lite-planex` | 轻量级规划和执行技能 |
| **workflow-multi-cli-plan** | `workflow-multi-cli-plan``workflow:multi-cli-plan` | 多 CLI 协作规划,带 ACE 上下文引擎 |
| **workflow-execute** | `workflow-execute` | 协调工作流任务的代理执行 |
| **workflow-tdd-plan** | `workflow-tdd-plan``workflow-tdd-verify` | TDD 工作流,带红-绿-重构任务链 |
@@ -103,7 +103,7 @@ team lifecycle
| `review code``code review``审查代码` | review-code |
| `workflow:review-cycle` | review-cycle |
| `workflow-plan` | workflow-plan |
| `workflow-lite-plan` | workflow-lite-plan |
| `workflow-lite-planex` | workflow-lite-planex |
| `workflow-multi-cli-plan``workflow:multi-cli-plan` | workflow-multi-cli-plan |
| `workflow-execute` | workflow-execute |
| `workflow-tdd-plan` | workflow-tdd-plan |
@@ -163,7 +163,7 @@ team lifecycle
| Generator-Critic Loop | team-iterdev |
| Wave Pipeline | team-planex |
| Red-Green-Refactor | workflow-tdd-plan |
| Pure Orchestrator | workflow-plan、workflow-lite-plan |
| Pure Orchestrator | workflow-plan、workflow-lite-planex |
| Progressive Phase Loading | workflow-plan、workflow-tdd-plan、team-lifecycle |
::: info 参见