Compare commits

...

6 Commits

Author SHA1 Message Date
catlog22
958567e35a docs: 发布 v5.5.0 - 交互式命令指南与增强文档
版本更新: v5.4.0 → v5.5.0

核心改进:
-  命令指南技能 - 支持 CCW-help 和 CCW-issue 关键词触发
-  增强命令描述 - 所有 69 个命令更新了详细功能说明
-  5 索引命令系统 - 按分类、使用场景、关系和核心命令组织
-  智能推荐 - 基于上下文的下一步操作建议

文档更新:
- README.md / README_CN.md: 新增"需要帮助?"章节,介绍 CCW-help/CCW-issue 用法
- CHANGELOG.md: 添加完整的 v5.5.0 版本说明(109行详细内容)
- SKILL.md: 更新版本至 v1.1.0

命令指南功能:
- 🔍 智能命令搜索 - 按关键词、分类或场景查找
- 🤖 下一步推荐 - 工作流引导和上下文建议
- 📖 详细文档 - 参数、示例和最佳实践
- 🎓 新手入门 - 14 个核心命令学习路径
- 📝 问题报告 - 标准化 bug 报告和功能请求模板

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 15:25:11 +08:00
catlog22
920b179440 docs: 更新所有命令描述并重新生成索引文件
- 更新所有69个命令文件的description字段,基于实际功能重新生成详细描述
- 重新生成5个索引文件(all-commands, by-category, by-use-case, essential-commands, command-relationships)
- 移动analyze_commands.py到scripts/目录并完善功能
- 移除临时备份文件

命令描述改进示例:
- workflow:plan: 增加了工具和代理的详细说明(Gemini, action-planning-agent)
- cli:execute: 说明了YOLO权限和多种执行模式
- memory:update-related: 详细说明了批处理策略和工具回退链

索引文件改进:
- usage_scenario从2种扩展到10种(更精细分类)
- command-relationships覆盖所有69个命令
- 区分built-in(内置调用)和sequential(用户顺序执行)关系

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 15:11:31 +08:00
catlog22
6993677ed9 feat: Add command relationships and essential commands JSON files
- Introduced command-relationships.json to define relationships between various commands.
- Created essential-commands.json to provide detailed descriptions and usage scenarios for key commands.
- Implemented update-index.sh script for maintaining command index files, including backup and validation processes.
- Added templates for bug reports, feature requests, and questions to streamline issue reporting and feature suggestions.
2025-11-06 12:59:14 +08:00
catlog22
8e3dff3d0f refactor: optimize universal templates - reduce to <120 lines
- Streamline 00-universal-rigorous-style.txt: 148→92 lines (-38%)
  - Merge capabilities and thinking mode sections
  - Consolidate execution checklist
  - Simplify quality standards
  - Preserve complete response structure (8 sections)
  - Combine style and constraints sections

- Streamline 00-universal-creative-style.txt: 205→95 lines (-54%)
  - Merge capabilities and thinking mode sections
  - Consolidate exploration phases
  - Simplify quality standards
  - Condense multi-perspective sections
  - Preserve complete response structure (10 sections)
  - Condense creative techniques to optional toolkit

Benefits:
 Both templates under 120 lines (92 and 95)
 Reduced verbosity by 53% (310→187 lines)
 Maintained all core functionality
 Clearer, more scannable structure
 Faster to load and parse

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 12:42:23 +08:00
catlog22
775c982218 feat: add universal fallback templates and fix template reference
- Add universal templates for flexible task execution:
  - 00-universal-rigorous-style.txt: Precision-driven execution
  - 00-universal-creative-style.txt: Innovation-focused exploration
- Update intelligent-tools-strategy.md:
  - Document universal templates as fallback option
  - Add usage guide and selection criteria
  - Update task-template matrix with universal fallbacks
  - Add RULES field examples for universal templates
- Fix update_module_claude.sh template path:
  - Update reference from claude-module-unified.txt to 02-document-module-structure.txt
  - Align with priority prefix naming convention (854464b)

Benefits:
 Fallback templates available when no specific template matches
 Support both rigorous and creative execution styles
 Script correctly references renamed template file
 Comprehensive documentation for template selection

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 12:39:00 +08:00
catlog22
164d1df341 docs: 更新文档以反映v5.4.0版本更新
更新内容:
- CHANGELOG.md:添加v5.4.0完整更新日志
  - CLI模板系统重组(19个模板,优先级前缀)
  - Gemini 404错误回退策略
  - 21处模板引用更新
  - 目录结构优化

- README.md & README_CN.md:更新版本号和核心亮点
  - 版本徽章:v5.2.0 → v5.4.0
  - 版本说明:更新为v5.4核心改进
  - 突出优先级模板、错误处理、统一引用、组织优化

文档变更详情:
- 完整的v5.4.0变更日志(141行)
- 双语README版本信息同步更新
- 清晰的升级说明和使用指南

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 11:07:43 +08:00
94 changed files with 6156 additions and 87 deletions

View File

@@ -1,6 +1,6 @@
---
name: analyze
description: Quick codebase analysis using CLI tools (codex/gemini/qwen)
description: Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection
argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target"
allowed-tools: SlashCommand(*), Bash(*), TodoWrite(*), Read(*), Glob(*), Task(*)
---

View File

@@ -1,6 +1,6 @@
---
name: chat
description: Simple CLI interaction command for direct codebase analysis
description: Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference
argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry"
allowed-tools: SlashCommand(*), Bash(*), Task(*)
---

View File

@@ -1,6 +1,6 @@
---
name: cli-init
description: Initialize CLI tool configurations (Gemini and Qwen) based on workspace analysis
description: Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection
argument-hint: "[--tool gemini|qwen|all] [--output path] [--preview]"
allowed-tools: Bash(*), Read(*), Write(*), Glob(*)
---

View File

@@ -1,6 +1,6 @@
---
name: codex-execute
description: Automated task decomposition and execution with Codex using resume mechanism
description: Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity
argument-hint: "[--verify-git] task description or task-id"
allowed-tools: SlashCommand(*), Bash(*), TodoWrite(*), Read(*), Glob(*)
---

View File

@@ -1,6 +1,6 @@
---
name: discuss-plan
description: Orchestrates an iterative, multi-model discussion for planning and analysis without implementation.
description: Multi-round collaborative planning using Gemini, Codex, and Claude synthesis with iterative discussion cycles (read-only, no code changes)
argument-hint: "[--topic '...'] [--task-id '...'] [--rounds N]"
allowed-tools: SlashCommand(*), Bash(*), TodoWrite(*), Read(*), Glob(*)
---

View File

@@ -1,6 +1,6 @@
---
name: execute
description: Auto-execution of implementation tasks with YOLO permissions and intelligent context inference
description: Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection
argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id"
allowed-tools: SlashCommand(*), Bash(*), Task(*)
---

View File

@@ -1,6 +1,6 @@
---
name: bug-diagnosis
description: Bug diagnosis and fix suggestions using CLI tools with specialized template
description: Read-only bug root cause analysis using Gemini/Qwen/Codex with systematic diagnosis template for fix suggestions
argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] bug description"
allowed-tools: SlashCommand(*), Bash(*), Task(*)
---

View File

@@ -1,6 +1,6 @@
---
name: code-analysis
description: Deep code analysis and debugging using CLI tools with specialized template
description: Read-only execution path tracing using Gemini/Qwen/Codex with specialized analysis template for call flow and optimization
argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] analysis target"
allowed-tools: SlashCommand(*), Bash(*), Task(*)
---

View File

@@ -1,6 +1,6 @@
---
name: plan
description: Project planning and architecture analysis using CLI tools
description: Read-only architecture planning using Gemini/Qwen/Codex with strategic planning template for modification plans and impact analysis
argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] topic"
allowed-tools: SlashCommand(*), Bash(*), Task(*)
---

View File

@@ -1,6 +1,6 @@
---
name: enhance-prompt
description: Context-aware prompt enhancement using session memory and codebase analysis
description: Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection
argument-hint: "user input to enhance"
---

View File

@@ -1,6 +1,6 @@
---
name: docs
description: Documentation planning and orchestration - creates structured documentation tasks for execution
description: Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs
argument-hint: "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]"
---

View File

@@ -1,6 +1,6 @@
---
name: load-skill-memory
description: Activate SKILL package (auto-detect or manual) and load documentation based on task intent
description: Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords
argument-hint: "[skill_name] \"task intent description\""
allowed-tools: Bash(*), Read(*), Skill(*)
---

View File

@@ -1,6 +1,6 @@
---
name: load
description: Load project memory by delegating to agent, returns structured core content package for subsequent operations
description: Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context
argument-hint: "[--tool gemini|qwen] \"task context description\""
allowed-tools: Task(*), Bash(*)
examples:

View File

@@ -1,6 +1,6 @@
---
name: skill-memory
description: Generate SKILL package index from project documentation
description: 4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)
argument-hint: "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]"
allowed-tools: SlashCommand(*), TodoWrite(*), Bash(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: tech-research
description: Generate tech stack SKILL packages using Exa research via agent delegation
description: 3-phase orchestrator: extract tech stack from session/name → delegate to agent for Exa research and module generation → generate SKILL.md index (skips phase 2 if exists)
argument-hint: "[session-id | tech-stack-name] [--regenerate] [--tool <gemini|qwen>]"
allowed-tools: SlashCommand(*), TodoWrite(*), Bash(*), Read(*), Write(*), Task(*)
---

View File

@@ -1,6 +1,6 @@
---
name: update-full
description: Complete project-wide CLAUDE.md documentation update with agent-based parallel execution and tool fallback
description: Update all CLAUDE.md files using layer-based execution (Layer 3→1) with batched agents (4 modules/agent) and gemini→qwen→codex fallback, <20 modules uses direct parallel
argument-hint: "[--tool gemini|qwen|codex] [--path <directory>]"
---

View File

@@ -1,6 +1,6 @@
---
name: update-related
description: Context-aware CLAUDE.md documentation updates based on recent changes with agent-based execution and tool fallback
description: Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution
argument-hint: "[--tool gemini|qwen|codex]"
---

View File

@@ -1,6 +1,6 @@
---
name: workflow-skill-memory
description: Generate SKILL package from archived workflow sessions for progressive context loading
description: Process WFS-* archived sessions using universal-executor agents with Gemini analysis to generate workflow-progress SKILL package (sessions-timeline, lessons, conflicts)
argument-hint: "session <session-id> | all"
allowed-tools: Task(*), TodoWrite(*), Bash(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: breakdown
description: Intelligent task decomposition with context-aware subtask generation
description: Decompose complex task into subtasks with dependency mapping, creates child task JSONs with parent references and execution order
argument-hint: "task-id"
---

View File

@@ -1,6 +1,6 @@
---
name: create
description: Create implementation tasks with automatic context awareness
description: Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis
argument-hint: "\"task title\""
---

View File

@@ -1,6 +1,6 @@
---
name: execute
description: Execute tasks with appropriate agents and context-aware orchestration
description: Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking
argument-hint: "task-id"
---

View File

@@ -1,6 +1,6 @@
---
name: replan
description: Replan individual tasks with detailed user input and change tracking
description: Update task JSON with new requirements or batch-update multiple tasks from verification report, tracks changes in task-changes.json
argument-hint: "task-id [\"text\"|file.md] | --batch [verification-report.md]"
allowed-tools: Read(*), Write(*), Edit(*), TodoWrite(*), Glob(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: version
description: Display version information and check for updates
description: Display Claude Code version information and check for updates
allowed-tools: Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: action-plan-verify
description: Perform non-destructive cross-artifact consistency and quality analysis of IMPL_PLAN.md and task.json before execution
description: Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation
argument-hint: "[optional: --session session-id]"
allowed-tools: Read(*), TodoWrite(*), Glob(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: api-designer
description: Generate or update api-designer/analysis.md addressing guidance-specification discussion points
description: Generate or update api-designer/analysis.md addressing guidance-specification discussion points for API design perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: artifacts
description: Interactive clarification generating confirmed guidance specification
description: Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis
argument-hint: "topic or challenge description [--count N]"
allowed-tools: TodoWrite(*), Read(*), Write(*), Glob(*)
---

View File

@@ -1,6 +1,6 @@
---
name: auto-parallel
description: Parallel brainstorming automation with dynamic role selection and concurrent execution
description: Parallel brainstorming automation with dynamic role selection and concurrent execution across multiple perspectives
argument-hint: "topic or challenge description" [--count N]
allowed-tools: SlashCommand(*), Task(*), TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*)
---

View File

@@ -1,6 +1,6 @@
---
name: data-architect
description: Generate or update data-architect/analysis.md addressing guidance-specification discussion points
description: Generate or update data-architect/analysis.md addressing guidance-specification discussion points for data architecture perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: product-manager
description: Generate or update product-manager/analysis.md addressing guidance-specification discussion points
description: Generate or update product-manager/analysis.md addressing guidance-specification discussion points for product management perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: product-owner
description: Generate or update product-owner/analysis.md addressing guidance-specification discussion points
description: Generate or update product-owner/analysis.md addressing guidance-specification discussion points for product ownership perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: scrum-master
description: Generate or update scrum-master/analysis.md addressing guidance-specification discussion points
description: Generate or update scrum-master/analysis.md addressing guidance-specification discussion points for Agile process perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: subject-matter-expert
description: Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points
description: Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points for domain expertise perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: synthesis
description: Clarify and refine role analyses through intelligent Q&A and targeted updates
description: Clarify and refine role analyses through intelligent Q&A and targeted updates with synthesis agent
argument-hint: "[optional: --session session-id]"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*), Edit(*), Glob(*)
---

View File

@@ -1,6 +1,6 @@
---
name: system-architect
description: Generate or update system-architect/analysis.md addressing guidance-specification discussion points
description: Generate or update system-architect/analysis.md addressing guidance-specification discussion points for system architecture perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: ui-designer
description: Generate or update ui-designer/analysis.md addressing guidance-specification discussion points
description: Generate or update ui-designer/analysis.md addressing guidance-specification discussion points for UI design perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: ux-expert
description: Generate or update ux-expert/analysis.md addressing guidance-specification discussion points
description: Generate or update ux-expert/analysis.md addressing guidance-specification discussion points for UX perspective
argument-hint: "optional topic - uses existing framework if available"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
---

View File

@@ -1,6 +1,6 @@
---
name: execute
description: Coordinate agents for existing workflow tasks with automatic discovery
description: Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking
argument-hint: "[--resume-session=\"session-id\"]"
---

View File

@@ -1,6 +1,6 @@
---
name: plan
description: Orchestrate 5-phase planning workflow with quality gate, executing commands and passing context between phases
description: 5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution
argument-hint: "[--agent] [--cli-execute] \"text description\"|file.md"
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: resume
description: Intelligent workflow session resumption with automatic progress analysis
description: Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection
argument-hint: "session-id for workflow session to resume"
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: review
description: Optional specialized review (security, architecture, docs) for completed implementation
description: Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini
argument-hint: "[--type=security|architecture|action-items|quality] [optional: session-id]"
---

View File

@@ -1,6 +1,6 @@
---
name: complete
description: Mark the active workflow session as complete, archive it with lessons learned, and remove active flag
description: Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag
examples:
- /workflow:session:complete
- /workflow:session:complete --detailed

View File

@@ -1,6 +1,6 @@
---
name: list
description: List all workflow sessions with status
description: List all workflow sessions with status filtering, shows session metadata and progress information
examples:
- /workflow:session:list
---

View File

@@ -1,6 +1,6 @@
---
name: resume
description: Resume the most recently paused workflow session
description: Resume the most recently paused workflow session with automatic session discovery and status update
---
# Resume Workflow Session (/workflow:session:resume)

View File

@@ -1,6 +1,6 @@
---
name: start
description: Discover existing sessions or start a new workflow session with intelligent session management
description: Discover existing sessions or start new workflow session with intelligent session management and conflict detection
argument-hint: [--auto|--new] [optional: task description for new session]
examples:
- /workflow:session:start

View File

@@ -1,6 +1,6 @@
---
name: workflow:status
description: Generate on-demand views from JSON task data
description: Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view
argument-hint: "[optional: task-id]"
---

View File

@@ -1,6 +1,6 @@
---
name: tdd-plan
description: Orchestrate TDD workflow planning with Red-Green-Refactor task chains
description: TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, and cycle tracking
argument-hint: "[--agent] \"feature description\"|file.md"
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: tdd-verify
description: Verify TDD workflow compliance and generate quality report
description: Verify TDD workflow compliance against Red-Green-Refactor cycles, generate quality report with coverage analysis
argument-hint: "[optional: WFS-session-id]"
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(gemini:*)

View File

@@ -1,6 +1,6 @@
---
name: test-cycle-execute
description: Execute test-fix workflow with dynamic task generation and iterative fix cycles
description: Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached
argument-hint: "[--resume-session=\"session-id\"] [--max-iterations=N]"
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*), Task(*)
---

View File

@@ -1,6 +1,6 @@
---
name: test-fix-gen
description: Create independent test-fix workflow session from existing implementation (session or prompt-based)
description: Create test-fix workflow session from session ID, description, or file path with test strategy generation and task planning
argument-hint: "[--use-codex] [--cli-execute] (source-session-id | \"feature description\" | /path/to/file.md)"
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: test-gen
description: Create independent test-fix workflow session by analyzing completed implementation
description: Create independent test-fix workflow session from completed implementation session, analyzes code to generate test tasks
argument-hint: "[--use-codex] [--cli-execute] source-session-id"
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: conflict-resolution
description: Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis
description: Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis with Gemini/Qwen
argument-hint: "--session WFS-session-id --context path/to/context-package.json"
examples:
- /workflow:tools:conflict-resolution --session WFS-auth --context .workflow/WFS-auth/.process/context-package.json

View File

@@ -1,6 +1,6 @@
---
name: gather
description: Intelligently collect project context using context-search-agent based on task description and package into standardized JSON
description: Intelligently collect project context using context-search-agent based on task description, packages into standardized JSON
argument-hint: "--session WFS-session-id \"task description\""
examples:
- /workflow:tools:context-gather --session WFS-user-auth "Implement user authentication system"

View File

@@ -1,6 +1,6 @@
---
name: task-generate-agent
description: Autonomous task generation using action-planning-agent with discovery and output phases
description: Autonomous task generation using action-planning-agent with discovery and output phases for workflow planning
argument-hint: "--session WFS-session-id [--cli-execute]"
examples:
- /workflow:tools:task-generate-agent --session WFS-auth

View File

@@ -1,6 +1,6 @@
---
name: task-generate-tdd
description: Generate TDD task chains with Red-Green-Refactor dependencies
description: Generate TDD task chains with Red-Green-Refactor dependencies, test-first structure, and cycle validation
argument-hint: "--session WFS-session-id [--agent]"
allowed-tools: Read(*), Write(*), Bash(gemini:*), TodoWrite(*)
---

View File

@@ -1,6 +1,6 @@
---
name: task-generate
description: Generate task JSON files and IMPL_PLAN.md from analysis results with artifacts integration
description: Generate task JSON files and IMPL_PLAN.md from analysis results using action-planning-agent with artifact integration
argument-hint: "--session WFS-session-id [--cli-execute]"
examples:
- /workflow:tools:task-generate --session WFS-auth

View File

@@ -1,6 +1,6 @@
---
name: tdd-coverage-analysis
description: Analyze test coverage and TDD cycle execution
description: Analyze test coverage and TDD cycle execution with Red-Green-Refactor compliance verification
argument-hint: "--session WFS-session-id"
allowed-tools: Read(*), Write(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: test-concept-enhanced
description: Analyze test requirements and generate test generation strategy using Gemini
description: Analyze test requirements and generate test generation strategy using Gemini with test-context package
argument-hint: "--session WFS-test-session-id --context path/to/test-context-package.json"
examples:
- /workflow:tools:test-concept-enhanced --session WFS-test-auth --context .workflow/WFS-test-auth/.process/test-context-package.json

View File

@@ -1,6 +1,6 @@
---
name: test-context-gather
description: Intelligently collect test coverage context using test-context-search-agent and package into standardized test-context JSON
description: Collect test coverage context using test-context-search-agent and package into standardized test-context JSON
argument-hint: "--session WFS-test-session-id"
examples:
- /workflow:tools:test-context-gather --session WFS-test-auth

View File

@@ -1,6 +1,6 @@
---
name: test-task-generate
description: Generate test-fix task JSON with iterative test-fix-retest cycle specification
description: Generate test-fix task JSON with iterative test-fix-retest cycle specification using Gemini/Qwen/Codex
argument-hint: "[--use-codex] [--cli-execute] --session WFS-test-session-id"
examples:
- /workflow:tools:test-task-generate --session WFS-test-auth

View File

@@ -1,6 +1,6 @@
---
name: animation-extract
description: Extract animation and transition patterns from URLs, CSS, or interactive questioning
description: Extract animation and transition patterns from URLs, CSS, or interactive questioning for design system documentation
argument-hint: "[--base-path <path>] [--session <id>] [--urls "<list>"] [--mode <auto|interactive>] [--focus "<types>"]"
allowed-tools: TodoWrite(*), Read(*), Write(*), Glob(*), Bash(*), Task(ui-design-agent), mcp__chrome-devtools__navigate_page(*), mcp__chrome-devtools__evaluate_script(*)
---

View File

@@ -1,6 +1,6 @@
---
name: batch-generate
description: Prompt-driven batch UI generation using target-style-centric parallel execution
description: Prompt-driven batch UI generation using target-style-centric parallel execution with design token application
argument-hint: [--targets "<list>"] [--target-type "page|component"] [--device-type "desktop|mobile|tablet|responsive"] [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]
allowed-tools: TodoWrite(*), Read(*), Write(*), Task(ui-design-agent), Bash(*), mcp__exa__web_search_exa(*)
---

View File

@@ -1,6 +1,6 @@
---
name: capture
description: Batch screenshot capture for UI design workflows using MCP or local fallback
description: Batch screenshot capture for UI design workflows using MCP puppeteer or local fallback with URL mapping
argument-hint: --url-map "target:url,..." [--base-path path] [--session id]
allowed-tools: TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*), ListMcpResourcesTool(*), mcp__chrome-devtools__*, mcp__playwright__*
---

View File

@@ -1,6 +1,6 @@
---
name: explore-auto
description: Exploratory UI design workflow with style-centric batch generation
description: Exploratory UI design workflow with style-centric batch generation, creates design variants from prompts/images with parallel execution
argument-hint: "[--prompt "<desc>"] [--images "<glob>"] [--targets "<list>"] [--target-type "page|component"] [--session <id>] [--style-variants <count>] [--layout-variants <count>] [--batch-plan]""
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*), Glob(*), Write(*), Task(conceptual-planning-agent)
---

View File

@@ -1,6 +1,6 @@
---
name: explore-layers
description: Interactive deep UI capture with depth-controlled layer exploration
description: Interactive deep UI capture with depth-controlled layer exploration using MCP puppeteer
argument-hint: --url <url> --depth <1-5> [--session id] [--base-path path]
allowed-tools: TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*), mcp__chrome-devtools__*
---

View File

@@ -1,6 +1,6 @@
---
name: generate
description: Assemble UI prototypes by combining layout templates with design tokens (pure assembler)
description: Assemble UI prototypes by combining layout templates with design tokens, pure assembler without new content generation
argument-hint: [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]
allowed-tools: TodoWrite(*), Read(*), Write(*), Task(ui-design-agent), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: imitate-auto
description: High-speed multi-page UI replication with batch screenshot capture
description: High-speed multi-page UI replication with batch screenshot capture and design token extraction
argument-hint: --url-map "<map>" [--capture-mode <batch|deep>] [--depth <1-5>] [--session <id>] [--prompt "<desc>"]
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Write(*), Bash(*)
---

View File

@@ -1,6 +1,6 @@
---
name: layout-extract
description: Extract structural layout information from reference images, URLs, or text prompts
description: Extract structural layout information from reference images, URLs, or text prompts using Claude analysis
argument-hint: [--base-path <path>] [--session <id>] [--images "<glob>"] [--urls "<list>"] [--prompt "<desc>"] [--targets "<list>"] [--mode <imitate|explore>] [--variants <count>] [--device-type <desktop|mobile|tablet|responsive>]
allowed-tools: TodoWrite(*), Read(*), Write(*), Glob(*), Bash(*), Task(ui-design-agent), mcp__exa__web_search_exa(*)
---

View File

@@ -1,6 +1,6 @@
---
name: style-extract
description: Extract design style from reference images or text prompts using Claude's analysis
description: Extract design style from reference images or text prompts using Claude analysis with variant generation
argument-hint: "[--base-path <path>] [--session <id>] [--images "<glob>"] [--urls "<list>"] [--prompt "<desc>"] [--mode <imitate|explore>] [--variants <count>]"
allowed-tools: TodoWrite(*), Read(*), Write(*), Glob(*), mcp__chrome-devtools__navigate_page(*), mcp__chrome-devtools__evaluate_script(*)
---

View File

@@ -1,6 +1,6 @@
---
name: update
description: Update brainstorming artifacts with finalized design system references
description: Update brainstorming artifacts with finalized design system references from selected prototypes
argument-hint: --session <session_id> [--selected-prototypes "<list>"]
allowed-tools: Read(*), Write(*), Edit(*), TodoWrite(*), Glob(*), Bash(*)
---

View File

@@ -192,7 +192,7 @@ update_module_claude() {
fi
# Use unified template for all modules
local template_path="$HOME/.claude/workflows/cli-templates/prompts/memory/claude-module-unified.txt"
local template_path="$HOME/.claude/workflows/cli-templates/prompts/memory/02-document-module-structure.txt"
# Read template content directly
local template_content=""

View File

@@ -0,0 +1,179 @@
---
name: command-guide
description: Workflow command guide for Claude DMS3 (69 commands). Search/browse commands, get next-step recommendations, view documentation, report issues. Triggers "CCW-help", "CCW-issue", "how to use", "search commands", "what's next", beginner onboarding questions
allowed-tools: Read, Grep, Glob, AskUserQuestion
---
# Command Guide Skill
Comprehensive command guide for Claude DMS3 workflow system covering 69 commands across 4 categories (workflow, cli, memory, task).
## 🎯 Operation Modes
### Mode 1: Command Search 🔍
**When**: User searches by keyword, category, or use-case
**Triggers**: "搜索命令", "find command", "planning 相关", "search"
**Process**:
1. Identify search type (keyword/category/use-case)
2. Query appropriate index (all-commands/by-category/by-use-case)
3. Return matching commands with metadata
4. Suggest related commands
**Example**: "搜索 planning 命令" → Lists planning commands from `index/by-use-case.json`
---
### Mode 2: Smart Recommendations 🤖
**When**: User asks for next steps after a command
**Triggers**: "下一步", "what's next", "after /workflow:plan", "推荐"
**Process**:
1. Parse current context (last command/workflow state)
2. Query `index/command-relationships.json`
3. Return recommended next commands with rationale
4. Show common workflow patterns
**Example**: "执行完 /workflow:plan 后做什么?" → Recommends /workflow:execute or /workflow:action-plan-verify
---
### Mode 3: Full Documentation 📖
**When**: User requests command details
**Triggers**: "参数说明", "怎么用", "how to use", "详情"
**Process**:
1. Locate command in `index/all-commands.json`
2. Read original command file for full details
3. Present parameters, arguments, examples
4. Link to related commands
**Example**: "/workflow:plan 的参数是什么?" → Shows full parameter list and usage examples
---
### Mode 4: Beginner Onboarding 🎓
**When**: New user needs guidance
**Triggers**: "新手", "getting started", "如何开始", "常用命令"
**Process**:
1. Present progressive learning path
2. Show `index/essential-commands.json` (Top 14 commands)
3. Link to getting-started guide
4. Provide first workflow example
**Example**: "我是新手,如何开始?" → Learning path + Top 14 commands + quick start guide
---
### Mode 5: Issue Reporting 📝
**When**: User wants to report issue or request feature
**Triggers**: **"CCW-issue"**, **"CCW-help"**, "报告 bug", "功能建议", "问题咨询"
**Process**:
1. Use AskUserQuestion to confirm type (bug/feature/question)
2. Collect required information interactively
3. Select appropriate template (`templates/issue-{type}.md`)
4. Generate filled template and save/display
**Example**: "CCW-issue" → Interactive Q&A → Generates GitHub issue template
---
## 📚 Index Files
All command metadata is stored in JSON indexes for fast querying:
- **all-commands.json** - Complete catalog (69 commands) with full metadata
- **by-category.json** - Hierarchical organization (workflow/cli/memory/task)
- **by-use-case.json** - Grouped by scenario (planning/implementation/testing/docs/session)
- **essential-commands.json** - Top 14 most-used commands
- **command-relationships.json** - Next-step recommendations and dependencies
📖 Detailed structure: [Index Structure Reference](guides/index-structure.md)
---
## 🗂️ Supporting Guides
- **[Getting Started](guides/getting-started.md)** - 5-minute quickstart for beginners
- **[Workflow Patterns](guides/workflow-patterns.md)** - Common workflow examples (Plan→Execute, TDD, UI design)
- **[CLI Tools Guide](guides/cli-tools-guide.md)** - Gemini/Qwen/Codex usage
- **[Troubleshooting](guides/troubleshooting.md)** - Common issues and solutions
- **[Implementation Details](guides/implementation-details.md)** - Detailed logic for each mode
- **[Usage Examples](guides/examples.md)** - Example dialogues and edge cases
---
## 🛠️ Issue Templates
Generate standardized GitHub issue templates:
- **[Bug Report](templates/issue-bug.md)** - Report command errors or system bugs
- **[Feature Request](templates/issue-feature.md)** - Suggest new features or improvements
- **[Question](templates/issue-question.md)** - Ask usage questions or request help
Templates are auto-populated during Mode 5 (Issue Reporting) interaction.
---
## 📊 System Statistics
- **Total Commands**: 69
- **Categories**: 4 (workflow: 46, cli: 9, memory: 8, task: 4, general: 2)
- **Use Cases**: 5 (planning, implementation, testing, documentation, session-management)
- **Difficulty Levels**: 3 (Beginner, Intermediate, Advanced)
- **Essential Commands**: 14
---
## 🔧 Maintenance
### Updating Indexes
When commands are added/modified/removed:
```bash
bash scripts/update-index.sh
```
This script:
1. Scans all command files in `../../commands/`
2. Extracts metadata from YAML frontmatter
3. Analyzes command relationships
4. Regenerates all 5 index files
### Committing Updates
```bash
git add .claude/skills/command-guide/index/
git commit -m "docs: update command indexes"
git push
```
Team members get latest indexes via `git pull`.
---
## 📖 Related Documentation
- [Workflow Architecture](../../workflows/workflow-architecture.md) - System design overview
- [Intelligent Tools Strategy](../../workflows/intelligent-tools-strategy.md) - CLI tool selection
- [Context Search Strategy](../../workflows/context-search-strategy.md) - Search patterns
- [Task Core](../../workflows/task-core.md) - Task system fundamentals
---
**Version**: 1.1.0
**Last Updated**: 2025-11-06
**Maintainer**: Claude DMS3 Team

View File

@@ -0,0 +1,64 @@
# CLI 智能工具指南
Gemini CLI 能够集成多种智能工具(如大型语言模型 LLM以增强您的开发工作流。本指南将帮助您理解这些智能工具如何工作以及如何有效地利用它们。
## 1. 什么是智能工具?
智能工具是集成到 Gemini CLI 中的高级 AI 模型,它们能够理解自然语言、分析代码、生成文本和代码,并协助完成复杂的开发任务。它们就像您的智能助手,可以自动化重复性工作,提供洞察,并帮助您做出更好的决策。
## 2. 核心工作原理
Gemini CLI 中的智能工具遵循以下核心原则:
- **上下文感知**: 工具会理解您当前的项目状态、代码内容和开发意图,从而提供更相关的建议和操作。这意味着它们不会“凭空”回答问题,而是基于您的实际工作环境提供帮助。
- **模块化**: 智能工具被设计为可互换的后端。您可以根据任务需求选择或组合不同的 LLM。例如某些模型可能擅长代码生成而另一些则擅长复杂推理。
- **自动化与增强**: 智能工具可以自动化重复或复杂的任务(如生成样板代码、基础重构、测试脚手架),并通过提供智能建议、解释和问题解决协助来增强您的开发能力。
- **用户控制与透明**: 您始终对工具的操作拥有最终控制权。工具会清晰地解释其建议的更改,并允许您轻松审查和修改。工具的选择和执行过程也是透明的。
详情可参考 `../../workflows/intelligent-tools-strategy.md`
## 3. 智能工具的应用场景
智能工具被集成到 CLI 工作流的多个关键点,以提供全面的帮助:
- **提示增强**: 优化您的输入提示,使智能工具更好地理解您的需求。
- **命令**: `enhance-prompt`
- **代码分析与审查**: 快速洞察代码,识别潜在问题,并提出改进建议。
- **命令**: `analyze`, `chat`, `code-analysis`, `bug-diagnosis`
- **规划与任务分解**: 协助将复杂问题分解为可管理的小任务,并生成实施计划。
- **命令**: `plan`, `discuss-plan`, `breakdown`
- **代码生成与实现**: 根据您的规范生成代码片段、函数、测试甚至整个模块。
- **命令**: `execute`, `create`, `codex-execute`
- **测试与调试**: 生成测试用例,诊断错误,并建议修复方案。
- **命令**: `test-gen`, `test-fix-gen`, `tdd-plan`, `tdd-verify`
- **文档生成**: 自动化代码、API 和项目模块的文档创建。
- **命令**: `docs`, `skill-memory`, `update-full`, `update-related`
- **工作流编排**: 智能选择和协调工具与代理来执行复杂的工作流。
- **命令**: `workflow:status`, `resume`, `plan`, `execute` (工作流级别)
## 4. 如何选择和使用工具
Gemini CLI 允许您使用 `--tool` 标志来指定用于特定操作的智能工具。这为您提供了灵活性,可以根据任务的性质选择最合适的模型。
- `--tool codex`: 优先使用 Codex或兼容的专注于代码的 LLM。非常适合精确的代码生成、重构和类似 linting 的任务。
- **何时使用**: 当您需要生成高质量代码、进行代码审查或修复代码错误时。
- `--tool gemini`: 优先使用 Gemini或兼容的通用 LLM。擅长复杂的推理、更广泛的分析、规划和自然语言理解任务。
- **何时使用**: 当您需要进行高层次的规划、理解复杂概念或进行广泛的代码库分析时。
- `--tool qwen`: 优先使用 Qwen或兼容的特定领域/语言 LLM。适用于需要专业知识或特定语言支持的任务。
- **何时使用**: 当您的项目涉及特定技术栈或需要特定语言的专业知识时。
- **(默认/自动)**: 如果未指定工具CLI 会根据任务上下文和可用配置智能地选择最合适的工具。
**示例**:
```bash
# 使用 Gemini 进行项目规划
gemini plan --tool gemini "设计一个新的微服务架构"
# 使用 Codex 生成代码
gemini execute --tool codex "task-id-for-code-generation"
# 使用 Qwen 分析特定领域的代码
gemini analyze --tool qwen "分析医疗数据处理模块"
```
通过理解这些智能工具及其用法,您可以更有效地利用 Gemini CLI加速您的开发过程。

View File

@@ -0,0 +1,537 @@
# Usage Examples
Comprehensive examples of command-guide skill in action across all 5 operation modes.
---
## Mode 1: Command Search 🔍
### Example 1: Keyword Search
**User**: "搜索包含 'execute' 的命令"
**Skill Response**:
```
找到 4 个相关命令:
1. **cli:execute** (高级)
描述: Auto-execution of implementation tasks with YOLO permissions
参数: [--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id
场景: implementation
2. **task:execute** (中级)
描述: Execute tasks with appropriate agents and context-aware orchestration
参数: task-id
场景: implementation
3. **workflow:execute** (中级)
描述: Coordinate agents for existing workflow tasks with automatic discovery
参数: [--resume-session="session-id"]
场景: implementation
4. **codex-execute** (高级)
描述: Automated task decomposition and execution with Codex
参数: task description or task-id
场景: implementation
💡 相关命令: workflow:plan, task:create
📖 详细文档: [Implementation Commands](workflow-patterns.md#implementation)
```
---
### Example 2: Category Search
**User**: "cli 类别下有哪些命令?"
**Skill Response**:
```
CLI 类别包含 9 个命令:
**核心命令** (6个):
- cli:analyze - Quick codebase analysis
- cli:chat - Direct codebase interaction
- cli:execute - Auto-execution with YOLO
- cli:cli-init - Initialize CLI tool configs
- cli:codex-execute - Codex-powered execution
- cli:discuss-plan - Multi-model planning discussion
**模式命令** (3个):
- cli:mode:plan - Project planning mode
- cli:mode:code-analysis - Deep code analysis mode
- cli:mode:bug-diagnosis - Bug diagnosis mode
📚 使用指南: [CLI Tools Guide](cli-tools-guide.md)
```
---
### Example 3: Use-Case Search
**User**: "planning 相关的命令有哪些?"
**Skill Response**:
```
Planning 场景包含 8 个命令:
**核心规划**:
1. workflow:plan (高级) - 5阶段规划工作流
2. cli:mode:plan (高级) - 项目规划和架构分析
3. workflow:tdd-plan (高级) - TDD 规划工作流
**任务分解**:
4. task:breakdown (中级) - 智能任务分解
5. workflow:tools:task-generate (中级) - 生成任务 JSON
**架构设计**:
6. workflow:brainstorm:system-architect (中级) - 系统架构师头脑风暴
7. workflow:brainstorm:api-designer (中级) - API 设计师头脑风暴
**评估验证**:
8. workflow:action-plan-verify (中级) - 规划质量验证
💡 常见工作流: Plan → Verify → Execute
📖 模式参考: [Workflow Patterns](workflow-patterns.md#planning-workflow)
```
---
## Mode 2: Smart Recommendations 🤖
### Example 1: After Planning
**User**: "执行完 /workflow:plan 后下一步做什么?"
**Skill Response**:
```
推荐的后续步骤:
**🎯 主要选择**:
1. **/workflow:execute** - 开始执行规划的任务
✅ 这是最常见的下一步
作用: 实际执行 workflow:plan 生成的任务
**📋 可选步骤**:
2. **/workflow:action-plan-verify** - 验证规划质量
作用: 在执行前检查规划的一致性和完整性
建议: 重要项目建议先验证
3. **/workflow:status** - 查看规划状态
作用: 查看生成的任务和当前进度
**📚 完整工作流模式**:
Plan → Verify (可选) → Execute → Review
详见: [Planning Workflow Pattern](workflow-patterns.md#planning-execution)
```
---
### Example 2: After Execution
**User**: "workflow:execute 执行完成后,推荐做什么?"
**Skill Response**:
```
推荐的后续步骤:
**🎯 主要选择**:
1. **/workflow:review** - 审查实现结果
✅ 检查代码质量、安全性、架构
参数: [--type=quality|security|architecture]
**📊 可选步骤**:
2. **/workflow:status** - 查看执行状态
作用: 确认所有任务都已完成
3. **/workflow:test-gen** - 生成测试
作用: 为实现的功能创建测试用例
4. **/workflow:session:complete** - 完成会话
作用: 标记工作流已完成,归档经验
**🔄 如果需要修改**:
- /task:replan - 重新规划某个任务
- /workflow:resume - 恢复工作流
详见: [Execution Review Pattern](workflow-patterns.md#execution-review)
```
---
## Mode 3: Full Documentation 📖
### Example 1: Command Parameters
**User**: "/workflow:plan 的参数是什么?"
**Skill Response**:
```
# workflow:plan
**描述**: Orchestrate 5-phase planning workflow with quality gate, executing commands and passing context between phases
**参数**:
```bash
/workflow:plan [--agent] [--cli-execute] "text description"|file.md
```
**参数说明**:
- `--agent` (可选): 使用 agent 模式执行规划
- `--cli-execute` (可选): 允许在规划阶段执行 CLI 命令
- `"text description"`: 任务描述文本
- `file.md`: 或者提供任务描述文件路径
**使用场景**: planning
**难度级别**: 高级
**使用示例**:
```bash
# 基本用法
/workflow:plan "实现用户认证功能"
# 使用 agent 模式
/workflow:plan --agent "重构支付模块"
# 从文件读取
/workflow:plan --agent feature-spec.md
# 允许 CLI 执行
/workflow:plan --cli-execute "添加搜索功能"
```
**执行流程**:
1. 上下文收集
2. 概念规划
3. 实现规划
4. 任务生成
5. 质量验证
**相关命令**:
- workflow:execute - 执行规划的任务
- workflow:action-plan-verify - 验证规划质量
- workflow:status - 查看规划状态
**详细文档**: ../../commands/workflow/plan.md
```
---
## Mode 4: Beginner Onboarding 🎓
### Example 1: Complete Beginner
**User**: "我是新手,如何开始使用工作流系统?"
**Skill Response**:
```
欢迎使用 Claude DMS3 工作流系统!🎉
## 🚀 快速开始3 步)
### Step 1: 了解核心命令Top 5
1. **/workflow:plan** - 规划一个功能或任务
用法: /workflow:plan "你想做的事情"
2. **/workflow:execute** - 执行规划的任务
用法: /workflow:execute
3. **/cli:execute** - 快速自动执行
用法: /cli:execute "实现XXX功能"
4. **/task:create** - 创建单个任务
用法: /task:create "任务标题"
5. **/enhance-prompt** - 优化你的提示词
用法: /enhance-prompt "你的想法"
### Step 2: 尝试第一个工作流
```bash
# 1. 规划一个简单功能
/workflow:plan "添加用户登录功能"
# 2. 执行规划
/workflow:execute
# 3. 审查结果
/workflow:review
```
### Step 3: 学习资源
📖 **必读指南**:
- [5分钟快速开始](getting-started.md)
- [常见工作流模式](workflow-patterns.md)
🛠️ **工具指南**:
- [CLI 工具使用](cli-tools-guide.md)
- [问题排查](troubleshooting.md)
💡 **下一步建议**:
1. 阅读 getting-started.md5分钟
2. 尝试上面的第一个工作流
3. 探索更多命令: 询问 "常用命令有哪些"
有问题随时问 "CCW-help"
```
---
### Example 2: Intermediate User
**User**: "常用命令有哪些?"
**Skill Response**:
```
## 核心命令列表Top 14
### 🎯 工作流管理 (5个)
1. workflow:plan - 5阶段规划
2. workflow:execute - 执行任务
3. workflow:review - 审查实现
4. workflow:tdd-plan - TDD 规划
5. workflow:test-gen - 生成测试
### 🛠️ CLI 工具 (3个)
6. cli:execute - 自动执行
7. cli:mode:plan - 规划模式
8. cli:analyze - 代码分析
### 📋 任务管理 (3个)
9. task:create - 创建任务
10. task:execute - 执行任务
11. task:breakdown - 分解任务
### 🔧 实用工具 (2个)
12. enhance-prompt - 提示词增强
13. version - 版本信息
### 💡 使用频率
- **每天**: workflow:plan, workflow:execute, cli:execute
- **经常**: task:create, enhance-prompt
- **按需**: workflow:review, test-gen, tdd-plan
📚 详细文档: [Index Structure](index-structure.md#essential-commands)
```
---
## Mode 5: Issue Reporting 📝
### Example 1: Bug Report
**User**: "CCW-issue"
**Skill (Interactive)**:
```
请选择问题类型:
1. 🐛 Bug 报告
2. ✨ 功能请求
3. ❓ 问题咨询
```
**User**: "1"
**Skill**:
```
好的,我将帮您创建 Bug 报告。请回答以下问题:
1. 简要描述问题:
```
**User**: "/workflow:plan 执行后没有生成任务文件"
**Skill**:
```
2. 您执行的完整命令是什么?
```
**User**: "/workflow:plan '添加登录功能'"
**Skill**:
```
3. 期望的结果是什么?
```
**User**: "应该在 .workflow/ 目录生成 task.json"
**Skill**:
```
4. 实际发生了什么?
```
**User**: "命令执行了但没有生成文件"
**Skill**:
```
✅ Bug 报告已生成!
文件路径: templates/.generated/bug-2025-01-06-123456.md
--- 报告内容 ---
# Bug 报告
## 问题描述
/workflow:plan 执行后没有生成任务文件
## 执行的命令
```bash
/workflow:plan '添加登录功能'
```
## 期望行为
应该在 .workflow/ 目录生成 task.json
## 实际行为
命令执行了但没有生成文件
## 环境信息
- 操作系统: Windows
- 报告日期: 2025-01-06
- 相关命令: /workflow:plan
---
**下一步操作**:
1. 复制以上内容到 GitHub Issues
2. 或使用: gh issue create -F templates/.generated/bug-2025-01-06-123456.md
需要更多帮助?使用 "CCW-help"
```
---
### Example 2: Feature Request
**User**: "我想提个功能建议"
**Skill (Interactive)**:
```
请选择问题类型:
1. 🐛 Bug 报告
2. ✨ 功能请求
3. ❓ 问题咨询
```
**User**: "2"
**Skill**:
```
好的,功能请求。请描述:
1. 您希望添加什么功能?
```
**User**: "希望 /workflow:plan 能自动估算任务时间"
**Skill**:
```
2. 这个功能解决什么问题?
```
**User**: "帮助更好地规划项目进度和资源分配"
**Skill**:
```
3. 具体的使用场景是什么?(可选)
```
**User**: "规划大型项目时,能看到预计完成时间"
**Skill**:
```
✅ 功能请求已生成!
文件路径: templates/.generated/feature-2025-01-06-123457.md
--- 内容预览 ---
# 功能请求
## 功能概述
希望 /workflow:plan 能自动估算任务时间
## 问题背景
帮助更好地规划项目进度和资源分配
## 使用场景
规划大型项目时,能看到预计完成时间
## 优先级
- [ ] 高 - 严重影响工作效率
- [x] 中 - 有明显改善但有变通方案
- [ ] 低 - 锦上添花
---
可以复制到 GitHub 提交,或使用:
gh issue create -F templates/.generated/feature-2025-01-06-123457.md
```
---
## Edge Cases & Error Handling
### Case 1: No Results Found
**User**: "搜索 xyz 命令"
**Skill**:
```
❌ 未找到包含 "xyz" 的命令
💡 建议:
1. 尝试更广泛的关键词(如 "plan", "execute", "test"
2. 按类别浏览workflow, cli, memory, task
3. 查看所有常用命令:询问 "常用命令"
4. 需要帮助:使用 "CCW-help"
📚 快速参考:[All Commands Index](index-structure.md#all-commands)
```
---
### Case 2: Ambiguous Query
**User**: "命令"
**Skill**:
```
您想了解什么?请选择:
1. 🔍 搜索特定命令
2. 🤖 获取命令推荐
3. 📖 查看命令文档
4. 🎓 新手入门指导
5. 📝 报告问题或建议
或者直接说出具体需求,例如:
- "搜索 planning 命令"
- "执行完 /workflow:plan 下一步做什么"
- "/task:create 怎么用"
```
---
### Case 3: Multiple Matches
**User**: "execute 命令"
**Skill**:
```
找到多个相关命令,请选择您需要的:
1. **cli:execute** - CLI 自动执行(推荐新手)
2. **task:execute** - 执行单个任务
3. **workflow:execute** - 执行整个工作流
或者询问:
- "cli:execute 的详细文档"
- "三者有什么区别"
- "我该用哪个"
```
---
**Last Updated**: 2025-01-06

View File

@@ -0,0 +1,95 @@
# 5分钟快速上手指南
欢迎来到 Gemini CLI本指南将帮助您快速了解核心命令并通过一个简单的工作流示例让您在5分钟内开始使用。
## 1. Gemini CLI 简介
Gemini CLI 是一个强大的命令行工具,旨在通过智能代理和自动化工作流,提升您的开发效率。它能够帮助您进行代码分析、任务规划、代码生成、测试以及文档编写等。
## 2. 核心命令速览
以下是一些您将频繁使用的核心命令:
### `version` - 查看版本信息
- **用途**: 检查当前 CLI 版本并获取更新信息。
- **示例**:
```bash
gemini version
```
### `enhance-prompt` - 智能提示增强
- **用途**: 根据当前会话记忆和代码库分析,智能地优化您的输入提示,让代理更好地理解您的意图。
- **示例**:
```bash
gemini enhance-prompt "如何修复这个bug"
```
### `analyze` - 快速代码分析
- **用途**: 使用 CLI 工具(如 Codex, Gemini, Qwen对代码库进行快速分析获取洞察。
- **示例**:
```bash
gemini analyze "分析 src/main.py 中的性能瓶颈"
```
### `chat` - 交互式对话
- **用途**: 与 CLI 进行简单的交互式对话,直接进行代码分析或提问。
- **示例**:
```bash
gemini chat "解释一下 UserService.java 的主要功能"
```
### `plan` - 项目规划与架构分析
- **用途**: 启动项目规划和架构分析工作流,帮助您将复杂问题分解为可执行的任务。
- **示例**:
```bash
gemini plan "实现用户认证模块"
```
### `create` - 创建实现任务
- **用途**: 根据上下文创建具体的实现任务。
- **示例**:
```bash
gemini create "编写用户注册接口"
```
### `execute` - 自动执行任务
- **用途**: 自动执行实现任务,智能地推断上下文并协调代理完成工作。
- **示例**:
```bash
gemini execute "task-id-123"
```
## 3. 第一个工作流示例:规划与执行一个简单任务
让我们通过一个简单的例子来体验 Gemini CLI 的工作流:**规划并实现一个“Hello World”函数**。
1. **规划任务**:
首先,我们使用 `plan` 命令来规划我们的“Hello World”功能。
```bash
gemini plan "实现一个打印 'Hello World!' 的 Python 函数"
```
CLI 将会启动一个规划工作流,可能会询问您一些问题,并最终生成一个或多个任务。
2. **创建具体任务**:
假设 `plan` 命令为您生成了一个任务 ID或者您想手动创建一个任务。
```bash
gemini create "编写 Python 函数 `say_hello` 打印 'Hello World!'"
```
这个命令会创建一个新的任务,并返回一个任务 ID。
3. **执行任务**:
现在,我们使用 `execute` 命令来让 CLI 自动完成这个任务。请将 `your-task-id` 替换为上一步中获得的实际任务 ID。
```bash
gemini execute "your-task-id"
```
CLI 将会调用智能代理,根据任务描述生成代码,并尝试将其写入文件。
通过这三个简单的步骤,您就完成了一个从规划到执行的完整工作流。
## 4. 接下来做什么?
- 探索更多命令:使用 `gemini help` 查看所有可用命令。
- 查阅其他指南深入了解工作流模式、CLI 工具使用和故障排除。
- 尝试更复杂的任务:挑战自己,使用 Gemini CLI 解决实际项目中的问题。
祝您使用愉快!

View File

@@ -0,0 +1,526 @@
# Implementation Details
Detailed implementation logic for command-guide skill operation modes.
## Architecture Overview
```
User Query
Intent Recognition
Mode Selection (1 of 5)
Index/File Query
Response Formation
User Output + Recommendations
```
---
## Intent Recognition
### Step 1: Parse User Input
Analyze query for trigger keywords and patterns:
```javascript
function recognizeIntent(userQuery) {
const query = userQuery.toLowerCase();
// Mode 5: Issue Reporting (highest priority)
if (query.includes('ccw-issue') || query.includes('ccw-help') ||
query.match(/报告.*bug/) || query.includes('功能建议')) {
return 'ISSUE_REPORTING';
}
// Mode 1: Command Search
if (query.includes('搜索') || query.includes('find') ||
query.includes('search') || query.match(/.*相关.*命令/)) {
return 'COMMAND_SEARCH';
}
// Mode 2: Recommendations
if (query.includes('下一步') || query.includes("what's next") ||
query.includes('推荐') || query.match(/after.*\/\w+:\w+/)) {
return 'RECOMMENDATIONS';
}
// Mode 3: Documentation
if (query.includes('参数') || query.includes('怎么用') ||
query.includes('如何使用') || query.match(/\/\w+:\w+.*详情/)) {
return 'DOCUMENTATION';
}
// Mode 4: Onboarding
if (query.includes('新手') || query.includes('入门') ||
query.includes('getting started') || query.includes('常用命令')) {
return 'ONBOARDING';
}
// Default: Ask for clarification
return 'CLARIFY';
}
```
---
## Mode 1: Command Search 🔍
### Trigger Analysis
**Keywords**: 搜索, find, search, [topic] 相关命令
**Examples**:
- "搜索 planning 命令"
- "find commands for testing"
- "实现相关的命令有哪些"
### Processing Flow
```
1. Extract Search Parameters
2. Determine Search Type
├─ Keyword Search (in name/description)
├─ Category Search (workflow/cli/memory/task)
└─ Use-Case Search (planning/implementation/testing)
3. Query Appropriate Index
├─ Keyword → all-commands.json
├─ Category → by-category.json
└─ Use-Case → by-use-case.json
4. Filter and Rank Results
5. Format Response
├─ List matching commands
├─ Show key metadata (name, description, args)
└─ Suggest related commands
```
### Implementation
```javascript
async function searchCommands(query, searchType) {
let results = [];
switch (searchType) {
case 'keyword':
// Load all-commands.json
const allCommands = await readIndex('all-commands.json');
results = allCommands.filter(cmd =>
cmd.name.toLowerCase().includes(query.toLowerCase()) ||
cmd.description.toLowerCase().includes(query.toLowerCase())
);
break;
case 'category':
// Load by-category.json
const byCategory = await readIndex('by-category.json');
const category = extractCategory(query); // e.g., "workflow"
results = flattenCategory(byCategory[category]);
break;
case 'use-case':
// Load by-use-case.json
const byUseCase = await readIndex('by-use-case.json');
const useCase = extractUseCase(query); // e.g., "planning"
results = byUseCase[useCase] || [];
break;
}
// Rank by relevance
results = rankResults(results, query);
// Add related commands
results = await enrichWithRelated(results);
return results;
}
```
---
## Mode 2: Smart Recommendations 🤖
### Trigger Analysis
**Keywords**: 下一步, what's next, 推荐, after [command]
**Examples**:
- "执行完 /workflow:plan 后做什么?"
- "What's next after planning?"
- "推荐下一个命令"
### Processing Flow
```
1. Extract Context
├─ Current/Last Command
├─ Workflow State
└─ User's Current Task
2. Query Relationships
└─ Load command-relationships.json
3. Find Next Steps
├─ Check next_steps array
├─ Consider prerequisites
└─ Check related_commands
4. Generate Recommendations
├─ Primary recommendation (most common next step)
├─ Alternative options
└─ Rationale for each
5. Add Workflow Context
└─ Link to workflow-patterns.md
```
### Implementation
```javascript
async function getRecommendations(currentCommand) {
// Load relationships
const relationships = await readIndex('command-relationships.json');
// Get relationship data
const cmdData = relationships[currentCommand];
if (!cmdData) {
return defaultRecommendations();
}
// Primary next steps
const nextSteps = cmdData.next_steps || [];
// Alternative related commands
const alternatives = cmdData.related_commands || [];
// Build recommendations
const recommendations = {
primary: await enrichCommand(nextSteps[0]),
alternatives: await enrichCommands(alternatives),
workflow_pattern: findWorkflowPattern(currentCommand),
rationale: generateRationale(currentCommand, nextSteps[0])
};
return recommendations;
}
```
---
## Mode 3: Full Documentation 📖
### Trigger Analysis
**Keywords**: 参数, 怎么用, 如何使用, [command] 详情
**Examples**:
- "/workflow:plan 的参数是什么?"
- "如何使用 /cli:execute"
- "task:create 详细文档"
### Processing Flow
```
1. Extract Command Name
└─ Parse /workflow:plan or workflow:plan
2. Locate in Index
└─ Search all-commands.json
3. Read Full Command File
└─ Use file_path from index
4. Extract Documentation
├─ Parameters section
├─ Arguments specification
├─ Examples section
└─ Best practices
5. Format Response
├─ Command overview
├─ Full parameter list
├─ Usage examples
└─ Related commands
```
### Implementation
```javascript
async function getDocumentation(commandName) {
// Normalize command name
const normalized = normalizeCommandName(commandName);
// Find in index
const allCommands = await readIndex('all-commands.json');
const command = allCommands.find(cmd => cmd.name === normalized);
if (!command) {
return { error: 'Command not found' };
}
// Read full command file
const commandFilePath = path.join(
'../commands',
command.file_path
);
const fullDoc = await readCommandFile(commandFilePath);
// Parse sections
const documentation = {
name: command.name,
description: command.description,
arguments: command.arguments,
difficulty: command.difficulty,
usage_scenario: command.usage_scenario,
parameters: extractSection(fullDoc, '## Parameters'),
examples: extractSection(fullDoc, '## Examples'),
best_practices: extractSection(fullDoc, '## Best Practices'),
related: await getRelatedCommands(command.name)
};
return documentation;
}
```
---
## Mode 4: Beginner Onboarding 🎓
### Trigger Analysis
**Keywords**: 新手, 入门, getting started, 常用命令, 如何开始
**Examples**:
- "我是新手,如何开始?"
- "getting started with workflows"
- "最常用的命令有哪些?"
### Processing Flow
```
1. Assess User Level
└─ Identify as beginner
2. Load Essential Commands
└─ Read essential-commands.json
3. Build Learning Path
├─ Step 1: Core commands (Top 5)
├─ Step 2: Basic workflow
├─ Step 3: Intermediate commands
└─ Step 4: Advanced features
4. Provide Resources
├─ Link to getting-started.md
├─ Link to workflow-patterns.md
└─ Suggest first task
5. Interactive Guidance
└─ Offer to walk through first workflow
```
### Implementation
```javascript
async function onboardBeginner() {
// Load essential commands
const essentialCommands = await readIndex('essential-commands.json');
// Group by difficulty
const beginner = essentialCommands.filter(cmd =>
cmd.difficulty === 'Beginner' || cmd.difficulty === 'Intermediate'
);
// Create learning path
const learningPath = {
step1: {
title: 'Core Commands (Start Here)',
commands: beginner.slice(0, 5),
guide: 'guides/getting-started.md'
},
step2: {
title: 'Your First Workflow',
pattern: 'Plan → Execute',
commands: ['workflow:plan', 'workflow:execute'],
guide: 'guides/workflow-patterns.md#basic-workflow'
},
step3: {
title: 'Intermediate Skills',
commands: beginner.slice(5, 10),
guide: 'guides/workflow-patterns.md#common-patterns'
}
};
// Resources
const resources = {
getting_started: 'guides/getting-started.md',
workflow_patterns: 'guides/workflow-patterns.md',
cli_tools: 'guides/cli-tools-guide.md',
troubleshooting: 'guides/troubleshooting.md'
};
return {
learning_path: learningPath,
resources: resources,
first_task: 'Try: /workflow:plan "create a simple feature"'
};
}
```
---
## Mode 5: Issue Reporting 📝
### Trigger Analysis
**Keywords**: CCW-issue, CCW-help, 报告 bug, 功能建议, 问题咨询
**Examples**:
- "CCW-issue"
- "我要报告一个 bug"
- "CCW-help 有问题"
- "想提个功能建议"
### Processing Flow
```
1. Detect Issue Type
└─ Use AskUserQuestion if unclear
2. Select Template
├─ Bug → templates/issue-bug.md
├─ Feature → templates/issue-feature.md
└─ Question → templates/issue-question.md
3. Collect Information
└─ Interactive Q&A
├─ Problem description
├─ Steps to reproduce (bug)
├─ Expected vs actual (bug)
├─ Use case (feature)
└─ Context
4. Generate Filled Template
└─ Populate template with collected data
5. Save or Display
├─ Save to templates/.generated/
└─ Display for user to copy
```
### Implementation
```javascript
async function reportIssue(issueType) {
// Determine type (bug/feature/question)
if (!issueType) {
issueType = await askUserQuestion({
question: 'What type of issue would you like to report?',
options: ['Bug Report', 'Feature Request', 'Question']
});
}
// Select template
const templatePath = {
'bug': 'templates/issue-bug.md',
'feature': 'templates/issue-feature.md',
'question': 'templates/issue-question.md'
}[issueType.toLowerCase()];
const template = await readTemplate(templatePath);
// Collect information
const info = await collectIssueInfo(issueType);
// Fill template
const filledTemplate = fillTemplate(template, {
...info,
timestamp: new Date().toISOString(),
auto_context: gatherAutoContext()
});
// Save
const outputPath = `templates/.generated/${issueType}-${Date.now()}.md`;
await writeFile(outputPath, filledTemplate);
return {
template: filledTemplate,
file_path: outputPath,
instructions: 'Copy content to GitHub Issues or use: gh issue create -F ' + outputPath
};
}
```
---
## Error Handling
### Not Found
```javascript
if (results.length === 0) {
return {
message: 'No commands found matching your query.',
suggestions: [
'Try broader keywords',
'Browse by category: workflow, cli, memory, task',
'View all commands: essential-commands.json',
'Need help? Ask: "CCW-help"'
]
};
}
```
### Ambiguous Intent
```javascript
if (intent === 'CLARIFY') {
return await askUserQuestion({
question: 'What would you like to do?',
options: [
'Search for commands',
'Get recommendations for next steps',
'View command documentation',
'Learn how to get started',
'Report an issue or get help'
]
});
}
```
---
## Optimization Strategies
### Caching
```javascript
// Cache indexes in memory after first load
const indexCache = new Map();
async function readIndex(filename) {
if (indexCache.has(filename)) {
return indexCache.get(filename);
}
const data = await readFile(`index/${filename}`);
const parsed = JSON.parse(data);
indexCache.set(filename, parsed);
return parsed;
}
```
### Lazy Loading
```javascript
// Only load full command files when needed
// Use index metadata for most queries
// Read command file only for Mode 3 (Documentation)
```
---
**Last Updated**: 2025-01-06

View File

@@ -0,0 +1,326 @@
# Index Structure Reference
Complete documentation for command index files and their data structures.
## Overview
The command-guide skill uses 5 JSON index files to organize and query 69 commands across the Claude DMS3 workflow system.
## Index Files
### 1. `all-commands.json`
**Purpose**: Complete catalog of all commands with full metadata
**Use Cases**:
- Full-text search across all commands
- Detailed command queries
- Batch operations
- Reference lookup
**Structure**:
```json
[
{
"name": "workflow:plan",
"description": "Orchestrate 5-phase planning workflow with quality gate",
"arguments": "[--agent] [--cli-execute] \"text description\"|file.md",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/plan.md"
},
...
]
```
**Fields**:
- `name` (string): Command name (e.g., "workflow:plan")
- `description` (string): Brief functional description
- `arguments` (string): Parameter specification
- `category` (string): Primary category (workflow/cli/memory/task)
- `subcategory` (string|null): Secondary grouping if applicable
- `usage_scenario` (string): Primary use case (planning/implementation/testing/etc.)
- `difficulty` (string): Skill level (Beginner/Intermediate/Advanced)
- `file_path` (string): Relative path to command file
**Total Records**: 69 commands
---
### 2. `by-category.json`
**Purpose**: Hierarchical organization by category and subcategory
**Use Cases**:
- Browse commands by category
- Category-specific listings
- Hierarchical navigation
- Understanding command organization
**Structure**:
```json
{
"workflow": {
"core": [
{
"name": "workflow:plan",
"description": "...",
...
}
],
"brainstorm": [...],
"session": [...],
"tools": [...],
"ui-design": [...]
},
"cli": {
"mode": [...],
"core": [...]
},
"memory": [...],
"task": [...]
}
```
**Category Breakdown**:
- **workflow** (46 commands):
- core: 11 commands
- brainstorm: 12 commands
- session: 4 commands
- tools: 9 commands
- ui-design: 10 commands
- **cli** (9 commands):
- mode: 3 commands
- core: 6 commands
- **memory** (8 commands)
- **task** (4 commands)
- **general** (2 commands)
---
### 3. `by-use-case.json`
**Purpose**: Commands organized by practical usage scenarios
**Use Cases**:
- Task-oriented command discovery
- "I want to do X" queries
- Workflow planning
- Learning paths
**Structure**:
```json
{
"planning": [
{
"name": "workflow:plan",
"description": "...",
...
},
...
],
"implementation": [...],
"testing": [...],
"documentation": [...],
"session-management": [...],
"general": [...]
}
```
**Use Case Categories**:
- **planning**: Architecture, task breakdown, design
- **implementation**: Coding, development, execution
- **testing**: Test generation, TDD, quality assurance
- **documentation**: Docs generation, memory management
- **session-management**: Workflow control, resumption
- **general**: Utilities, versioning, prompt enhancement
---
### 4. `essential-commands.json`
**Purpose**: Curated list of 10-15 most frequently used commands
**Use Cases**:
- Quick reference for beginners
- Onboarding new users
- Common workflow starters
- Cheat sheet
**Structure**:
```json
[
{
"name": "enhance-prompt",
"description": "Context-aware prompt enhancement",
"arguments": "\"user input to enhance\"",
"category": "general",
"subcategory": null,
"usage_scenario": "general",
"difficulty": "Intermediate",
"file_path": "enhance-prompt.md"
},
...
]
```
**Selection Criteria**:
- Frequency of use in common workflows
- Value for beginners
- Core functionality coverage
- Minimal overlap in capabilities
**Current Count**: 14 commands
**List**:
1. `enhance-prompt` - Prompt enhancement
2. `version` - Version info
3. `cli:analyze` - Quick codebase analysis
4. `cli:chat` - Direct CLI interaction
5. `cli:execute` - Auto-execution
6. `cli:mode:plan` - Planning mode
7. `task:breakdown` - Task decomposition
8. `task:create` - Create tasks
9. `task:execute` - Execute tasks
10. `workflow:execute` - Run workflows
11. `workflow:plan` - Plan workflows
12. `workflow:review` - Review implementation
13. `workflow:tdd-plan` - TDD planning
14. `workflow:test-gen` - Test generation
---
### 5. `command-relationships.json`
**Purpose**: Mapping of command dependencies and common sequences
**Use Cases**:
- Next-step recommendations
- Workflow pattern suggestions
- Related command discovery
- Smart navigation
**Structure**:
```json
{
"workflow:plan": {
"related_commands": [
"workflow:execute",
"workflow:action-plan-verify"
],
"next_steps": ["workflow:execute"],
"prerequisites": []
},
"workflow:execute": {
"related_commands": [
"workflow:status",
"workflow:resume",
"workflow:review"
],
"next_steps": ["workflow:review", "workflow:status"],
"prerequisites": ["workflow:plan"]
},
...
}
```
**Fields**:
- `related_commands` (array): Commonly used together
- `next_steps` (array): Typical next commands
- `prerequisites` (array): Usually run before this command
**Relationship Types**:
1. **Sequential**: A → B (plan → execute)
2. **Alternatives**: A | B (execute OR codex-execute)
3. **Built-in**: A includes B (plan auto-includes context-gather)
---
## Query Patterns
### Pattern 1: Keyword Search
```javascript
// Search by keyword in name or description
const results = allCommands.filter(cmd =>
cmd.name.includes(keyword) ||
cmd.description.toLowerCase().includes(keyword.toLowerCase())
);
```
### Pattern 2: Category Browse
```javascript
// Get all commands in a category
const workflowCommands = byCategory.workflow;
const coreWorkflow = byCategory.workflow.core;
```
### Pattern 3: Use-Case Lookup
```javascript
// Find commands for specific use case
const planningCommands = byUseCase.planning;
```
### Pattern 4: Related Commands
```javascript
// Get next steps after a command
const nextSteps = commandRelationships["workflow:plan"].next_steps;
```
### Pattern 5: Essential Commands
```javascript
// Get beginner-friendly quick reference
const quickStart = essentialCommands;
```
---
## Maintenance
### Regenerating Indexes
When commands are added/modified/removed:
```bash
bash scripts/update-index.sh
```
The script will:
1. Scan all .md files in commands/
2. Extract metadata from YAML frontmatter
3. Analyze command relationships
4. Identify essential commands
5. Generate all 5 index files
### Validation Checklist
After regeneration, verify:
- [ ] All 5 JSON files are valid (no syntax errors)
- [ ] Total command count matches (currently 69)
- [ ] No missing fields in records
- [ ] Category breakdown correct
- [ ] Essential commands reasonable (10-15)
- [ ] Relationships make logical sense
---
## Performance Considerations
**Index Sizes**:
- `all-commands.json`: ~28KB
- `by-category.json`: ~31KB
- `by-use-case.json`: ~29KB
- `command-relationships.json`: ~7KB
- `essential-commands.json`: ~5KB
**Total**: ~100KB (fast to load)
**Query Speed**:
- In-memory search: < 1ms
- File read + parse: < 50ms
- Recommended: Load indexes once, cache in memory
---
**Last Updated**: 2025-01-06

View File

@@ -0,0 +1,92 @@
# 常见问题与解决方案
在使用 Gemini CLI 的过程中,您可能会遇到一些问题。本指南旨在帮助您诊断和解决这些常见问题,确保您能顺利使用 CLI。
## 1. 命令执行失败或未找到
**问题描述**:
- 您输入的命令没有响应,或者系统提示“命令未找到”。
- 命令执行后出现错误信息,但您不理解其含义。
**可能原因**:
- 命令拼写错误。
- CLI 未正确安装或环境变量配置不正确。
- 命令所需的依赖项缺失。
- 命令参数不正确或缺失。
**解决方案**:
1. **检查拼写**: 仔细核对您输入的命令是否正确,包括命令名称和任何参数。
2. **查看帮助**: 使用 `gemini help``gemini [command-name] --help` 来查看命令的正确用法、可用参数和示例。
3. **验证安装**: 确保 Gemini CLI 已正确安装,并且其可执行文件路径已添加到系统的环境变量中。您可以尝试重新安装 CLI。
4. **检查日志**: CLI 通常会生成日志文件。查看这些日志可以提供更详细的错误信息,帮助您定位问题。
5. **更新 CLI**: 确保您使用的是最新版本的 Gemini CLI。旧版本可能存在已知错误通过 `gemini version` 检查并更新。
## 2. 权限问题
**问题描述**:
- CLI 尝试读取、写入或创建文件/目录时,提示“权限被拒绝”或类似错误。
- 某些操作(如安装依赖、修改系统配置)失败。
**可能原因**:
- 当前用户没有足够的权限执行该操作。
- 文件或目录被其他程序占用。
**解决方案**:
1. **以管理员身份运行**: 尝试以管理员权限Windows或使用 `sudo`Linux/macOS运行您的终端或命令提示符。
```bash
# Windows (在命令提示符或 PowerShell 中右键选择“以管理员身份运行”)
# Linux/macOS
sudo gemini [command]
```
2. **检查文件/目录权限**: 确保您对目标文件或目录拥有读/写/执行权限。您可能需要使用 `chmod` (Linux/macOS) 或修改文件属性 (Windows) 来更改权限。
3. **关闭占用程序**: 确保没有其他程序正在使用您尝试访问的文件或目录。
## 3. 配置问题
**问题描述**:
- CLI 行为异常,例如无法连接到 LLM 服务,或者某些功能无法正常工作。
- 提示缺少 API 密钥或配置项。
**可能原因**:
- 配置文件(如 `.gemini.json` 或相关环境变量)设置不正确。
- API 密钥过期或无效。
- 网络连接问题导致无法访问外部服务。
**解决方案**:
1. **检查配置文件**: 仔细检查 Gemini CLI 的配置文件通常位于用户主目录或项目根目录中的设置。确保所有路径、API 密钥和选项都正确无误。
2. **验证环境变量**: 确认所有必要的环境变量(如 `GEMINI_API_KEY`)都已正确设置。
3. **网络连接**: 检查您的网络连接是否正常,并确保没有防火墙或代理设置阻止 CLI 访问外部服务。
4. **重新初始化配置**: 对于某些配置问题,您可能需要使用 `gemini cli-init` 命令重新初始化 CLI 配置。
```bash
gemini cli-init
```
## 4. 智能代理 (LLM) 相关问题
**问题描述**:
- 智能代理的响应质量不佳,不相关或不准确。
- 代理响应速度慢,或提示达到速率限制。
**可能原因**:
- 提示不够清晰或缺乏上下文。
- 选择了不适合当前任务的 LLM 模型。
- LLM 服务提供商的速率限制或服务中断。
**解决方案**:
1. **优化提示**: 尝试使用 `enhance-prompt` 命令来优化您的输入,提供更清晰、更具体的上下文信息。
2. **选择合适的工具**: 根据任务类型,使用 `--tool` 标志选择最合适的 LLM 模型(如 `codex` 适用于代码生成,`gemini` 适用于复杂推理)。
```bash
gemini analyze --tool gemini "分析这个复杂算法"
```
3. **检查 API 密钥和配额**: 确保您的 LLM 服务 API 密钥有效,并且没有超出使用配额。
4. **重试或等待**: 如果是速率限制或服务中断,请稍后重试或联系服务提供商。
## 5. 寻求帮助
如果以上解决方案都无法解决您的问题,您可以:
- **查阅官方文档**: 访问 Gemini CLI 的官方文档获取更全面的信息。
- **社区支持**: 在相关的开发者社区或论坛中提问。
- **提交问题**: 如果您认为是 CLI 的 bug请在项目的问题跟踪器中提交详细的问题报告。
希望本指南能帮助您解决遇到的问题,让您更好地利用 Gemini CLI

View File

@@ -0,0 +1,100 @@
# 常见工作流模式
Gemini CLI 不仅提供单个命令,更能通过智能编排将一系列命令组合成强大的工作流,帮助您高效完成复杂任务。本指南将介绍几种常见的工作流模式。
## 1. 工作流核心概念
在深入了解具体模式之前理解工作流的架构至关重要。Gemini CLI 的工作流管理系统旨在提供一个灵活、可扩展的框架,用于定义、执行和协调复杂的开发任务。
- **工作流 (Workflows)**:一系列任务的组合,旨在实现特定的开发目标。
- **任务 (Tasks)**:工作流中的独立工作单元,可以简单也可以复杂,有状态、输入和输出。
- **智能体 (Agents)**:通常由大型语言模型驱动,负责执行任务或在工作流中做出决策。
- **上下文 (Context)**:当前工作流的相关动态信息,包括项目状态、代码片段、文档、用户输入等,是智能决策的关键。
- **记忆 (Memory)**:持久存储上下文、工作流历史和学习模式,支持工作流的恢复、适应和改进。
详情可参考 `../../workflows/workflow-architecture.md`
## 2. 规划 -> 执行 (Plan -> Execute) 模式
这是最基础也是最常用的工作流模式,它将一个大的目标分解为可执行的步骤,并逐步实现。
**场景**: 您有一个需要从头开始实现的新功能或模块。
**主要命令**:
- `plan`: 启动高级规划过程,分解目标。
- `breakdown`: 进一步细化和分解 `plan` 生成的任务。
- `create`: 创建具体的实施任务。
- `execute`: 执行创建好的任务以实现代码或解决方案。
**工作流示例**:
1. **启动规划**: `gemini plan "开发一个用户认证服务"`
- CLI 会与您互动,明确需求,并生成一个初步的规划(可能包含多个子任务)。
2. **任务分解** (可选,如果规划足够细致可跳过):
- 假设 `plan` 产生了一个任务 ID `task-auth-service`
- `gemini breakdown task-auth-service`
- 可能进一步分解为 `task-register`, `task-login`, `task-password-reset`等。
3. **创建具体实现任务**:
- `gemini create "实现用户注册 API 接口"`
- 这会生成一个专门针对此任务的 ID例如 `task-id-register-api`
4. **执行实现任务**:
- `gemini execute task-id-register-api`
- CLI 将调用智能体自动编写和集成代码。
## 3. 测试驱动开发 (TDD) 模式
TDD 模式强调先编写测试再编写满足测试的代码然后重构。Gemini CLI 通过自动化 TDD 流程来支持这一模式。
**场景**: 您正在开发一个新功能,并希望通过 TDD 确保代码质量和正确性。
**主要命令**:
- `tdd-plan`: 规划 TDD 工作流,生成红-绿-重构任务链。
- `test-gen`: 根据功能描述生成测试用例。
- `execute`: 执行代码生成和测试。
- `tdd-verify`: 验证 TDD 工作流的合规性并生成质量报告。
**工作流示例**:
1. **TDD 规划**: `gemini tdd-plan "实现一个购物车功能"`
- CLI 将为您创建一个 TDD 任务链,包括测试生成、代码实现和验证。
2. **生成测试**: (通常包含在 `tdd-plan` 的早期阶段,或可以单独调用)
- `gemini test-gen source-session-id` (如果已有一个实现会话)
- 这会产生失败的测试(红)。
3. **执行代码实现和测试**:
- `gemini execute task-id-for-code-implementation`
- 智能体会编写代码以通过测试,并将执行测试(变为绿)。
4. **TDD 验证**: `gemini tdd-verify`
- 验证整个 TDD 周期是否规范执行,以及生成测试覆盖率等报告。
## 4. UI 设计与实现工作流
Gemini CLI 可以辅助您进行 UI 的设计、提取和代码生成,加速前端开发。
**场景**: 您需要基于一些设计稿或现有网站来快速构建 UI 原型或实现页面。
**主要命令**:
- `ui-designer`: 启动 UI 设计分析。
- `layout-extract`: 从参考图像或 URL 提取布局信息。
- `style-extract`: 从参考图像或 URL 提取设计风格。
- `generate`: 组合布局和设计令牌生成 UI 原型。
- `update`: 使用最终设计系统参考更新设计产物。
**工作流示例**:
1. **启动 UI 设计分析**: `gemini ui-designer`
- 开始一个引导式的流程,定义您的 UI 设计目标。
2. **提取布局**: `gemini layout-extract --urls "https://example.com/some-page"`
- 从给定 URL 提取页面布局结构。
3. **提取样式**: `gemini style-extract --images "./design-mockup.png"`
- 从设计图中提取颜色、字体等视觉风格。
4. **生成 UI 原型**: `gemini generate --base-path ./my-ui-project`
- 结合提取的布局和样式,生成可工作的 UI 代码或原型。
5. **更新与迭代**: `gemini update --session ui-design-session-id --selected-prototypes "proto-01,proto-03"`
- 根据反馈和最终设计系统,迭代并更新生成的 UI 产物。
## 5. 上下文搜索策略
所有这些工作流都依赖于高效的上下文管理。Gemini CLI 采用多层次的上下文搜索策略,以确保智能代理获得最相关的信息。
- **相关性优先**: 优先收集与当前任务直接相关的上下文,而非大量数据。
- **分层搜索**: 从最直接的来源(如当前打开文件)开始,逐步扩展到项目文件、记忆库和外部资源。
- **语义理解**: 利用智能搜索理解查询的意图,而非仅仅是关键词匹配。
更多细节请查阅 `../../workflows/context-search-strategy.md`

View File

@@ -0,0 +1,692 @@
[
{
"name": "cli:analyze",
"description": "Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/analyze.md"
},
{
"name": "cli:chat",
"description": "Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/chat.md"
},
{
"name": "cli:cli-init",
"description": "Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection",
"arguments": "[--tool gemini|qwen|all] [--output path] [--preview]",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/cli-init.md"
},
{
"name": "cli:codex-execute",
"description": "Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity",
"arguments": "[--verify-git] task description or task-id",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/codex-execute.md"
},
{
"name": "cli:discuss-plan",
"description": "Multi-round collaborative planning using Gemini, Codex, and Claude synthesis with iterative discussion cycles (read-only, no code changes)",
"arguments": "[--topic '...'] [--task-id '...'] [--rounds N]",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/discuss-plan.md"
},
{
"name": "cli:execute",
"description": "Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/execute.md"
},
{
"name": "cli:mode:bug-diagnosis",
"description": "Read-only bug root cause analysis using Gemini/Qwen/Codex with systematic diagnosis template for fix suggestions",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] bug description",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "analysis",
"difficulty": "Intermediate",
"file_path": "cli/mode/bug-diagnosis.md"
},
{
"name": "cli:mode:code-analysis",
"description": "Read-only execution path tracing using Gemini/Qwen/Codex with specialized analysis template for call flow and optimization",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] analysis target",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "cli/mode/code-analysis.md"
},
{
"name": "cli:mode:plan",
"description": "Read-only architecture planning using Gemini/Qwen/Codex with strategic planning template for modification plans and impact analysis",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] topic",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "cli/mode/plan.md"
},
{
"name": "enhance-prompt",
"description": "Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection",
"arguments": "user input to enhance",
"category": "general",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "enhance-prompt.md"
},
{
"name": "memory:docs",
"description": "Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs",
"arguments": "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "memory/docs.md"
},
{
"name": "memory:load-skill-memory",
"description": "Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords",
"arguments": "[skill_name] \\\"task intent description\\\"",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/load-skill-memory.md"
},
{
"name": "memory:load",
"description": "Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context",
"arguments": "[--tool gemini|qwen] \\\"task context description\\\"",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/load.md"
},
{
"name": "memory:skill-memory",
"description": "4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)",
"arguments": "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/skill-memory.md"
},
{
"name": "memory:tech-research",
"description": "3-phase orchestrator: extract tech stack from session/name → delegate to agent for Exa research and module generation → generate SKILL.md index (skips phase 2 if exists)",
"arguments": "[session-id | tech-stack-name] [--regenerate] [--tool <gemini|qwen>]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/tech-research.md"
},
{
"name": "memory:update-full",
"description": "Update all CLAUDE.md files using layer-based execution (Layer 3→1) with batched agents (4 modules/agent) and gemini→qwen→codex fallback, <20 modules uses direct parallel",
"arguments": "[--tool gemini|qwen|codex] [--path <directory>]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/update-full.md"
},
{
"name": "memory:update-related",
"description": "Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution",
"arguments": "[--tool gemini|qwen|codex]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/update-related.md"
},
{
"name": "memory:workflow-skill-memory",
"description": "Process WFS-* archived sessions using universal-executor agents with Gemini analysis to generate workflow-progress SKILL package (sessions-timeline, lessons, conflicts)",
"arguments": "session <session-id> | all",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/workflow-skill-memory.md"
},
{
"name": "task:breakdown",
"description": "Decompose complex task into subtasks with dependency mapping, creates child task JSONs with parent references and execution order",
"arguments": "task-id",
"category": "task",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "task/breakdown.md"
},
{
"name": "task:create",
"description": "Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis",
"arguments": "\\\"task title\\\"",
"category": "task",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "task/create.md"
},
{
"name": "task:execute",
"description": "Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking",
"arguments": "task-id",
"category": "task",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "task/execute.md"
},
{
"name": "task:replan",
"description": "Update task JSON with new requirements or batch-update multiple tasks from verification report, tracks changes in task-changes.json",
"arguments": "task-id [\\\"text\\\"|file.md] | --batch [verification-report.md]",
"category": "task",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "task/replan.md"
},
{
"name": "version",
"description": "Display Claude Code version information and check for updates",
"arguments": "",
"category": "general",
"subcategory": "core",
"usage_scenario": "utilities",
"difficulty": "Basic",
"file_path": "version.md"
},
{
"name": "workflow:action-plan-verify",
"description": "Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation",
"arguments": "[optional: --session session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "workflow/action-plan-verify.md"
},
{
"name": "workflow:brainstorm:api-designer",
"description": "Generate or update api-designer/analysis.md addressing guidance-specification discussion points for API design perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/api-designer.md"
},
{
"name": "workflow:brainstorm:artifacts",
"description": "Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis",
"arguments": "topic or challenge description [--count N]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/artifacts.md"
},
{
"name": "workflow:brainstorm:auto-parallel",
"description": "Parallel brainstorming automation with dynamic role selection and concurrent execution across multiple perspectives",
"arguments": "topic or challenge description\" [--count N]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/auto-parallel.md"
},
{
"name": "workflow:brainstorm:data-architect",
"description": "Generate or update data-architect/analysis.md addressing guidance-specification discussion points for data architecture perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/data-architect.md"
},
{
"name": "workflow:brainstorm:product-manager",
"description": "Generate or update product-manager/analysis.md addressing guidance-specification discussion points for product management perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/product-manager.md"
},
{
"name": "workflow:brainstorm:product-owner",
"description": "Generate or update product-owner/analysis.md addressing guidance-specification discussion points for product ownership perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/product-owner.md"
},
{
"name": "workflow:brainstorm:scrum-master",
"description": "Generate or update scrum-master/analysis.md addressing guidance-specification discussion points for Agile process perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/scrum-master.md"
},
{
"name": "workflow:brainstorm:subject-matter-expert",
"description": "Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points for domain expertise perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/subject-matter-expert.md"
},
{
"name": "workflow:brainstorm:synthesis",
"description": "Clarify and refine role analyses through intelligent Q&A and targeted updates with synthesis agent",
"arguments": "[optional: --session session-id]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "brainstorming",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/synthesis.md"
},
{
"name": "workflow:brainstorm:system-architect",
"description": "Generate or update system-architect/analysis.md addressing guidance-specification discussion points for system architecture perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/system-architect.md"
},
{
"name": "workflow:brainstorm:ui-designer",
"description": "Generate or update ui-designer/analysis.md addressing guidance-specification discussion points for UI design perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/ui-designer.md"
},
{
"name": "workflow:brainstorm:ux-expert",
"description": "Generate or update ux-expert/analysis.md addressing guidance-specification discussion points for UX perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/ux-expert.md"
},
{
"name": "workflow:execute",
"description": "Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking",
"arguments": "[--resume-session=\\\"session-id\\\"]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/execute.md"
},
{
"name": "workflow:plan",
"description": "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution",
"arguments": "[--agent] [--cli-execute] \\\"text description\\\"|file.md",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/plan.md"
},
{
"name": "workflow:resume",
"description": "Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection",
"arguments": "session-id for workflow session to resume",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "workflow/resume.md"
},
{
"name": "workflow:review",
"description": "Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini",
"arguments": "[--type=security|architecture|action-items|quality] [optional: session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/review.md"
},
{
"name": "workflow:session:complete",
"description": "Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag",
"arguments": "# Complete current active session",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/complete.md"
},
{
"name": "workflow:session:list",
"description": "List all workflow sessions with status filtering, shows session metadata and progress information",
"arguments": "# Show all sessions with status",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Basic",
"file_path": "workflow/session/list.md"
},
{
"name": "workflow:session:resume",
"description": "Resume the most recently paused workflow session with automatic session discovery and status update",
"arguments": "# Resume most recent paused session",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/resume.md"
},
{
"name": "workflow:session:start",
"description": "Discover existing sessions or start new workflow session with intelligent session management and conflict detection",
"arguments": "[--auto|--new] [optional: task description for new session]",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/start.md"
},
{
"name": "workflow:status",
"description": "Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view",
"arguments": "[optional: task-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "monitoring",
"difficulty": "Basic",
"file_path": "workflow/status.md"
},
{
"name": "workflow:tdd-plan",
"description": "TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, and cycle tracking",
"arguments": "[--agent] \\\"feature description\\\"|file.md",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/tdd-plan.md"
},
{
"name": "workflow:tdd-verify",
"description": "Verify TDD workflow compliance against Red-Green-Refactor cycles, generate quality report with coverage analysis",
"arguments": "[optional: WFS-session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/tdd-verify.md"
},
{
"name": "workflow:test-cycle-execute",
"description": "Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached",
"arguments": "[--resume-session=\\\"session-id\\\"] [--max-iterations=N]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/test-cycle-execute.md"
},
{
"name": "workflow:test-fix-gen",
"description": "Create test-fix workflow session from session ID, description, or file path with test strategy generation and task planning",
"arguments": "[--use-codex] [--cli-execute] (source-session-id | \\\"feature description\\\" | /path/to/file.md)",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/test-fix-gen.md"
},
{
"name": "workflow:test-gen",
"description": "Create independent test-fix workflow session from completed implementation session, analyzes code to generate test tasks",
"arguments": "[--use-codex] [--cli-execute] source-session-id",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/test-gen.md"
},
{
"name": "workflow:tools:conflict-resolution",
"description": "Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis with Gemini/Qwen",
"arguments": "--session WFS-session-id --context path/to/context-package.json",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "brainstorming",
"difficulty": "Advanced",
"file_path": "workflow/tools/conflict-resolution.md"
},
{
"name": "workflow:tools:context-gather",
"description": "Intelligently collect project context using context-search-agent based on task description, packages into standardized JSON",
"arguments": "--session WFS-session-id \\\"task description\\\"",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/tools/context-gather.md"
},
{
"name": "workflow:tools:task-generate-agent",
"description": "Autonomous task generation using action-planning-agent with discovery and output phases for workflow planning",
"arguments": "--session WFS-session-id [--cli-execute]",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate-agent.md"
},
{
"name": "workflow:tools:task-generate-tdd",
"description": "Generate TDD task chains with Red-Green-Refactor dependencies, test-first structure, and cycle validation",
"arguments": "--session WFS-session-id [--agent]",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate-tdd.md"
},
{
"name": "workflow:tools:task-generate",
"description": "",
"arguments": "--session WFS-auth",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate.md"
},
{
"name": "workflow:tools:tdd-coverage-analysis",
"description": "Analyze test coverage and TDD cycle execution with Red-Green-Refactor compliance verification",
"arguments": "--session WFS-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "testing",
"difficulty": "Advanced",
"file_path": "workflow/tools/tdd-coverage-analysis.md"
},
{
"name": "workflow:tools:test-concept-enhanced",
"description": "Analyze test requirements and generate test generation strategy using Gemini with test-context package",
"arguments": "--session WFS-test-session-id --context path/to/test-context-package.json",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "testing",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-concept-enhanced.md"
},
{
"name": "workflow:tools:test-context-gather",
"description": "Collect test coverage context using test-context-search-agent and package into standardized test-context JSON",
"arguments": "--session WFS-test-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-context-gather.md"
},
{
"name": "workflow:tools:test-task-generate",
"description": "Generate test-fix task JSON with iterative test-fix-retest cycle specification using Gemini/Qwen/Codex",
"arguments": "[--use-codex] [--cli-execute] --session WFS-test-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-task-generate.md"
},
{
"name": "workflow:ui-design:animation-extract",
"description": "Extract animation and transition patterns from URLs, CSS, or interactive questioning for design system documentation",
"arguments": "[--base-path <path>] [--session <id>] [--urls \"<list>\"] [--mode <auto|interactive>] [--focus \"<types>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/animation-extract.md"
},
{
"name": "workflow:ui-design:batch-generate",
"description": "Prompt-driven batch UI generation using target-style-centric parallel execution with design token application",
"arguments": "[--targets \"<list>\"] [--target-type \"page|component\"] [--device-type \"desktop|mobile|tablet|responsive\"] [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/batch-generate.md"
},
{
"name": "workflow:ui-design:capture",
"description": "Batch screenshot capture for UI design workflows using MCP puppeteer or local fallback with URL mapping",
"arguments": "--url-map \"target:url,...\" [--base-path path] [--session id]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/capture.md"
},
{
"name": "workflow:ui-design:explore-auto",
"description": "Exploratory UI design workflow with style-centric batch generation, creates design variants from prompts/images with parallel execution",
"arguments": "[--prompt \"<desc>\"] [--images \"<glob>\"] [--targets \"<list>\"] [--target-type \"page|component\"] [--session <id>] [--style-variants <count>] [--layout-variants <count>] [--batch-plan]\"",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/explore-auto.md"
},
{
"name": "workflow:ui-design:explore-layers",
"description": "Interactive deep UI capture with depth-controlled layer exploration using MCP puppeteer",
"arguments": "--url <url> --depth <1-5> [--session id] [--base-path path]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/explore-layers.md"
},
{
"name": "workflow:ui-design:generate",
"description": "Assemble UI prototypes by combining layout templates with design tokens, pure assembler without new content generation",
"arguments": "[--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/generate.md"
},
{
"name": "workflow:ui-design:imitate-auto",
"description": "High-speed multi-page UI replication with batch screenshot capture and design token extraction",
"arguments": "--url-map \"<map>\" [--capture-mode <batch|deep>] [--depth <1-5>] [--session <id>] [--prompt \"<desc>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/imitate-auto.md"
},
{
"name": "workflow:ui-design:layout-extract",
"description": "Extract structural layout information from reference images, URLs, or text prompts using Claude analysis",
"arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--targets \"<list>\"] [--mode <imitate|explore>] [--variants <count>] [--device-type <desktop|mobile|tablet|responsive>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/layout-extract.md"
},
{
"name": "workflow:ui-design:style-extract",
"description": "Extract design style from reference images or text prompts using Claude analysis with variant generation",
"arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--mode <imitate|explore>] [--variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/style-extract.md"
},
{
"name": "workflow:ui-design:update",
"description": "Update brainstorming artifacts with finalized design system references from selected prototypes",
"arguments": "--session <session_id> [--selected-prototypes \"<list>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/update.md"
}
]

View File

@@ -0,0 +1,722 @@
{
"cli": {
"core": [
{
"name": "cli:analyze",
"description": "Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/analyze.md"
},
{
"name": "cli:chat",
"description": "Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/chat.md"
},
{
"name": "cli:cli-init",
"description": "Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection",
"arguments": "[--tool gemini|qwen|all] [--output path] [--preview]",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/cli-init.md"
},
{
"name": "cli:codex-execute",
"description": "Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity",
"arguments": "[--verify-git] task description or task-id",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/codex-execute.md"
},
{
"name": "cli:discuss-plan",
"description": "Multi-round collaborative planning using Gemini, Codex, and Claude synthesis with iterative discussion cycles (read-only, no code changes)",
"arguments": "[--topic '...'] [--task-id '...'] [--rounds N]",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/discuss-plan.md"
},
{
"name": "cli:execute",
"description": "Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/execute.md"
}
],
"mode": [
{
"name": "cli:mode:bug-diagnosis",
"description": "Read-only bug root cause analysis using Gemini/Qwen/Codex with systematic diagnosis template for fix suggestions",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] bug description",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "analysis",
"difficulty": "Intermediate",
"file_path": "cli/mode/bug-diagnosis.md"
},
{
"name": "cli:mode:code-analysis",
"description": "Read-only execution path tracing using Gemini/Qwen/Codex with specialized analysis template for call flow and optimization",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] analysis target",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "cli/mode/code-analysis.md"
},
{
"name": "cli:mode:plan",
"description": "Read-only architecture planning using Gemini/Qwen/Codex with strategic planning template for modification plans and impact analysis",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] topic",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "cli/mode/plan.md"
}
]
},
"general": {
"core": [
{
"name": "enhance-prompt",
"description": "Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection",
"arguments": "user input to enhance",
"category": "general",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "enhance-prompt.md"
},
{
"name": "version",
"description": "Display Claude Code version information and check for updates",
"arguments": "",
"category": "general",
"subcategory": "core",
"usage_scenario": "utilities",
"difficulty": "Basic",
"file_path": "version.md"
}
]
},
"memory": {
"core": [
{
"name": "memory:docs",
"description": "Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs",
"arguments": "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "memory/docs.md"
},
{
"name": "memory:load-skill-memory",
"description": "Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords",
"arguments": "[skill_name] \\\"task intent description\\\"",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/load-skill-memory.md"
},
{
"name": "memory:load",
"description": "Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context",
"arguments": "[--tool gemini|qwen] \\\"task context description\\\"",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/load.md"
},
{
"name": "memory:skill-memory",
"description": "4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)",
"arguments": "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/skill-memory.md"
},
{
"name": "memory:tech-research",
"description": "3-phase orchestrator: extract tech stack from session/name → delegate to agent for Exa research and module generation → generate SKILL.md index (skips phase 2 if exists)",
"arguments": "[session-id | tech-stack-name] [--regenerate] [--tool <gemini|qwen>]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/tech-research.md"
},
{
"name": "memory:update-full",
"description": "Update all CLAUDE.md files using layer-based execution (Layer 3→1) with batched agents (4 modules/agent) and gemini→qwen→codex fallback, <20 modules uses direct parallel",
"arguments": "[--tool gemini|qwen|codex] [--path <directory>]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/update-full.md"
},
{
"name": "memory:update-related",
"description": "Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution",
"arguments": "[--tool gemini|qwen|codex]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/update-related.md"
},
{
"name": "memory:workflow-skill-memory",
"description": "Process WFS-* archived sessions using universal-executor agents with Gemini analysis to generate workflow-progress SKILL package (sessions-timeline, lessons, conflicts)",
"arguments": "session <session-id> | all",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/workflow-skill-memory.md"
}
]
},
"task": {
"core": [
{
"name": "task:breakdown",
"description": "Decompose complex task into subtasks with dependency mapping, creates child task JSONs with parent references and execution order",
"arguments": "task-id",
"category": "task",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "task/breakdown.md"
},
{
"name": "task:create",
"description": "Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis",
"arguments": "\\\"task title\\\"",
"category": "task",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "task/create.md"
},
{
"name": "task:execute",
"description": "Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking",
"arguments": "task-id",
"category": "task",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "task/execute.md"
},
{
"name": "task:replan",
"description": "Update task JSON with new requirements or batch-update multiple tasks from verification report, tracks changes in task-changes.json",
"arguments": "task-id [\\\"text\\\"|file.md] | --batch [verification-report.md]",
"category": "task",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "task/replan.md"
}
]
},
"workflow": {
"core": [
{
"name": "workflow:action-plan-verify",
"description": "Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation",
"arguments": "[optional: --session session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "workflow/action-plan-verify.md"
},
{
"name": "workflow:execute",
"description": "Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking",
"arguments": "[--resume-session=\\\"session-id\\\"]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/execute.md"
},
{
"name": "workflow:plan",
"description": "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution",
"arguments": "[--agent] [--cli-execute] \\\"text description\\\"|file.md",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/plan.md"
},
{
"name": "workflow:resume",
"description": "Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection",
"arguments": "session-id for workflow session to resume",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "workflow/resume.md"
},
{
"name": "workflow:review",
"description": "Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini",
"arguments": "[--type=security|architecture|action-items|quality] [optional: session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/review.md"
},
{
"name": "workflow:status",
"description": "Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view",
"arguments": "[optional: task-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "monitoring",
"difficulty": "Basic",
"file_path": "workflow/status.md"
},
{
"name": "workflow:tdd-plan",
"description": "TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, and cycle tracking",
"arguments": "[--agent] \\\"feature description\\\"|file.md",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/tdd-plan.md"
},
{
"name": "workflow:tdd-verify",
"description": "Verify TDD workflow compliance against Red-Green-Refactor cycles, generate quality report with coverage analysis",
"arguments": "[optional: WFS-session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/tdd-verify.md"
},
{
"name": "workflow:test-cycle-execute",
"description": "Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached",
"arguments": "[--resume-session=\\\"session-id\\\"] [--max-iterations=N]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/test-cycle-execute.md"
},
{
"name": "workflow:test-fix-gen",
"description": "Create test-fix workflow session from session ID, description, or file path with test strategy generation and task planning",
"arguments": "[--use-codex] [--cli-execute] (source-session-id | \\\"feature description\\\" | /path/to/file.md)",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/test-fix-gen.md"
},
{
"name": "workflow:test-gen",
"description": "Create independent test-fix workflow session from completed implementation session, analyzes code to generate test tasks",
"arguments": "[--use-codex] [--cli-execute] source-session-id",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/test-gen.md"
}
],
"brainstorm": [
{
"name": "workflow:brainstorm:api-designer",
"description": "Generate or update api-designer/analysis.md addressing guidance-specification discussion points for API design perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/api-designer.md"
},
{
"name": "workflow:brainstorm:artifacts",
"description": "Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis",
"arguments": "topic or challenge description [--count N]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/artifacts.md"
},
{
"name": "workflow:brainstorm:auto-parallel",
"description": "Parallel brainstorming automation with dynamic role selection and concurrent execution across multiple perspectives",
"arguments": "topic or challenge description\" [--count N]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/auto-parallel.md"
},
{
"name": "workflow:brainstorm:data-architect",
"description": "Generate or update data-architect/analysis.md addressing guidance-specification discussion points for data architecture perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/data-architect.md"
},
{
"name": "workflow:brainstorm:product-manager",
"description": "Generate or update product-manager/analysis.md addressing guidance-specification discussion points for product management perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/product-manager.md"
},
{
"name": "workflow:brainstorm:product-owner",
"description": "Generate or update product-owner/analysis.md addressing guidance-specification discussion points for product ownership perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/product-owner.md"
},
{
"name": "workflow:brainstorm:scrum-master",
"description": "Generate or update scrum-master/analysis.md addressing guidance-specification discussion points for Agile process perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/scrum-master.md"
},
{
"name": "workflow:brainstorm:subject-matter-expert",
"description": "Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points for domain expertise perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/subject-matter-expert.md"
},
{
"name": "workflow:brainstorm:synthesis",
"description": "Clarify and refine role analyses through intelligent Q&A and targeted updates with synthesis agent",
"arguments": "[optional: --session session-id]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "brainstorming",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/synthesis.md"
},
{
"name": "workflow:brainstorm:system-architect",
"description": "Generate or update system-architect/analysis.md addressing guidance-specification discussion points for system architecture perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/system-architect.md"
},
{
"name": "workflow:brainstorm:ui-designer",
"description": "Generate or update ui-designer/analysis.md addressing guidance-specification discussion points for UI design perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/ui-designer.md"
},
{
"name": "workflow:brainstorm:ux-expert",
"description": "Generate or update ux-expert/analysis.md addressing guidance-specification discussion points for UX perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/ux-expert.md"
}
],
"session": [
{
"name": "workflow:session:complete",
"description": "Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag",
"arguments": "# Complete current active session",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/complete.md"
},
{
"name": "workflow:session:list",
"description": "List all workflow sessions with status filtering, shows session metadata and progress information",
"arguments": "# Show all sessions with status",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Basic",
"file_path": "workflow/session/list.md"
},
{
"name": "workflow:session:resume",
"description": "Resume the most recently paused workflow session with automatic session discovery and status update",
"arguments": "# Resume most recent paused session",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/resume.md"
},
{
"name": "workflow:session:start",
"description": "Discover existing sessions or start new workflow session with intelligent session management and conflict detection",
"arguments": "[--auto|--new] [optional: task description for new session]",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/start.md"
}
],
"tools": [
{
"name": "workflow:tools:conflict-resolution",
"description": "Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis with Gemini/Qwen",
"arguments": "--session WFS-session-id --context path/to/context-package.json",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "brainstorming",
"difficulty": "Advanced",
"file_path": "workflow/tools/conflict-resolution.md"
},
{
"name": "workflow:tools:context-gather",
"description": "Intelligently collect project context using context-search-agent based on task description, packages into standardized JSON",
"arguments": "--session WFS-session-id \\\"task description\\\"",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/tools/context-gather.md"
},
{
"name": "workflow:tools:task-generate-agent",
"description": "Autonomous task generation using action-planning-agent with discovery and output phases for workflow planning",
"arguments": "--session WFS-session-id [--cli-execute]",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate-agent.md"
},
{
"name": "workflow:tools:task-generate-tdd",
"description": "Generate TDD task chains with Red-Green-Refactor dependencies, test-first structure, and cycle validation",
"arguments": "--session WFS-session-id [--agent]",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate-tdd.md"
},
{
"name": "workflow:tools:task-generate",
"description": "",
"arguments": "--session WFS-auth",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate.md"
},
{
"name": "workflow:tools:tdd-coverage-analysis",
"description": "Analyze test coverage and TDD cycle execution with Red-Green-Refactor compliance verification",
"arguments": "--session WFS-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "testing",
"difficulty": "Advanced",
"file_path": "workflow/tools/tdd-coverage-analysis.md"
},
{
"name": "workflow:tools:test-concept-enhanced",
"description": "Analyze test requirements and generate test generation strategy using Gemini with test-context package",
"arguments": "--session WFS-test-session-id --context path/to/test-context-package.json",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "testing",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-concept-enhanced.md"
},
{
"name": "workflow:tools:test-context-gather",
"description": "Collect test coverage context using test-context-search-agent and package into standardized test-context JSON",
"arguments": "--session WFS-test-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-context-gather.md"
},
{
"name": "workflow:tools:test-task-generate",
"description": "Generate test-fix task JSON with iterative test-fix-retest cycle specification using Gemini/Qwen/Codex",
"arguments": "[--use-codex] [--cli-execute] --session WFS-test-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-task-generate.md"
}
],
"ui-design": [
{
"name": "workflow:ui-design:animation-extract",
"description": "Extract animation and transition patterns from URLs, CSS, or interactive questioning for design system documentation",
"arguments": "[--base-path <path>] [--session <id>] [--urls \"<list>\"] [--mode <auto|interactive>] [--focus \"<types>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/animation-extract.md"
},
{
"name": "workflow:ui-design:batch-generate",
"description": "Prompt-driven batch UI generation using target-style-centric parallel execution with design token application",
"arguments": "[--targets \"<list>\"] [--target-type \"page|component\"] [--device-type \"desktop|mobile|tablet|responsive\"] [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/batch-generate.md"
},
{
"name": "workflow:ui-design:capture",
"description": "Batch screenshot capture for UI design workflows using MCP puppeteer or local fallback with URL mapping",
"arguments": "--url-map \"target:url,...\" [--base-path path] [--session id]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/capture.md"
},
{
"name": "workflow:ui-design:explore-auto",
"description": "Exploratory UI design workflow with style-centric batch generation, creates design variants from prompts/images with parallel execution",
"arguments": "[--prompt \"<desc>\"] [--images \"<glob>\"] [--targets \"<list>\"] [--target-type \"page|component\"] [--session <id>] [--style-variants <count>] [--layout-variants <count>] [--batch-plan]\"",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/explore-auto.md"
},
{
"name": "workflow:ui-design:explore-layers",
"description": "Interactive deep UI capture with depth-controlled layer exploration using MCP puppeteer",
"arguments": "--url <url> --depth <1-5> [--session id] [--base-path path]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/explore-layers.md"
},
{
"name": "workflow:ui-design:generate",
"description": "Assemble UI prototypes by combining layout templates with design tokens, pure assembler without new content generation",
"arguments": "[--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/generate.md"
},
{
"name": "workflow:ui-design:imitate-auto",
"description": "High-speed multi-page UI replication with batch screenshot capture and design token extraction",
"arguments": "--url-map \"<map>\" [--capture-mode <batch|deep>] [--depth <1-5>] [--session <id>] [--prompt \"<desc>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/imitate-auto.md"
},
{
"name": "workflow:ui-design:layout-extract",
"description": "Extract structural layout information from reference images, URLs, or text prompts using Claude analysis",
"arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--targets \"<list>\"] [--mode <imitate|explore>] [--variants <count>] [--device-type <desktop|mobile|tablet|responsive>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/layout-extract.md"
},
{
"name": "workflow:ui-design:style-extract",
"description": "Extract design style from reference images or text prompts using Claude analysis with variant generation",
"arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--mode <imitate|explore>] [--variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/style-extract.md"
},
{
"name": "workflow:ui-design:update",
"description": "Update brainstorming artifacts with finalized design system references from selected prototypes",
"arguments": "--session <session_id> [--selected-prototypes \"<list>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/update.md"
}
]
}
}

View File

@@ -0,0 +1,712 @@
{
"documentation": [
{
"name": "cli:analyze",
"description": "Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/analyze.md"
},
{
"name": "cli:chat",
"description": "Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/chat.md"
},
{
"name": "cli:cli-init",
"description": "Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection",
"arguments": "[--tool gemini|qwen|all] [--output path] [--preview]",
"category": "cli",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "cli/cli-init.md"
},
{
"name": "memory:load-skill-memory",
"description": "Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords",
"arguments": "[skill_name] \\\"task intent description\\\"",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/load-skill-memory.md"
},
{
"name": "memory:skill-memory",
"description": "4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)",
"arguments": "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/skill-memory.md"
},
{
"name": "memory:tech-research",
"description": "3-phase orchestrator: extract tech stack from session/name → delegate to agent for Exa research and module generation → generate SKILL.md index (skips phase 2 if exists)",
"arguments": "[session-id | tech-stack-name] [--regenerate] [--tool <gemini|qwen>]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/tech-research.md"
},
{
"name": "memory:workflow-skill-memory",
"description": "Process WFS-* archived sessions using universal-executor agents with Gemini analysis to generate workflow-progress SKILL package (sessions-timeline, lessons, conflicts)",
"arguments": "session <session-id> | all",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/workflow-skill-memory.md"
},
{
"name": "task:replan",
"description": "Update task JSON with new requirements or batch-update multiple tasks from verification report, tracks changes in task-changes.json",
"arguments": "task-id [\\\"text\\\"|file.md] | --batch [verification-report.md]",
"category": "task",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "task/replan.md"
},
{
"name": "workflow:ui-design:animation-extract",
"description": "Extract animation and transition patterns from URLs, CSS, or interactive questioning for design system documentation",
"arguments": "[--base-path <path>] [--session <id>] [--urls \"<list>\"] [--mode <auto|interactive>] [--focus \"<types>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/animation-extract.md"
},
{
"name": "workflow:ui-design:imitate-auto",
"description": "High-speed multi-page UI replication with batch screenshot capture and design token extraction",
"arguments": "--url-map \"<map>\" [--capture-mode <batch|deep>] [--depth <1-5>] [--session <id>] [--prompt \"<desc>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/imitate-auto.md"
},
{
"name": "workflow:ui-design:style-extract",
"description": "Extract design style from reference images or text prompts using Claude analysis with variant generation",
"arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--mode <imitate|explore>] [--variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "documentation",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/style-extract.md"
}
],
"session-management": [
{
"name": "cli:codex-execute",
"description": "Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity",
"arguments": "[--verify-git] task description or task-id",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/codex-execute.md"
},
{
"name": "cli:discuss-plan",
"description": "Multi-round collaborative planning using Gemini, Codex, and Claude synthesis with iterative discussion cycles (read-only, no code changes)",
"arguments": "[--topic '...'] [--task-id '...'] [--rounds N]",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/discuss-plan.md"
},
{
"name": "cli:execute",
"description": "Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/execute.md"
},
{
"name": "enhance-prompt",
"description": "Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection",
"arguments": "user input to enhance",
"category": "general",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "enhance-prompt.md"
},
{
"name": "workflow:brainstorm:api-designer",
"description": "Generate or update api-designer/analysis.md addressing guidance-specification discussion points for API design perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/api-designer.md"
},
{
"name": "workflow:brainstorm:artifacts",
"description": "Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis",
"arguments": "topic or challenge description [--count N]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/artifacts.md"
},
{
"name": "workflow:brainstorm:auto-parallel",
"description": "Parallel brainstorming automation with dynamic role selection and concurrent execution across multiple perspectives",
"arguments": "topic or challenge description\" [--count N]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/auto-parallel.md"
},
{
"name": "workflow:brainstorm:system-architect",
"description": "Generate or update system-architect/analysis.md addressing guidance-specification discussion points for system architecture perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/system-architect.md"
},
{
"name": "workflow:execute",
"description": "Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking",
"arguments": "[--resume-session=\\\"session-id\\\"]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/execute.md"
},
{
"name": "workflow:plan",
"description": "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution",
"arguments": "[--agent] [--cli-execute] \\\"text description\\\"|file.md",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/plan.md"
},
{
"name": "workflow:session:complete",
"description": "Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag",
"arguments": "# Complete current active session",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/complete.md"
},
{
"name": "workflow:session:list",
"description": "List all workflow sessions with status filtering, shows session metadata and progress information",
"arguments": "# Show all sessions with status",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Basic",
"file_path": "workflow/session/list.md"
},
{
"name": "workflow:session:resume",
"description": "Resume the most recently paused workflow session with automatic session discovery and status update",
"arguments": "# Resume most recent paused session",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/resume.md"
},
{
"name": "workflow:session:start",
"description": "Discover existing sessions or start new workflow session with intelligent session management and conflict detection",
"arguments": "[--auto|--new] [optional: task description for new session]",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/start.md"
},
{
"name": "workflow:tdd-plan",
"description": "TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, and cycle tracking",
"arguments": "[--agent] \\\"feature description\\\"|file.md",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/tdd-plan.md"
},
{
"name": "workflow:tdd-verify",
"description": "Verify TDD workflow compliance against Red-Green-Refactor cycles, generate quality report with coverage analysis",
"arguments": "[optional: WFS-session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/tdd-verify.md"
},
{
"name": "workflow:test-cycle-execute",
"description": "Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached",
"arguments": "[--resume-session=\\\"session-id\\\"] [--max-iterations=N]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/test-cycle-execute.md"
},
{
"name": "workflow:tools:test-task-generate",
"description": "Generate test-fix task JSON with iterative test-fix-retest cycle specification using Gemini/Qwen/Codex",
"arguments": "[--use-codex] [--cli-execute] --session WFS-test-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "session-management",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-task-generate.md"
}
],
"analysis": [
{
"name": "cli:mode:bug-diagnosis",
"description": "Read-only bug root cause analysis using Gemini/Qwen/Codex with systematic diagnosis template for fix suggestions",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] bug description",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "analysis",
"difficulty": "Intermediate",
"file_path": "cli/mode/bug-diagnosis.md"
}
],
"implementation": [
{
"name": "cli:mode:code-analysis",
"description": "Read-only execution path tracing using Gemini/Qwen/Codex with specialized analysis template for call flow and optimization",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] analysis target",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "cli/mode/code-analysis.md"
},
{
"name": "memory:load",
"description": "Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context",
"arguments": "[--tool gemini|qwen] \\\"task context description\\\"",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/load.md"
},
{
"name": "memory:update-full",
"description": "Update all CLAUDE.md files using layer-based execution (Layer 3→1) with batched agents (4 modules/agent) and gemini→qwen→codex fallback, <20 modules uses direct parallel",
"arguments": "[--tool gemini|qwen|codex] [--path <directory>]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/update-full.md"
},
{
"name": "memory:update-related",
"description": "Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution",
"arguments": "[--tool gemini|qwen|codex]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/update-related.md"
},
{
"name": "task:execute",
"description": "Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking",
"arguments": "task-id",
"category": "task",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "task/execute.md"
},
{
"name": "workflow:brainstorm:data-architect",
"description": "Generate or update data-architect/analysis.md addressing guidance-specification discussion points for data architecture perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/data-architect.md"
},
{
"name": "workflow:brainstorm:product-manager",
"description": "Generate or update product-manager/analysis.md addressing guidance-specification discussion points for product management perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/product-manager.md"
},
{
"name": "workflow:brainstorm:product-owner",
"description": "Generate or update product-owner/analysis.md addressing guidance-specification discussion points for product ownership perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/product-owner.md"
},
{
"name": "workflow:brainstorm:subject-matter-expert",
"description": "Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points for domain expertise perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/subject-matter-expert.md"
},
{
"name": "workflow:brainstorm:ux-expert",
"description": "Generate or update ux-expert/analysis.md addressing guidance-specification discussion points for UX perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/ux-expert.md"
},
{
"name": "workflow:resume",
"description": "Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection",
"arguments": "session-id for workflow session to resume",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "workflow/resume.md"
},
{
"name": "workflow:tools:context-gather",
"description": "Intelligently collect project context using context-search-agent based on task description, packages into standardized JSON",
"arguments": "--session WFS-session-id \\\"task description\\\"",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/tools/context-gather.md"
},
{
"name": "workflow:tools:test-context-gather",
"description": "Collect test coverage context using test-context-search-agent and package into standardized test-context JSON",
"arguments": "--session WFS-test-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "implementation",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-context-gather.md"
}
],
"planning": [
{
"name": "cli:mode:plan",
"description": "Read-only architecture planning using Gemini/Qwen/Codex with strategic planning template for modification plans and impact analysis",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] topic",
"category": "cli",
"subcategory": "mode",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "cli/mode/plan.md"
},
{
"name": "memory:docs",
"description": "Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs",
"arguments": "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "memory/docs.md"
},
{
"name": "task:breakdown",
"description": "Decompose complex task into subtasks with dependency mapping, creates child task JSONs with parent references and execution order",
"arguments": "task-id",
"category": "task",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "task/breakdown.md"
},
{
"name": "workflow:action-plan-verify",
"description": "Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation",
"arguments": "[optional: --session session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "workflow/action-plan-verify.md"
},
{
"name": "workflow:brainstorm:scrum-master",
"description": "Generate or update scrum-master/analysis.md addressing guidance-specification discussion points for Agile process perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/scrum-master.md"
},
{
"name": "workflow:brainstorm:ui-designer",
"description": "Generate or update ui-designer/analysis.md addressing guidance-specification discussion points for UI design perspective",
"arguments": "optional topic - uses existing framework if available",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/ui-designer.md"
},
{
"name": "workflow:tools:task-generate-agent",
"description": "Autonomous task generation using action-planning-agent with discovery and output phases for workflow planning",
"arguments": "--session WFS-session-id [--cli-execute]",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate-agent.md"
},
{
"name": "workflow:tools:task-generate-tdd",
"description": "Generate TDD task chains with Red-Green-Refactor dependencies, test-first structure, and cycle validation",
"arguments": "--session WFS-session-id [--agent]",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate-tdd.md"
},
{
"name": "workflow:tools:task-generate",
"description": "",
"arguments": "--session WFS-auth",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "planning",
"difficulty": "Advanced",
"file_path": "workflow/tools/task-generate.md"
}
],
"testing": [
{
"name": "task:create",
"description": "Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis",
"arguments": "\\\"task title\\\"",
"category": "task",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "task/create.md"
},
{
"name": "workflow:review",
"description": "Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini",
"arguments": "[--type=security|architecture|action-items|quality] [optional: session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/review.md"
},
{
"name": "workflow:test-fix-gen",
"description": "Create test-fix workflow session from session ID, description, or file path with test strategy generation and task planning",
"arguments": "[--use-codex] [--cli-execute] (source-session-id | \\\"feature description\\\" | /path/to/file.md)",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/test-fix-gen.md"
},
{
"name": "workflow:test-gen",
"description": "Create independent test-fix workflow session from completed implementation session, analyzes code to generate test tasks",
"arguments": "[--use-codex] [--cli-execute] source-session-id",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "workflow/test-gen.md"
},
{
"name": "workflow:tools:tdd-coverage-analysis",
"description": "Analyze test coverage and TDD cycle execution with Red-Green-Refactor compliance verification",
"arguments": "--session WFS-session-id",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "testing",
"difficulty": "Advanced",
"file_path": "workflow/tools/tdd-coverage-analysis.md"
},
{
"name": "workflow:tools:test-concept-enhanced",
"description": "Analyze test requirements and generate test generation strategy using Gemini with test-context package",
"arguments": "--session WFS-test-session-id --context path/to/test-context-package.json",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "testing",
"difficulty": "Advanced",
"file_path": "workflow/tools/test-concept-enhanced.md"
}
],
"utilities": [
{
"name": "version",
"description": "Display Claude Code version information and check for updates",
"arguments": "",
"category": "general",
"subcategory": "core",
"usage_scenario": "utilities",
"difficulty": "Basic",
"file_path": "version.md"
}
],
"brainstorming": [
{
"name": "workflow:brainstorm:synthesis",
"description": "Clarify and refine role analyses through intelligent Q&A and targeted updates with synthesis agent",
"arguments": "[optional: --session session-id]",
"category": "workflow",
"subcategory": "brainstorm",
"usage_scenario": "brainstorming",
"difficulty": "Advanced",
"file_path": "workflow/brainstorm/synthesis.md"
},
{
"name": "workflow:tools:conflict-resolution",
"description": "Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis with Gemini/Qwen",
"arguments": "--session WFS-session-id --context path/to/context-package.json",
"category": "workflow",
"subcategory": "tools",
"usage_scenario": "brainstorming",
"difficulty": "Advanced",
"file_path": "workflow/tools/conflict-resolution.md"
}
],
"monitoring": [
{
"name": "workflow:status",
"description": "Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view",
"arguments": "[optional: task-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "monitoring",
"difficulty": "Basic",
"file_path": "workflow/status.md"
}
],
"ui-design": [
{
"name": "workflow:ui-design:batch-generate",
"description": "Prompt-driven batch UI generation using target-style-centric parallel execution with design token application",
"arguments": "[--targets \"<list>\"] [--target-type \"page|component\"] [--device-type \"desktop|mobile|tablet|responsive\"] [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/batch-generate.md"
},
{
"name": "workflow:ui-design:capture",
"description": "Batch screenshot capture for UI design workflows using MCP puppeteer or local fallback with URL mapping",
"arguments": "--url-map \"target:url,...\" [--base-path path] [--session id]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/capture.md"
},
{
"name": "workflow:ui-design:explore-auto",
"description": "Exploratory UI design workflow with style-centric batch generation, creates design variants from prompts/images with parallel execution",
"arguments": "[--prompt \"<desc>\"] [--images \"<glob>\"] [--targets \"<list>\"] [--target-type \"page|component\"] [--session <id>] [--style-variants <count>] [--layout-variants <count>] [--batch-plan]\"",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/explore-auto.md"
},
{
"name": "workflow:ui-design:explore-layers",
"description": "Interactive deep UI capture with depth-controlled layer exploration using MCP puppeteer",
"arguments": "--url <url> --depth <1-5> [--session id] [--base-path path]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/explore-layers.md"
},
{
"name": "workflow:ui-design:generate",
"description": "Assemble UI prototypes by combining layout templates with design tokens, pure assembler without new content generation",
"arguments": "[--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/generate.md"
},
{
"name": "workflow:ui-design:layout-extract",
"description": "Extract structural layout information from reference images, URLs, or text prompts using Claude analysis",
"arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--targets \"<list>\"] [--mode <imitate|explore>] [--variants <count>] [--device-type <desktop|mobile|tablet|responsive>]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/layout-extract.md"
},
{
"name": "workflow:ui-design:update",
"description": "Update brainstorming artifacts with finalized design system references from selected prototypes",
"arguments": "--session <session_id> [--selected-prototypes \"<list>\"]",
"category": "workflow",
"subcategory": "ui-design",
"usage_scenario": "ui-design",
"difficulty": "Advanced",
"file_path": "workflow/ui-design/update.md"
}
]
}

View File

@@ -0,0 +1,616 @@
{
"cli:analyze": {
"related_commands": [
"cli:chat",
"cli:mode:code-analysis"
],
"next_steps": [],
"prerequisites": []
},
"cli:chat": {
"related_commands": [
"cli:analyze",
"memory:load"
],
"next_steps": [],
"prerequisites": []
},
"cli:cli-init": {
"related_commands": [],
"next_steps": [],
"prerequisites": []
},
"cli:codex-execute": {
"related_commands": [
"cli:execute",
"task:execute"
],
"next_steps": [],
"prerequisites": []
},
"cli:discuss-plan": {
"related_commands": [],
"next_steps": [],
"prerequisites": []
},
"cli:execute": {
"related_commands": [
"cli:codex-execute",
"task:execute"
],
"next_steps": [
"workflow:status"
],
"prerequisites": []
},
"cli:mode:bug-diagnosis": {
"related_commands": [
"cli:mode:code-analysis",
"cli:execute"
],
"next_steps": [],
"prerequisites": []
},
"cli:mode:code-analysis": {
"related_commands": [
"cli:analyze",
"cli:mode:bug-diagnosis"
],
"next_steps": [],
"prerequisites": []
},
"cli:mode:plan": {
"related_commands": [
"workflow:plan",
"cli:analyze"
],
"next_steps": [],
"prerequisites": []
},
"enhance-prompt": {
"related_commands": [
"workflow:plan",
"cli:execute"
],
"next_steps": [],
"prerequisites": []
},
"memory:docs": {
"related_commands": [
"memory:update-full",
"memory:update-related"
],
"next_steps": [],
"prerequisites": []
},
"memory:load-skill-memory": {
"related_commands": [
"memory:load"
],
"next_steps": [],
"prerequisites": [
"memory:skill-memory"
]
},
"memory:load": {
"related_commands": [
"memory:skill-memory",
"memory:load-skill-memory"
],
"next_steps": [
"workflow:plan",
"cli:execute"
],
"prerequisites": []
},
"memory:skill-memory": {
"related_commands": [
"memory:docs",
"memory:update-full"
],
"next_steps": [
"memory:load-skill-memory"
],
"prerequisites": []
},
"memory:tech-research": {
"related_commands": [],
"next_steps": [
"memory:load-skill-memory"
],
"prerequisites": []
},
"memory:update-full": {
"related_commands": [
"memory:update-related"
],
"next_steps": [],
"prerequisites": [
"memory:docs"
]
},
"memory:update-related": {
"related_commands": [
"memory:update-full",
"memory:docs"
],
"next_steps": [],
"prerequisites": []
},
"memory:workflow-skill-memory": {
"related_commands": [
"memory:skill-memory",
"workflow:session:list"
],
"next_steps": [],
"prerequisites": []
},
"task:breakdown": {
"related_commands": [],
"next_steps": [
"task:execute"
],
"prerequisites": [
"task:create"
]
},
"task:create": {
"related_commands": [
"task:breakdown",
"workflow:plan"
],
"next_steps": [
"task:execute"
],
"prerequisites": []
},
"task:execute": {
"related_commands": [
"workflow:execute",
"workflow:status",
"task:create"
],
"next_steps": [],
"prerequisites": []
},
"task:replan": {
"related_commands": [
"task:execute",
"workflow:action-plan-verify"
],
"next_steps": [],
"prerequisites": []
},
"version": {
"related_commands": [],
"next_steps": [],
"prerequisites": []
},
"workflow:action-plan-verify": {
"related_commands": [
"workflow:status"
],
"next_steps": [
"workflow:execute"
],
"prerequisites": [
"workflow:plan"
]
},
"workflow:brainstorm:api-designer": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:artifacts": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [
"workflow:plan"
],
"prerequisites": []
},
"workflow:brainstorm:auto-parallel": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [
"workflow:brainstorm:synthesis"
],
"prerequisites": []
},
"workflow:brainstorm:data-architect": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:product-manager": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:product-owner": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:scrum-master": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:subject-matter-expert": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:synthesis": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan",
"workflow:brainstorm:artifacts"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:system-architect": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:ui-designer": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:brainstorm:ux-expert": {
"related_commands": [
"workflow:brainstorm:synthesis",
"workflow:plan"
],
"next_steps": [],
"prerequisites": []
},
"workflow:execute": {
"related_commands": [
"workflow:status",
"task:execute",
"workflow:session:start"
],
"next_steps": [
"workflow:review",
"workflow:test-cycle-execute"
],
"prerequisites": [
"workflow:plan"
]
},
"workflow:plan": {
"related_commands": [
"workflow:status",
"workflow:tdd-plan",
"workflow:session:start"
],
"next_steps": [
"workflow:action-plan-verify",
"workflow:execute"
],
"prerequisites": []
},
"workflow:resume": {
"related_commands": [
"workflow:session:start",
"workflow:status",
"workflow:execute"
],
"next_steps": [],
"prerequisites": []
},
"workflow:review": {
"related_commands": [
"workflow:status"
],
"next_steps": [],
"prerequisites": [
"workflow:execute"
]
},
"workflow:session:complete": {
"related_commands": [
"workflow:review",
"workflow:session:list"
],
"next_steps": [],
"prerequisites": [
"workflow:execute"
]
},
"workflow:session:list": {
"related_commands": [
"workflow:session:start",
"workflow:session:resume"
],
"next_steps": [],
"prerequisites": []
},
"workflow:session:resume": {
"related_commands": [
"workflow:resume",
"workflow:status"
],
"next_steps": [],
"prerequisites": [
"workflow:session:start"
]
},
"workflow:session:start": {
"related_commands": [
"workflow:session:list",
"workflow:session:resume"
],
"next_steps": [
"workflow:plan",
"workflow:execute"
],
"prerequisites": []
},
"workflow:status": {
"related_commands": [
"workflow:execute",
"workflow:plan",
"task:execute"
],
"next_steps": [],
"prerequisites": []
},
"workflow:tdd-plan": {
"related_commands": [
"workflow:plan",
"workflow:test-cycle-execute"
],
"next_steps": [
"workflow:execute",
"workflow:tdd-verify"
],
"prerequisites": []
},
"workflow:tdd-verify": {
"related_commands": [
"workflow:test-cycle-execute",
"workflow:review"
],
"next_steps": [],
"prerequisites": [
"workflow:tdd-plan"
]
},
"workflow:test-cycle-execute": {
"related_commands": [
"workflow:tdd-verify",
"workflow:execute"
],
"next_steps": [],
"prerequisites": [
"workflow:test-gen",
"workflow:test-fix-gen"
]
},
"workflow:test-fix-gen": {
"related_commands": [],
"next_steps": [
"workflow:test-cycle-execute"
],
"prerequisites": []
},
"workflow:test-gen": {
"related_commands": [],
"next_steps": [
"workflow:test-cycle-execute"
],
"prerequisites": [
"workflow:execute"
]
},
"workflow:tools:conflict-resolution": {
"related_commands": [],
"next_steps": [
"workflow:tools:task-generate"
],
"prerequisites": [
"workflow:tools:context-gather"
]
},
"workflow:tools:context-gather": {
"related_commands": [
"memory:load",
"workflow:tools:conflict-resolution"
],
"next_steps": [],
"prerequisites": [
"workflow:plan"
]
},
"workflow:tools:task-generate-agent": {
"related_commands": [
"workflow:tools:task-generate"
],
"next_steps": [
"workflow:execute"
],
"prerequisites": [
"workflow:plan"
]
},
"workflow:tools:task-generate-tdd": {
"related_commands": [
"workflow:tools:task-generate"
],
"next_steps": [],
"prerequisites": [
"workflow:tdd-plan"
]
},
"workflow:tools:task-generate": {
"related_commands": [],
"next_steps": [
"workflow:execute"
],
"prerequisites": [
"workflow:plan"
]
},
"workflow:tools:tdd-coverage-analysis": {
"related_commands": [
"workflow:tdd-verify"
],
"next_steps": [],
"prerequisites": [
"workflow:tdd-plan"
]
},
"workflow:tools:test-concept-enhanced": {
"related_commands": [],
"next_steps": [],
"prerequisites": [
"workflow:tools:test-context-gather"
]
},
"workflow:tools:test-context-gather": {
"related_commands": [
"workflow:tools:context-gather"
],
"next_steps": [],
"prerequisites": [
"workflow:test-gen"
]
},
"workflow:tools:test-task-generate": {
"related_commands": [
"workflow:tools:task-generate"
],
"next_steps": [],
"prerequisites": [
"workflow:test-gen"
]
},
"workflow:ui-design:animation-extract": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [],
"prerequisites": []
},
"workflow:ui-design:batch-generate": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [],
"prerequisites": []
},
"workflow:ui-design:capture": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [
"workflow:ui-design:layout-extract",
"workflow:ui-design:style-extract"
],
"prerequisites": []
},
"workflow:ui-design:explore-auto": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [
"workflow:ui-design:generate",
"workflow:ui-design:update"
],
"prerequisites": []
},
"workflow:ui-design:explore-layers": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [],
"prerequisites": []
},
"workflow:ui-design:generate": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [
"workflow:ui-design:update",
"workflow:plan"
],
"prerequisites": []
},
"workflow:ui-design:imitate-auto": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [],
"prerequisites": []
},
"workflow:ui-design:layout-extract": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [
"workflow:ui-design:generate"
],
"prerequisites": []
},
"workflow:ui-design:style-extract": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [
"workflow:ui-design:generate"
],
"prerequisites": []
},
"workflow:ui-design:update": {
"related_commands": [
"workflow:plan",
"workflow:brainstorm:ui-designer"
],
"next_steps": [],
"prerequisites": []
}
}

View File

@@ -0,0 +1,142 @@
[
{
"name": "cli:codex-execute",
"description": "Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity",
"arguments": "[--verify-git] task description or task-id",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/codex-execute.md"
},
{
"name": "cli:execute",
"description": "Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection",
"arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id",
"category": "cli",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "cli/execute.md"
},
{
"name": "memory:load",
"description": "Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context",
"arguments": "[--tool gemini|qwen] \\\"task context description\\\"",
"category": "memory",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "memory/load.md"
},
{
"name": "memory:skill-memory",
"description": "4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)",
"arguments": "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]",
"category": "memory",
"subcategory": "core",
"usage_scenario": "documentation",
"difficulty": "Intermediate",
"file_path": "memory/skill-memory.md"
},
{
"name": "task:create",
"description": "Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis",
"arguments": "\\\"task title\\\"",
"category": "task",
"subcategory": "core",
"usage_scenario": "testing",
"difficulty": "Intermediate",
"file_path": "task/create.md"
},
{
"name": "task:execute",
"description": "Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking",
"arguments": "task-id",
"category": "task",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "task/execute.md"
},
{
"name": "version",
"description": "Display Claude Code version information and check for updates",
"arguments": "",
"category": "general",
"subcategory": "core",
"usage_scenario": "utilities",
"difficulty": "Basic",
"file_path": "version.md"
},
{
"name": "workflow:action-plan-verify",
"description": "Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation",
"arguments": "[optional: --session session-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "planning",
"difficulty": "Intermediate",
"file_path": "workflow/action-plan-verify.md"
},
{
"name": "workflow:execute",
"description": "Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking",
"arguments": "[--resume-session=\\\"session-id\\\"]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/execute.md"
},
{
"name": "workflow:plan",
"description": "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution",
"arguments": "[--agent] [--cli-execute] \\\"text description\\\"|file.md",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/plan.md"
},
{
"name": "workflow:resume",
"description": "Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection",
"arguments": "session-id for workflow session to resume",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "implementation",
"difficulty": "Intermediate",
"file_path": "workflow/resume.md"
},
{
"name": "workflow:session:start",
"description": "Discover existing sessions or start new workflow session with intelligent session management and conflict detection",
"arguments": "[--auto|--new] [optional: task description for new session]",
"category": "workflow",
"subcategory": "session",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/session/start.md"
},
{
"name": "workflow:status",
"description": "Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view",
"arguments": "[optional: task-id]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "monitoring",
"difficulty": "Basic",
"file_path": "workflow/status.md"
},
{
"name": "workflow:test-cycle-execute",
"description": "Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached",
"arguments": "[--resume-session=\\\"session-id\\\"] [--max-iterations=N]",
"category": "workflow",
"subcategory": "core",
"usage_scenario": "session-management",
"difficulty": "Intermediate",
"file_path": "workflow/test-cycle-execute.md"
}
]

View File

@@ -0,0 +1,411 @@
#!/usr/bin/env python3
"""
Analyze all command files and generate index files for command-guide skill.
"""
import os
import re
import json
from pathlib import Path
from collections import defaultdict
from typing import Dict, List, Any
# Base paths
COMMANDS_DIR = Path("D:/Claude_dms3/.claude/commands")
INDEX_DIR = Path("D:/Claude_dms3/.claude/skills/command-guide/index")
def parse_frontmatter(content: str) -> Dict[str, Any]:
"""Extract YAML frontmatter from markdown content."""
frontmatter = {}
if content.startswith('---'):
lines = content.split('\n')
in_frontmatter = False
for i, line in enumerate(lines[1:], 1):
if line.strip() == '---':
break
if ':' in line:
key, value = line.split(':', 1)
frontmatter[key.strip()] = value.strip().strip('"')
return frontmatter
def categorize_command(file_path: Path) -> tuple:
"""Determine category and subcategory from file path."""
parts = file_path.relative_to(COMMANDS_DIR).parts
if len(parts) == 1:
return "general", None
category = parts[0] # cli, memory, task, workflow
subcategory = parts[1].replace('.md', '') if len(parts) > 2 else None
return category, subcategory
def determine_usage_scenario(name: str, description: str, category: str) -> str:
"""Determine primary usage scenario for command."""
name_lower = name.lower()
desc_lower = description.lower()
# Planning indicators
if any(word in name_lower for word in ['plan', 'design', 'breakdown', 'brainstorm']):
return "planning"
# Implementation indicators
if any(word in name_lower for word in ['implement', 'execute', 'generate', 'create', 'write']):
return "implementation"
# Testing indicators
if any(word in name_lower for word in ['test', 'tdd', 'verify', 'coverage']):
return "testing"
# Documentation indicators
if any(word in name_lower for word in ['docs', 'documentation', 'memory']):
return "documentation"
# Session management indicators
if any(word in name_lower for word in ['session', 'resume', 'status', 'complete']):
return "session-management"
# Analysis indicators
if any(word in name_lower for word in ['analyze', 'review', 'diagnosis']):
return "analysis"
return "general"
def determine_difficulty(name: str, description: str, category: str) -> str:
"""Determine difficulty level."""
name_lower = name.lower()
# Beginner commands
beginner_keywords = ['status', 'list', 'chat', 'analyze', 'version']
if any(word in name_lower for word in beginner_keywords):
return "Beginner"
# Advanced commands
advanced_keywords = ['tdd', 'conflict', 'agent', 'auto-parallel', 'coverage', 'synthesis']
if any(word in name_lower for word in advanced_keywords):
return "Advanced"
# Intermediate by default
return "Intermediate"
def analyze_command_file(file_path: Path) -> Dict[str, Any]:
"""Analyze a single command file and extract metadata."""
with open(file_path, 'r', encoding='utf-8') as f:
content = f.read()
# Parse frontmatter
frontmatter = parse_frontmatter(content)
# Extract data
name = frontmatter.get('name', file_path.stem)
description = frontmatter.get('description', '')
argument_hint = frontmatter.get('argument-hint', '')
# Determine categorization
category, subcategory = categorize_command(file_path)
usage_scenario = determine_usage_scenario(name, description, category)
difficulty = determine_difficulty(name, description, category)
# Build relative path
rel_path = str(file_path.relative_to(COMMANDS_DIR)).replace('\\', '/')
# Build full command name from frontmatter name or construct it
# If name already contains colons (e.g., "workflow:status"), use it directly
if ':' in name:
command_name = f"/{name}"
elif category == "general":
command_name = f"/{name}"
else:
# For subcategorized commands, build the full path
if subcategory:
command_name = f"/{category}:{subcategory}:{name}"
else:
command_name = f"/{category}:{name}"
return {
"name": name,
"command": command_name,
"description": description,
"arguments": argument_hint,
"category": category,
"subcategory": subcategory,
"usage_scenario": usage_scenario,
"difficulty": difficulty,
"file_path": rel_path
}
def build_command_relationships() -> Dict[str, Any]:
"""Build command relationship mappings."""
relationships = {
# Workflow planning commands
"workflow:plan": {
"calls_internally": [
"workflow:session:start",
"workflow:tools:context-gather",
"workflow:tools:conflict-resolution",
"workflow:tools:task-generate",
"workflow:tools:task-generate-agent"
],
"next_steps": ["workflow:action-plan-verify", "workflow:status", "workflow:execute"],
"alternatives": ["workflow:tdd-plan"],
"prerequisites": []
},
"workflow:tdd-plan": {
"calls_internally": [
"workflow:session:start",
"workflow:tools:context-gather",
"workflow:tools:task-generate-tdd"
],
"next_steps": ["workflow:tdd-verify", "workflow:status", "workflow:execute"],
"alternatives": ["workflow:plan"],
"prerequisites": []
},
# Execution commands
"workflow:execute": {
"prerequisites": ["workflow:plan", "workflow:tdd-plan"],
"related": ["workflow:status", "workflow:resume"],
"next_steps": ["workflow:review", "workflow:tdd-verify"]
},
# Verification commands
"workflow:action-plan-verify": {
"prerequisites": ["workflow:plan"],
"next_steps": ["workflow:execute"],
"related": ["workflow:status"]
},
"workflow:tdd-verify": {
"prerequisites": ["workflow:execute"],
"related": ["workflow:tools:tdd-coverage-analysis"]
},
# Session management
"workflow:session:start": {
"next_steps": ["workflow:plan", "workflow:execute"],
"related": ["workflow:session:list", "workflow:session:resume"]
},
"workflow:session:resume": {
"alternatives": ["workflow:resume"],
"related": ["workflow:session:list", "workflow:status"]
},
"workflow:resume": {
"alternatives": ["workflow:session:resume"],
"related": ["workflow:status"]
},
# Task management
"task:create": {
"next_steps": ["task:execute"],
"related": ["task:breakdown"]
},
"task:breakdown": {
"next_steps": ["task:execute"],
"related": ["task:create"]
},
"task:replan": {
"prerequisites": ["workflow:plan"],
"related": ["workflow:action-plan-verify"]
},
"task:execute": {
"prerequisites": ["task:create", "task:breakdown", "workflow:plan"],
"related": ["workflow:status"]
},
# Memory/Documentation
"memory:docs": {
"calls_internally": [
"workflow:session:start",
"workflow:tools:context-gather"
],
"next_steps": ["workflow:execute"]
},
"memory:skill-memory": {
"next_steps": ["workflow:plan", "cli:analyze"],
"related": ["memory:load-skill-memory"]
},
"memory:workflow-skill-memory": {
"related": ["memory:skill-memory"],
"next_steps": ["workflow:plan"]
},
# CLI modes
"cli:execute": {
"alternatives": ["cli:codex-execute"],
"related": ["cli:analyze", "cli:chat"]
},
"cli:analyze": {
"related": ["cli:chat", "cli:mode:code-analysis"],
"next_steps": ["cli:execute"]
},
# Brainstorming
"workflow:brainstorm:artifacts": {
"next_steps": ["workflow:brainstorm:synthesis", "workflow:plan"],
"related": ["workflow:brainstorm:auto-parallel"]
},
"workflow:brainstorm:synthesis": {
"prerequisites": ["workflow:brainstorm:artifacts"],
"next_steps": ["workflow:plan"]
},
"workflow:brainstorm:auto-parallel": {
"next_steps": ["workflow:brainstorm:synthesis", "workflow:plan"],
"related": ["workflow:brainstorm:artifacts"]
},
# Test workflows
"workflow:test-gen": {
"prerequisites": ["workflow:execute"],
"next_steps": ["workflow:test-cycle-execute"]
},
"workflow:test-fix-gen": {
"alternatives": ["workflow:test-gen"],
"next_steps": ["workflow:test-cycle-execute"]
},
"workflow:test-cycle-execute": {
"prerequisites": ["workflow:test-gen", "workflow:test-fix-gen"],
"related": ["workflow:tdd-verify"]
},
# UI Design workflows
"workflow:ui-design:explore-auto": {
"calls_internally": ["workflow:ui-design:capture", "workflow:ui-design:style-extract", "workflow:ui-design:layout-extract"],
"next_steps": ["workflow:ui-design:generate"]
},
"workflow:ui-design:imitate-auto": {
"calls_internally": ["workflow:ui-design:capture"],
"next_steps": ["workflow:ui-design:generate"]
}
}
return relationships
def identify_essential_commands(all_commands: List[Dict]) -> List[Dict]:
"""Identify the most essential commands for beginners."""
# Essential command names (14 most important) - use full command paths
essential_names = [
"workflow:plan",
"workflow:execute",
"workflow:status",
"workflow:session:start",
"task:execute",
"cli:analyze",
"cli:chat",
"memory:docs",
"workflow:brainstorm:artifacts",
"workflow:action-plan-verify",
"workflow:resume",
"workflow:review",
"version",
"enhance-prompt"
]
essential = []
for cmd in all_commands:
# Check command name without leading slash
cmd_name = cmd['command'].lstrip('/')
if cmd_name in essential_names:
essential.append(cmd)
# Sort by order in essential_names
essential.sort(key=lambda x: essential_names.index(x['command'].lstrip('/')))
return essential[:14] # Limit to 14
def main():
"""Main analysis function."""
import sys
import io
# Fix Windows console encoding
if sys.platform == 'win32':
sys.stdout = io.TextIOWrapper(sys.stdout.buffer, encoding='utf-8')
print("Analyzing command files...")
# Find all command files
command_files = list(COMMANDS_DIR.rglob("*.md"))
print(f"Found {len(command_files)} command files")
# Analyze each command
all_commands = []
for cmd_file in sorted(command_files):
try:
metadata = analyze_command_file(cmd_file)
all_commands.append(metadata)
print(f" OK {metadata['command']}")
except Exception as e:
print(f" ERROR analyzing {cmd_file}: {e}")
print(f"\nAnalyzed {len(all_commands)} commands")
# Generate index files
INDEX_DIR.mkdir(parents=True, exist_ok=True)
# 1. all-commands.json
all_commands_path = INDEX_DIR / "all-commands.json"
with open(all_commands_path, 'w', encoding='utf-8') as f:
json.dump(all_commands, f, indent=2, ensure_ascii=False)
print(f"\nOK Generated {all_commands_path} ({os.path.getsize(all_commands_path)} bytes)")
# 2. by-category.json
by_category = defaultdict(lambda: defaultdict(list))
for cmd in all_commands:
cat = cmd['category']
subcat = cmd['subcategory'] or '_root'
by_category[cat][subcat].append(cmd)
by_category_path = INDEX_DIR / "by-category.json"
with open(by_category_path, 'w', encoding='utf-8') as f:
json.dump(dict(by_category), f, indent=2, ensure_ascii=False)
print(f"OK Generated {by_category_path} ({os.path.getsize(by_category_path)} bytes)")
# 3. by-use-case.json
by_use_case = defaultdict(list)
for cmd in all_commands:
by_use_case[cmd['usage_scenario']].append(cmd)
by_use_case_path = INDEX_DIR / "by-use-case.json"
with open(by_use_case_path, 'w', encoding='utf-8') as f:
json.dump(dict(by_use_case), f, indent=2, ensure_ascii=False)
print(f"OK Generated {by_use_case_path} ({os.path.getsize(by_use_case_path)} bytes)")
# 4. essential-commands.json
essential = identify_essential_commands(all_commands)
essential_path = INDEX_DIR / "essential-commands.json"
with open(essential_path, 'w', encoding='utf-8') as f:
json.dump(essential, f, indent=2, ensure_ascii=False)
print(f"OK Generated {essential_path} ({os.path.getsize(essential_path)} bytes)")
# 5. command-relationships.json
relationships = build_command_relationships()
relationships_path = INDEX_DIR / "command-relationships.json"
with open(relationships_path, 'w', encoding='utf-8') as f:
json.dump(relationships, f, indent=2, ensure_ascii=False)
print(f"OK Generated {relationships_path} ({os.path.getsize(relationships_path)} bytes)")
# Print summary statistics
print("\n=== Summary Statistics ===")
print(f"Total commands: {len(all_commands)}")
print(f"\nBy category:")
for cat in sorted(by_category.keys()):
total = sum(len(cmds) for cmds in by_category[cat].values())
print(f" {cat}: {total}")
for subcat in sorted(by_category[cat].keys()):
if subcat != '_root':
print(f" - {subcat}: {len(by_category[cat][subcat])}")
print(f"\nBy usage scenario:")
for scenario in sorted(by_use_case.keys()):
print(f" {scenario}: {len(by_use_case[scenario])}")
print(f"\nBy difficulty:")
difficulty_counts = defaultdict(int)
for cmd in all_commands:
difficulty_counts[cmd['difficulty']] += 1
for difficulty in ['Beginner', 'Intermediate', 'Advanced']:
print(f" {difficulty}: {difficulty_counts[difficulty]}")
print(f"\nEssential commands: {len(essential)}")
if __name__ == '__main__':
main()

View File

@@ -0,0 +1,130 @@
#!/bin/bash
##############################################################################
# 命令索引更新脚本
# 用途: 维护者使用此脚本重新生成命令索引文件
# 使用: bash update-index.sh
##############################################################################
set -e # 遇到错误立即退出
# 颜色输出
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
NC='\033[0m' # No Color
# 获取脚本所在目录
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
SKILL_DIR="$(dirname "$SCRIPT_DIR")"
COMMANDS_DIR="$(dirname "$(dirname "$SKILL_DIR")")/commands"
INDEX_DIR="$SKILL_DIR/index"
echo -e "${GREEN}=== 命令索引更新工具 ===${NC}"
echo ""
echo "技能目录: $SKILL_DIR"
echo "命令目录: $COMMANDS_DIR"
echo "索引目录: $INDEX_DIR"
echo ""
# 检查命令目录是否存在
if [ ! -d "$COMMANDS_DIR" ]; then
echo -e "${RED}错误: 命令目录不存在: $COMMANDS_DIR${NC}"
exit 1
fi
# 检查 gemini 是否可用
if ! command -v gemini &> /dev/null; then
echo -e "${RED}错误: gemini 命令未找到${NC}"
echo "请确保 gemini CLI 工具已安装并在 PATH 中"
exit 1
fi
# 统计命令文件数量
COMMAND_COUNT=$(find "$COMMANDS_DIR" -name "*.md" -type f | wc -l)
echo -e "${YELLOW}发现 $COMMAND_COUNT 个命令文件${NC}"
echo ""
# 备份现有索引(如果存在)
if [ -d "$INDEX_DIR" ] && [ "$(ls -A $INDEX_DIR)" ]; then
BACKUP_DIR="$INDEX_DIR/.backup-$(date +%Y%m%d-%H%M%S)"
echo -e "${YELLOW}备份现有索引到: $BACKUP_DIR${NC}"
mkdir -p "$BACKUP_DIR"
cp "$INDEX_DIR"/*.json "$BACKUP_DIR/" 2>/dev/null || true
echo ""
fi
# 确保索引目录存在
mkdir -p "$INDEX_DIR"
echo -e "${GREEN}开始生成索引...${NC}"
echo ""
# 使用 gemini 生成索引
cd "$COMMANDS_DIR" && gemini -p "
PURPOSE: 解析所有命令文件(约 $COMMAND_COUNT 个)并重新生成结构化命令索引
TASK:
• 扫描所有 .md 命令文件(包括子目录)
• 提取每个命令的元数据name, description, arguments, category, subcategory
• 分析命令的使用场景和难度等级(初级/中级/高级)
• 识别命令之间的关联关系(通常一起使用的命令、前置依赖、后续推荐)
• 识别10-15个最常用的核心命令
• 按使用场景分类planning/implementation/testing/documentation/session-management
• 生成5个 JSON 索引文件到 $INDEX_DIR 目录
MODE: write
CONTEXT: @**/*.md | Memory: 命令分为4大类workflow, cli, memory, task需要理解每个命令的实际用途来生成准确的索引
EXPECTED: 生成5个规范的 JSON 文件:
1. all-commands.json - 包含所有命令的完整信息数组
2. by-category.json - 按 category/subcategory 层级组织
3. by-use-case.json - 按使用场景planning/implementation/testing等组织
4. essential-commands.json - 核心命令列表10-15个
5. command-relationships.json - 命令关联关系图command -> related_commands数组
每个命令对象包含name, description, arguments, category, subcategory, usage_scenario, difficulty, file_path
RULES: 保持一致的数据结构JSON格式严格遵循规范确保所有命令都被包含 | write=CREATE
" -m gemini-2.5-flash --approval-mode yolo
# 检查生成结果
if [ $? -eq 0 ]; then
echo ""
echo -e "${GREEN}✓ 索引生成成功!${NC}"
echo ""
echo "生成的索引文件:"
ls -lh "$INDEX_DIR"/*.json
echo ""
# 验证文件
echo -e "${YELLOW}验证索引文件...${NC}"
REQUIRED_FILES=("all-commands.json" "by-category.json" "by-use-case.json" "essential-commands.json" "command-relationships.json")
ALL_EXIST=true
for file in "${REQUIRED_FILES[@]}"; do
if [ -f "$INDEX_DIR/$file" ]; then
echo -e "${GREEN}${NC} $file"
else
echo -e "${RED}${NC} $file (缺失)"
ALL_EXIST=false
fi
done
echo ""
if [ "$ALL_EXIST" = true ]; then
echo -e "${GREEN}=== 索引更新完成!===${NC}"
echo ""
echo "后续步骤:"
echo "1. 验证生成的索引内容是否正确"
echo "2. 提交更新: git add .claude/skills/command-guide/index/"
echo "3. 创建提交: git commit -m \"docs: 更新命令索引\""
echo "4. 推送更新: git push"
echo ""
echo "团队成员执行 'git pull' 后将自动获取最新索引"
else
echo -e "${RED}=== 索引更新不完整,请检查错误 ===${NC}"
exit 1
fi
else
echo ""
echo -e "${RED}✗ 索引生成失败${NC}"
echo "请检查 gemini 输出的错误信息"
exit 1
fi

View File

@@ -0,0 +1,63 @@
---
name: Bug 报告
about: 报告命令执行问题或系统错误
labels: bug
---
# Bug 报告
## 问题描述
<!-- 简要描述遇到的问题 -->
## 执行的命令
```bash
<!-- 粘贴执行的命令 -->
```
## 期望行为
<!-- 描述您期望的结果是什么 -->
## 实际行为
<!-- 描述实际发生的情况,包括错误信息 -->
## 复现步骤
1.
2.
3.
## 环境信息
- **操作系统**: Windows / Mac / Linux
- **OS 版本**:
- **Claude Code 版本**:
- **相关命令**:
- **相关文件路径**:
## 错误日志
```
<!-- 如有错误信息或日志,请粘贴在这里 -->
```
## 额外上下文
<!-- 任何其他有助于理解问题的信息,如:
- 是否是首次执行此命令
- 之前是否成功执行过
- 最近是否修改过配置或文件
- 相关的 workflow session ID如适用
-->
## 可能的解决方案(可选)
<!-- 如果您有任何想法或建议,请在这里描述 -->
---
**报告日期**: <!-- 自动填充 -->
**报告人**: <!-- 自动填充 -->

View File

@@ -0,0 +1,64 @@
---
name: 功能请求
about: 建议新功能或改进现有功能
labels: enhancement
---
# 功能请求
## 功能概述
<!-- 简要描述您希望添加或改进的功能 -->
## 问题背景
<!-- 描述当前的痛点或限制,这个功能将解决什么问题? -->
## 建议的解决方案
<!-- 详细描述您建议的功能实现方式 -->
## 使用场景
<!-- 描述具体的使用场景和示例 -->
### 场景 1:
**情况**:
**操作**:
**期望结果**:
### 场景 2可选:
**情况**:
**操作**:
**期望结果**:
## 预期效果
<!-- 描述这个功能将如何改善工作流程或用户体验 -->
## 参考示例(可选)
<!-- 如果有类似功能的参考实现(其他工具、项目等),请提供链接或描述 -->
## 替代方案(可选)
<!-- 描述您考虑过的其他解决方案 -->
## 优先级
- [ ] 高 - 严重影响工作效率
- [ ] 中 - 有明显改善但有变通方案
- [ ] 低 - 锦上添花
## 额外信息
<!-- 任何其他相关信息,如:
- 相关的命令或工作流
- 技术实现建议
- 可能的挑战或限制
-->
---
**提交日期**: <!-- 自动填充 -->
**提交人**: <!-- 自动填充 -->

View File

@@ -0,0 +1,81 @@
---
name: 问题咨询
about: 询问使用方法、最佳实践或寻求帮助
labels: question
---
# 问题咨询
## 问题描述
<!-- 清楚地描述您的问题或困惑 -->
## 当前情况
<!-- 描述您当前的情况和已尝试的方法 -->
### 相关命令
```bash
<!-- 如果与特定命令相关,请粘贴命令 -->
```
### 已尝试的方法
1.
2.
3.
## 具体疑问
<!-- 详细说明您想要了解的内容 -->
### 问题 1:
### 问题 2可选:
## 期望的解答
<!-- 描述您期望获得什么样的帮助或解答 -->
- [ ] 使用方法说明
- [ ] 最佳实践建议
- [ ] 示例代码或配置
- [ ] 故障排除指导
- [ ] 概念解释
- [ ] 其他:
## 上下文信息
### 使用场景
<!-- 描述您的具体使用场景 -->
### 项目类型
<!-- 如果相关描述您的项目类型Web 应用、API 服务、数据分析等 -->
### 相关文档
<!-- 列出您已经查看过的相关文档 -->
- [ ] getting-started.md
- [ ] workflow-patterns.md
- [ ] cli-tools-guide.md
- [ ] troubleshooting.md
- [ ] 命令文档:
- [ ] 其他:
## 紧急程度
- [ ] 紧急 - 阻碍当前工作
- [ ] 一般 - 希望尽快了解
- [ ] 不急 - 学习和改进目的
## 额外信息
<!-- 任何其他可能有助于理解或解答的信息 -->
---
**提问日期**: <!-- 自动填充 -->
**提问人**: <!-- 自动填充 -->

View File

@@ -0,0 +1,95 @@
# AI Prompt: Universal Creative Exploration Template (Chinese Output)
## I. CORE DIRECTIVE
You are an **Innovative Problem-Solving Catalyst**. Approach tasks with creative thinking, explore multiple solution paths, and generate novel approaches while maintaining practical viability. Responses **MUST** be in **Chinese (中文)**.
## II. CORE CAPABILITIES & THINKING MODE
**Capabilities**: Divergent thinking, pattern recognition, creative synthesis, constraint reframing, rapid prototyping, contextual adaptation, elegant simplicity, future-oriented design
**Thinking Mode**: Exploratory & open-minded, adaptive & flexible, synthesis-driven, innovation-focused
## III. EXPLORATION PHASES
**Divergent Phase**: Multiple perspectives, analogies & metaphors, constraint questioning, alternative approaches (3+), what-if scenarios
**Convergent Phase**: Pattern integration, practical viability, elegant simplicity, context optimization, future proofing
**Validation Phase**: Constraint compliance, risk assessment, proof of concept, iterative refinement, documentation
## IV. QUALITY STANDARDS
**Innovation**: Novelty, elegance, effectiveness, flexibility, insight, viability
**Process**: Exploration breadth, synthesis quality, justification clarity, alternatives documented
## V. RESPONSE STRUCTURE (Output in Chinese)
---
### 0. 创造性思考过程 (Creative Thinking Process)
* **问题重构**: 从多个角度理解和重新定义问题
* **灵感来源**: 识别可借鉴的模式、类比或跨领域经验
* **可能性空间**: 探索不同解决方案的可能性
* **约束与自由**: 识别硬性约束与创新空间
* **综合策略**: 规划如何整合不同思路形成最优方案
### 1. 问题深度理解 (Deep Problem Understanding)
* **表层需求**: 明确的功能和非功能需求
* **隐含目标**: 未明说但重要的用户期望和体验目标
* **约束条件**: 必须遵守的技术和业务约束
* **机会空间**: 可以创新和优化的领域
### 2. 多角度探索 (Multi-Perspective Exploration)
* **视角1-3**: 从不同角度分析问题,每个视角包含:核心洞察、解决思路、优势与局限
### 3. 跨领域类比 (Cross-Domain Analogies)
* **类比1-2**: 相关领域或模式,说明如何应用到当前问题
### 4. 候选方案生成 (Solution Candidates - 2-3个)
* **方案A/B/C**: 每个方案包含:核心思路、关键特点、优势、潜在挑战、适用场景
### 5. 方案综合与优化 (Solution Synthesis & Optimization)
* **选择理由**: 为什么选择或综合某些方案
* **综合策略**: 如何结合不同方案的优点
* **简化优化**: 如何使方案更简洁优雅
* **创新点**: 方案的独特价值和创新之处
### 6. 实施细节与代码 (Implementation Details & Code)
* **架构设计**: 清晰的结构设计
* **核心实现**: 关键功能的实现
* **扩展点**: 预留的扩展和定制接口
* **优雅之处**: 设计中的巧妙和优雅元素
### 7. 验证与迭代 (Validation & Iteration)
* **快速验证**: 如何快速验证核心假设
* **迭代路径**: 从MVP到完整方案的演进路径
* **反馈机制**: 如何收集反馈并改进
* **风险应对**: 主要风险和应对策略
### 8. 替代方案记录 (Alternative Approaches)
* **未采纳方案**: 列出其他考虑过的方案
* **未来可能性**: 可能在未来更合适的方案
* **经验教训**: 从探索过程中学到的洞察
### 9. 总结与展望 (Summary & Future Vision)
* **核心价值**: 该方案的核心价值和创新点
* **关键决策**: 重要的设计决策及其理由
* **扩展可能**: 未来可能的扩展方向
* **开放性**: 留下的开放问题和探索空间
---
## VI. STYLE & CONSTRAINTS
**Style**: Exploratory & open, insightful & thoughtful, enthusiastic & positive, clear & inspiring, balanced & practical
**Core Constraints**:
- Practical viability - innovation must be implementable
- Constraint awareness - creativity within boundaries
- Value-driven - innovation must add real value
- Simplicity preference - elegant solutions over complex ones
- Documentation - alternative approaches must be recorded
- Justification - creative choices must be reasoned
- Iterative mindset - embrace refinement and evolution
## VII. CREATIVE THINKING TECHNIQUES (Optional)
**Toolkit**: First principles thinking, inversion, constraint removal, analogical reasoning, combination & synthesis, abstraction ladder, pattern languages, what-if scenarios
**Application**: Select 2-3 techniques, apply during divergent phase, document insights, inform synthesis
## VIII. FINAL VALIDATION
Before finalizing, verify: Multiple perspectives explored, 2-3 distinct approaches considered, cross-domain analogies identified, solution elegance pursued, practical constraints respected, innovation points articulated, alternatives documented, implementation viable, future extensibility considered, rationale clear

View File

@@ -0,0 +1,92 @@
# AI Prompt: Universal Rigorous Execution Template (Chinese Output)
## I. CORE DIRECTIVE
You are a **Precision-Driven Expert System**. Execute tasks with rigorous accuracy, systematic validation, and adherence to standards. Responses **MUST** be in **Chinese (中文)**.
## II. CORE CAPABILITIES & THINKING MODE
**Capabilities**: Systematic methodology, specification adherence, validation & verification, edge case handling, error prevention, formal reasoning, documentation excellence, quality assurance
**Thinking Mode**: Rigorous & methodical, defensive & cautious, standards-driven, traceable & auditable
## III. EXECUTION CHECKLIST
**Before Starting**: Clarify requirements, identify standards, plan validation, assess risks
**During Execution**: Follow patterns, validate continuously, handle edge cases, maintain consistency, document decisions
**After Completion**: Comprehensive testing, code review, backward compatibility, documentation update
## IV. QUALITY STANDARDS
**Code**: Correctness, robustness, maintainability, performance, security, testability
**Process**: Repeatability, traceability, reversibility, incremental progress
## V. RESPONSE STRUCTURE (Output in Chinese)
---
### 0. 规范性思考过程 (Rigorous Thinking Process)
* **任务理解**: 明确任务目标、范围和约束条件
* **标准识别**: 确定适用的规范、最佳实践和质量标准
* **风险分析**: 识别潜在问题、边界条件和失败模式
* **验证计划**: 定义成功标准和验证检查点
* **执行策略**: 制定系统化、可追溯的实施方案
### 1. 需求分析与验证 (Requirement Analysis & Validation)
* **核心需求**: 列出所有明确的功能和非功能需求
* **隐式约束**: 识别未明确说明但必须遵守的约束
* **边界条件**: 明确输入范围、特殊情况和异常场景
* **验证标准**: 定义可测试的成功标准
### 2. 标准与模式分析 (Standards & Pattern Analysis)
* **适用标准**: 列出相关编码规范、设计模式、最佳实践
* **现有模式**: 识别项目中类似的成功实现
* **依赖关系**: 分析与现有代码的集成点和依赖
* **兼容性要求**: 确保向后兼容和接口稳定性
### 3. 详细实施方案 (Detailed Implementation Plan)
* **分解步骤**: 将任务分解为小的、可验证的步骤
* **关键决策**: 记录所有重要的技术决策及其理由
* **边界处理**: 说明如何处理边界条件和错误情况
* **验证点**: 在每个步骤设置验证检查点
### 4. 实施细节与代码 (Implementation Details & Code)
* **核心逻辑**: 实现主要功能,确保正确性
* **错误处理**: 完善的异常捕获和错误处理
* **输入验证**: 严格的输入校验和边界检查
* **代码注释**: 关键逻辑的清晰注释说明
### 5. 测试与验证 (Testing & Validation)
* **单元测试**: 覆盖所有主要功能和边界条件
* **集成测试**: 验证与现有系统的集成
* **边界测试**: 测试极端情况和异常输入
* **回归测试**: 确保未破坏现有功能
### 6. 质量检查清单 (Quality Checklist)
- [ ] 功能完整性: 所有需求都已实现
- [ ] 规范遵循: 符合代码规范和最佳实践
- [ ] 边界处理: 所有边界条件都已处理
- [ ] 错误处理: 完善的异常处理机制
- [ ] 向后兼容: 未破坏现有功能
- [ ] 文档完整: 代码注释和文档齐全
- [ ] 测试覆盖: 全面的测试覆盖
- [ ] 性能优化: 符合性能要求
### 7. 总结与建议 (Summary & Recommendations)
* **实施总结**: 简要总结完成的工作
* **关键决策**: 重申重要技术决策
* **后续建议**: 提出改进和优化建议
* **风险提示**: 指出需要关注的潜在问题
---
## VI. STYLE & CONSTRAINTS
**Style**: Formal & professional, precise & unambiguous, evidence-based, defensive & cautious, structured & systematic
**Core Constraints**:
- Zero tolerance for errors - correctness is paramount
- Standards compliance - follow established conventions
- Complete validation - all assumptions must be validated
- Comprehensive testing - all paths must be tested
- Full documentation - all decisions must be documented
- Backward compatibility - existing functionality is sacred
- No shortcuts - quality cannot be compromised
## VII. FINAL VALIDATION
Before finalizing, verify: All requirements addressed, edge cases handled, standards followed, decisions documented, code tested, documentation complete, backward compatibility maintained, quality standards met

View File

@@ -69,7 +69,6 @@ codex -C [dir] --full-auto exec "[prompt]" [-m model] [--skip-git-repo-check -s
| Architecture Review | Gemini → Qwen | analysis | `analysis/02-review-architecture.txt` |
| Feature Implementation | Codex | auto | `development/02-implement-feature.txt` |
| Component Development | Codex | auto | `development/02-implement-component-ui.txt` |
| Documentation | Gemini/Qwen | write | `memory/02-document-module-structure.txt` |
| Test Generation | Codex | write | `development/02-generate-tests.txt` |
### Core Principles
@@ -79,10 +78,14 @@ codex -C [dir] --full-auto exec "[prompt]" [-m model] [--skip-git-repo-check -s
- **Default to tools** - Use for most coding tasks, no matter how small
- **Minimize context noise** - Use `cd` + `--include-directories` to focus on relevant files
- **⚠️ Choose templates by need** - Select templates based on task requirements:
- `00-*` for universal fallback when no specific template matches
- `01-*` for general exploratory/diagnostic work
- `02-*` for common implementation/analysis tasks
- `03-*` for specialized domains
- **⚠️ Always specify templates** - Include appropriate template in RULES field via `$(cat ~/.claude/workflows/cli-templates/prompts/.../...txt)`
- **⚠️ Universal templates as fallback** - Use universal templates when no specific template matches your needs:
- `universal/00-universal-rigorous-style.txt` for precision-critical tasks
- `universal/00-universal-creative-style.txt` for exploratory/innovative tasks
- **⚠️ Write protection** - Require EXPLICIT MODE=write or MODE=auto specification
---
@@ -462,6 +465,8 @@ RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/02-analyze-code-
- **Why**: Shell executes `$(...)` in subshell where path is safe
**Examples**:
- Universal rigorous: `$(cat ~/.claude/workflows/cli-templates/prompts/universal/00-universal-rigorous-style.txt) | Critical production refactoring`
- Universal creative: `$(cat ~/.claude/workflows/cli-templates/prompts/universal/00-universal-creative-style.txt) | Explore alternative architecture approaches`
- General template: `$(cat ~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt) | Focus on authentication module`
- Specialized template: `$(cat ~/.claude/workflows/cli-templates/prompts/analysis/02-analyze-code-patterns.txt) | React hooks only`
- Multiple: `$(cat template1.txt) $(cat template2.txt) | Enterprise standards`
@@ -472,15 +477,48 @@ RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/02-analyze-code-
**Base**: `~/.claude/workflows/cli-templates/`
**Naming Convention**:
- `00-*` - **Universal fallback templates** (use when no specific template matches)
- `01-*` - Universal, high-frequency templates
- `02-*` - Common specialized templates
- `03-*` - Domain-specific, less frequent templates
**Note**: Number prefix indicates category and frequency, not required usage order. Choose based on task needs.
**Universal Templates (Fallback)**:
When no specific template matches your task requirements, use one of these universal templates based on the desired execution style:
1. **Rigorous Style** (`universal/00-universal-rigorous-style.txt`)
- **Use for**: Precision-critical tasks requiring systematic methodology
- **Characteristics**:
- Strict adherence to standards and specifications
- Comprehensive validation and edge case handling
- Defensive programming and error prevention
- Full documentation and traceability
- **Best for**: Production code, critical systems, refactoring, compliance tasks
- **Thinking mode**: Systematic, methodical, standards-driven
2. **Creative Style** (`universal/00-universal-creative-style.txt`)
- **Use for**: Exploratory tasks requiring innovative solutions
- **Characteristics**:
- Multi-perspective problem exploration
- Pattern synthesis from different domains
- Alternative approach generation
- Elegant simplicity pursuit
- **Best for**: New feature design, architecture exploration, optimization, problem-solving
- **Thinking mode**: Exploratory, synthesis-driven, innovation-focused
**Selection Guide**:
- **Rigorous**: When correctness, reliability, and compliance are paramount
- **Creative**: When innovation, flexibility, and elegant solutions are needed
- **Specific template**: When task matches predefined category (analysis, development, planning, etc.)
**Available Templates**:
```
prompts/
├── universal/ # ← NEW: Universal fallback templates
│ ├── 00-universal-rigorous-style.txt # Precision & standards-driven
│ └── 00-universal-creative-style.txt # Innovation & exploration-focused
├── analysis/
│ ├── 01-trace-code-execution.txt
│ ├── 01-diagnose-bug-root-cause.txt
@@ -496,8 +534,6 @@ prompts/
│ ├── 02-generate-tests.txt
│ ├── 02-implement-component-ui.txt
│ └── 03-debug-runtime-issues.txt
├── memory/
│ └── 02-document-module-structure.txt
└── planning/
├── 01-plan-architecture-design.txt
├── 02-breakdown-task-steps.txt
@@ -510,6 +546,10 @@ prompts/
| Task Type | Tool | Template |
|-----------|------|----------|
| **Universal Fallbacks** | | |
| Precision-Critical Tasks | Gemini/Qwen/Codex | `universal/00-universal-rigorous-style.txt` |
| Exploratory/Innovative Tasks | Gemini/Qwen/Codex | `universal/00-universal-creative-style.txt` |
| **Analysis Tasks** | | |
| Execution Tracing | Gemini (Qwen fallback) | `analysis/01-trace-code-execution.txt` |
| Bug Diagnosis | Gemini (Qwen fallback) | `analysis/01-diagnose-bug-root-cause.txt` |
| Code Pattern Analysis | Gemini (Qwen fallback) | `analysis/02-analyze-code-patterns.txt` |
@@ -518,17 +558,18 @@ prompts/
| Performance Analysis | Gemini (Qwen fallback) | `analysis/03-analyze-performance.txt` |
| Security Assessment | Gemini (Qwen fallback) | `analysis/03-assess-security-risks.txt` |
| Quality Standards | Gemini (Qwen fallback) | `analysis/03-review-quality-standards.txt` |
| **Planning Tasks** | | |
| Architecture Planning | Gemini (Qwen fallback) | `planning/01-plan-architecture-design.txt` |
| Task Breakdown | Gemini (Qwen fallback) | `planning/02-breakdown-task-steps.txt` |
| Component Design | Gemini (Qwen fallback) | `planning/02-design-component-spec.txt` |
| Concept Evaluation | Gemini (Qwen fallback) | `planning/03-evaluate-concept-feasibility.txt` |
| Migration Planning | Gemini (Qwen fallback) | `planning/03-plan-migration-strategy.txt` |
| **Development Tasks** | | |
| Feature Development | Codex | `development/02-implement-feature.txt` |
| Refactoring | Codex | `development/02-refactor-codebase.txt` |
| Test Generation | Codex | `development/02-generate-tests.txt` |
| Component Implementation | Codex | `development/02-implement-component-ui.txt` |
| Debugging | Codex | `development/03-debug-runtime-issues.txt` |
| Module Documentation | Gemini (Qwen fallback) | `memory/02-document-module-structure.txt` |
---

View File

@@ -5,6 +5,239 @@ All notable changes to Claude Code Workflow (CCW) will be documented in this fil
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [5.5.0] - 2025-11-06
### 🎯 Interactive Command Guide & Enhanced Documentation
This release introduces a comprehensive command-guide skill with interactive help, enhanced command descriptions, and an organized 5-index command system for better discoverability and workflow guidance.
#### ✨ Added
**Command-Guide Skill**:
-**Interactive Help System** - New command-guide skill activated by CCW-help and CCW-issue keywords
- 🔍 Mode 1: Command Search - Find commands by keyword, category, or use-case
- 🤖 Mode 2: Smart Recommendations - Context-aware next-step suggestions
- 📖 Mode 3: Full Documentation - Detailed parameter info, examples, best practices
- 🎓 Mode 4: Beginner Onboarding - Top 14 essential commands with learning path
- 📝 Mode 5: Issue Reporting - Guided bug report and feature request templates
**5-Index Command System**:
-**all-commands.json** (30KB) - Complete catalog of 69 commands with full metadata
-**by-category.json** (33KB) - Hierarchical organization (workflow/cli/memory/task/general)
-**by-use-case.json** (32KB) - Grouped by 10 usage scenarios
-**essential-commands.json** (5.8KB) - Top 14 most-used commands for quick reference
-**command-relationships.json** (13KB) - Workflow guidance with next-steps and dependencies
**Issue Templates**:
-**Bug Report Template** - Standardized bug reporting with environment info
-**Feature Request Template** - Structured feature proposals with use cases
-**Question Template** - Help request format for user support
#### 🔄 Changed
**Command Descriptions Enhanced** (69 files):
- 🔄 **Detailed Functionality** - All command descriptions updated from basic to comprehensive
- Includes tools used (Gemini/Qwen/Codex)
- Specifies agents invoked
- Lists workflow phases
- Documents output files
- Mentions key flags and modes
- 🔄 **Example Updates**:
- `workflow:plan`: "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution"
- `cli:execute`: "Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection"
- `memory:update-related`: "Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback"
**Index Organization**:
- 🔄 **Use-Case Categories Expanded** - From 2 to 10 distinct scenarios
- session-management, implementation, documentation, planning, ui-design, testing, brainstorming, analysis, monitoring, utilities
- 🔄 **Command Relationships Comprehensive** - All 69 commands mapped with:
- `calls_internally` - Commands auto-invoked (built-in)
- `next_steps` - User-executed next commands (sequential)
- `prerequisites` - Commands to run before
- `alternatives` - Similar-purpose commands
**Maintenance Tools**:
- 🔄 **analyze_commands.py** - Moved to scripts/ directory
- Auto-generates all 5 index files from command frontmatter
- Validates JSON syntax
- Provides statistical reports
#### 📝 Documentation
**New Files**:
-**guides/index-structure.md** - Complete index file schema documentation
-**guides/implementation-details.md** - 5-mode implementation logic
-**guides/examples.md** - Usage examples for all modes
-**guides/getting-started.md** - 5-minute quickstart guide
-**guides/workflow-patterns.md** - Common workflow examples
-**guides/cli-tools-guide.md** - Gemini/Qwen/Codex usage
-**guides/troubleshooting.md** - Common issues and solutions
**Updated Files**:
- 🔄 **README.md** - Added "Need Help?" section with CCW-help/CCW-issue usage
- 🔄 **README_CN.md** - Chinese version of help documentation
- 🔄 **SKILL.md** - Optimized to 179 lines (from 412, 56.6% reduction)
- Clear 5-mode operation structure
- Explicit CCW-help and CCW-issue triggers
- Progressive disclosure pattern
#### 🎯 Benefits
**User Experience**:
- 📦 **Easier Discovery** - CCW-help provides instant command search and recommendations
- 📦 **Better Guidance** - Smart next-step suggestions based on workflow context
- 📦 **Faster Onboarding** - Essential commands list gets beginners started quickly
- 📦 **Simplified Reporting** - CCW-issue generates proper bug/feature templates
**Developer Experience**:
-**Comprehensive Metadata** - All 69 commands fully documented with tools, agents, phases
-**Workflow Clarity** - Command relationships show built-in vs sequential execution
-**Automated Maintenance** - analyze_commands.py regenerates indexes from source
-**Quality Documentation** - 7 guide files cover all aspects of the system
**System Organization**:
- 🏗️ **Structured Indexes** - 5 JSON files provide multiple access patterns
- 🏗️ **Clear Relationships** - Distinguish built-in calls from user workflows
- 🏗️ **Scalable Architecture** - Easy to add new commands with auto-indexing
---
## [5.4.0] - 2025-11-06
### 🎯 CLI Template System Reorganization
This release introduces a comprehensive reorganization of the CLI template system with priority-based naming and enhanced error handling for Gemini models.
#### ✨ Added
**Template Priority System**:
-**Priority-Based Naming** - All templates now use priority prefixes for better organization
- `01-*` prefix: Universal, high-frequency templates (e.g., trace-code-execution, diagnose-bug-root-cause)
- `02-*` prefix: Common specialized templates (e.g., implement-feature, analyze-code-patterns)
- `03-*` prefix: Domain-specific, less frequent templates (e.g., assess-security-risks, debug-runtime-issues)
-**19 Templates Reorganized** - Complete template system restructure across 4 directories
- analysis/ (8 templates): Code analysis, bug diagnosis, architecture review, security assessment
- development/ (5 templates): Feature implementation, refactoring, testing, UI components
- planning/ (5 templates): Architecture design, task breakdown, component specs, migration
- memory/ (1 template): Module documentation
-**Template Selection Guidance** - Choose templates based on task needs, not sequence numbers
**Error Handling Enhancement**:
-**Gemini 404 Fallback Strategy** - Automatic model fallback for improved reliability
- If `gemini-3-pro-preview-11-2025` returns 404 error, automatically fallback to `gemini-2.5-pro`
- Comprehensive error handling documentation for HTTP 429 and HTTP 404 errors
- Added to both Model Selection and Tool Specifications sections
#### 🔄 Changed
**Template File Reorganization** (19 files):
*Analysis Templates*:
- `code-execution-tracing.txt``01-trace-code-execution.txt`
- `bug-diagnosis.txt``01-diagnose-bug-root-cause.txt` (moved from development/)
- `pattern.txt``02-analyze-code-patterns.txt`
- `architecture.txt``02-review-architecture.txt`
- `code-review.txt``02-review-code-quality.txt` (moved from review/)
- `performance.txt``03-analyze-performance.txt`
- `security.txt``03-assess-security-risks.txt`
- `quality.txt``03-review-quality-standards.txt`
*Development Templates*:
- `feature.txt``02-implement-feature.txt`
- `refactor.txt``02-refactor-codebase.txt`
- `testing.txt``02-generate-tests.txt`
- `component.txt``02-implement-component-ui.txt`
- `debugging.txt``03-debug-runtime-issues.txt`
*Planning Templates*:
- `architecture-planning.txt``01-plan-architecture-design.txt`
- `task-breakdown.txt``02-breakdown-task-steps.txt`
- `component.txt``02-design-component-spec.txt` (moved from implementation/)
- `concept-eval.txt``03-evaluate-concept-feasibility.txt`
- `migration.txt``03-plan-migration-strategy.txt`
*Memory Templates*:
- `claude-module-unified.txt``02-document-module-structure.txt`
**Directory Structure Optimization**:
- 🔄 **Bug Diagnosis Reclassified** - Moved from development/ to analysis/ (diagnostic work, not implementation)
- 🔄 **Removed Redundant Directories** - Eliminated implementation/ and review/ folders
- 🔄 **Unified Path References** - All command files now use full path format
**Command File Updates** (21 references across 5 files):
- `cli/mode/bug-diagnosis.md` - 6 template references updated
- `cli/mode/code-analysis.md` - 6 template references updated
- `cli/mode/plan.md` - 6 template references updated
- `task/execute.md` - 1 template reference updated
- `workflow/tools/test-task-generate.md` - 2 template references updated
#### 📝 Documentation
**Updated Files**:
- 🔄 **intelligent-tools-strategy.md** - Complete template system guide with new naming convention
- Updated Available Templates section with all new template names
- Enhanced Task-Template Matrix with priority-based organization
- Added Gemini error handling documentation (404 and 429)
- Removed star symbols (⭐) - redundant with priority numbers
-**command-template-update-summary.md** - New file documenting all template reference changes
#### 🎯 Benefits
**Template System Improvements**:
- 📦 **Better Discoverability** - Priority prefixes make it easy to find appropriate templates
- 📦 **Clearer Organization** - Templates grouped by usage frequency and specialization
- 📦 **Consistent Naming** - Descriptive names following `[Priority]-[Action]-[Object]-[Context].txt` pattern
- 📦 **No Breaking Changes** - All command references updated, backward compatible
**Error Handling Enhancements**:
-**Improved Reliability** - Automatic fallback prevents workflow interruption
-**Better Documentation** - Clear guidance for both HTTP 429 and 404 errors
-**User-Friendly** - Transparent error handling without manual intervention
**Workflow Integration**:
- 🔗 All 5 command files seamlessly updated with new template paths
- 🔗 Full path references ensure clarity and maintainability
- 🔗 No user action required - all updates applied systematically
#### 📦 Modified Files
**Templates** (19 renames, 2 directory removals):
- `.claude/workflows/cli-templates/prompts/analysis/` - 8 templates reorganized
- `.claude/workflows/cli-templates/prompts/development/` - 5 templates reorganized
- `.claude/workflows/cli-templates/prompts/planning/` - 5 templates reorganized
- `.claude/workflows/cli-templates/prompts/memory/` - 1 template reorganized
- Removed: `implementation/`, `review/` directories
**Commands** (5 files, 21 references):
- `.claude/commands/cli/mode/bug-diagnosis.md`
- `.claude/commands/cli/mode/code-analysis.md`
- `.claude/commands/cli/mode/plan.md`
- `.claude/commands/task/execute.md`
- `.claude/commands/workflow/tools/test-task-generate.md`
**Documentation**:
- `.claude/workflows/intelligent-tools-strategy.md`
- `.claude/workflows/command-template-update-summary.md` (new)
#### 🔗 Upgrade Notes
**No User Action Required**:
- All template references automatically updated
- Commands work with new template paths
- No breaking changes to existing workflows
**Template Selection**:
- Use priority prefix as a guide, not a requirement
- Choose templates based on your specific task needs
- Number indicates category and frequency, not usage order
**Error Handling**:
- Gemini 404 errors now automatically fallback to `gemini-2.5-pro`
- HTTP 429 errors continue with existing handling (check results existence)
---
## [5.2.2] - 2025-11-03
### ✨ Added

View File

@@ -2,7 +2,7 @@
<div align="center">
[![Version](https://img.shields.io/badge/version-v5.2.0-blue.svg)](https://github.com/catlog22/Claude-Code-Workflow/releases)
[![Version](https://img.shields.io/badge/version-v5.5.0-blue.svg)](https://github.com/catlog22/Claude-Code-Workflow/releases)
[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
[![Platform](https://img.shields.io/badge/platform-Windows%20%7C%20Linux%20%7C%20macOS-lightgrey.svg)]()
@@ -14,13 +14,13 @@
**Claude Code Workflow (CCW)** transforms AI development from simple prompt chaining into a robust, context-first orchestration system. It solves execution uncertainty and error accumulation through structured planning, deterministic execution, and intelligent multi-model orchestration.
> **🎉 Version 5.2: Memory Commands Enhancement**
> **🎉 Version 5.5: Interactive Command Guide & Enhanced Documentation**
>
> **Core Improvements**:
> - **Batch Processing** - Single Level 1 task handles all module trees (67% fewer tasks)
> - **Dual Execution Modes** - Agent Mode and CLI Mode (--cli-execute) support
> - **Pre-computed Analysis** - Unified analysis eliminates redundant CLI calls (67% reduction)
> - **Performance Boost** - 67% fewer file reads, 33% fewer total tasks
> - **Command-Guide Skill** - Interactive help system with CCW-help and CCW-issue triggers
> - **Enhanced Command Descriptions** - All 69 commands updated with detailed functionality descriptions
> - **5-Index Command System** - Organized by category, use-case, relationships, and essentials
> - **Smart Recommendations** - Context-aware next-step suggestions for workflow guidance
>
> See [CHANGELOG.md](CHANGELOG.md) for full details.
@@ -74,6 +74,34 @@ For a detailed technical specification of every command, see the [**COMMAND_SPEC
---
### 💡 **Need Help? Use the Interactive Command Guide**
CCW includes a built-in **command-guide skill** to help you discover and use commands effectively:
- **`CCW-help`** - Get interactive help and command recommendations
- **`CCW-issue`** - Report bugs or request features with guided templates
The command guide provides:
- 🔍 **Smart Command Search** - Find commands by keyword, category, or use-case
- 🤖 **Next-Step Recommendations** - Get suggestions for what to do after any command
- 📖 **Detailed Documentation** - View parameters, examples, and best practices
- 🎓 **Beginner Onboarding** - Learn the top 14 essential commands with a guided learning path
- 📝 **Issue Reporting** - Generate standardized bug reports and feature requests
**Example Usage**:
```
User: "CCW-help"
→ Interactive menu with command search, recommendations, and documentation
User: "What's next after /workflow:plan?"
→ Recommends /workflow:execute, /workflow:action-plan-verify, with workflow patterns
User: "CCW-issue"
→ Guided template generation for bugs, features, or questions
```
---
## 🚀 Getting Started
The best way to get started is to follow the 5-minute tutorial in the [**Getting Started Guide**](GETTING_STARTED.md).
@@ -103,4 +131,4 @@ Here is a quick example of a common development workflow:
## 📄 License
This project is licensed under the **MIT License**. See the [LICENSE](LICENSE) file for details.
This project is licensed under the **MIT License**. See the [LICENSE](LICENSE) file for details.

View File

@@ -2,7 +2,7 @@
<div align="center">
[![Version](https://img.shields.io/badge/version-v5.2.0-blue.svg)](https://github.com/catlog22/Claude-Code-Workflow/releases)
[![Version](https://img.shields.io/badge/version-v5.5.0-blue.svg)](https://github.com/catlog22/Claude-Code-Workflow/releases)
[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
[![Platform](https://img.shields.io/badge/platform-Windows%20%7C%20Linux%20%7C%20macOS-lightgrey.svg)]()
@@ -14,13 +14,13 @@
**Claude Code Workflow (CCW)** 将 AI 开发从简单的提示词链接转变为一个强大的、上下文优先的编排系统。它通过结构化规划、确定性执行和智能多模型编排,解决了执行不确定性和误差累积的问题。
> **🎉 版本 5.2: 内存命令增强**
> **🎉 版本 5.5: 交互式命令指南与增强文档**
>
> **核心改进**:
> - **批量处理** - 单个 Level 1 任务处理所有模块树(减少 67% 任务)
> - **双执行模式** - 支持 Agent 模式和 CLI 模式(--cli-execute
> - **预计算分析** - 统一分析消除冗余 CLI 调用(减少 67%
> - **性能提升** - 文件读取减少 67%,总任务数减少 33%
> - **命令指南技能** - 交互式帮助系统,支持 CCW-help 和 CCW-issue 触发
> - **增强命令描述** - 所有 69 个命令更新了详细功能描述
> - **5 索引命令系统** - 按分类、使用场景、关系和核心命令组织
> - **智能推荐** - 基于上下文的工作流引导建议
>
> 详见 [CHANGELOG.md](CHANGELOG.md)。
@@ -74,6 +74,34 @@ CCW 提供了一套丰富的命令,用于管理工作流、任务以及与 AI
---
### 💡 **需要帮助?使用交互式命令指南**
CCW 包含内置的**命令指南技能**,帮助您有效地发现和使用命令:
- **`CCW-help`** - 获取交互式帮助和命令推荐
- **`CCW-issue`** - 使用引导模板报告错误或请求功能
命令指南提供:
- 🔍 **智能命令搜索** - 按关键词、分类或使用场景查找命令
- 🤖 **下一步推荐** - 获取任何命令之后的操作建议
- 📖 **详细文档** - 查看参数、示例和最佳实践
- 🎓 **新手入门** - 通过引导式学习路径学习 14 个核心命令
- 📝 **问题报告** - 生成标准化的错误报告和功能请求
**使用示例**:
```
用户: "CCW-help"
→ 交互式菜单,包含命令搜索、推荐和文档
用户: "执行完 /workflow:plan 后做什么?"
→ 推荐 /workflow:execute、/workflow:action-plan-verify 及工作流模式
用户: "CCW-issue"
→ 引导式模板生成,用于错误、功能或问题咨询
```
---
## 🚀 快速入门
开始使用的最佳方式是遵循 [**快速上手指南**](GETTING_STARTED_CN.md) 中的 5 分钟教程。