mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-11 02:33:51 +08:00
refactor: Standardize command naming conventions and remove parent relationships
Updates all command files to use consistent naming without parent field: - Remove parent field from all command frontmatter - Standardize name field to use simple names instead of prefixed names - Fix usage patterns for brainstorm commands to use proper workflow namespace - Add new medium-project-update.sh script for batch updates 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:business-analyst
|
||||
name: business-analyst
|
||||
description: Business analyst perspective brainstorming for process optimization and business efficiency analysis
|
||||
usage: /brainstorm:business-analyst <topic>
|
||||
usage: /workflow:brainstorm:business-analyst <topic>
|
||||
argument-hint: "topic or challenge to analyze from business analysis perspective"
|
||||
examples:
|
||||
- /brainstorm:business-analyst "workflow automation opportunities"
|
||||
- /brainstorm:business-analyst "business process optimization"
|
||||
- /brainstorm:business-analyst "cost reduction initiatives"
|
||||
- /workflow:brainstorm:business-analyst "workflow automation opportunities"
|
||||
- /workflow:brainstorm:business-analyst "business process optimization"
|
||||
- /workflow:brainstorm:business-analyst "cost reduction initiatives"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:data-architect
|
||||
name: data-architect
|
||||
description: Data architect perspective brainstorming for data modeling, flow, and analytics analysis
|
||||
usage: /brainstorm:data-architect <topic>
|
||||
usage: /workflow:brainstorm:data-architect <topic>
|
||||
argument-hint: "topic or challenge to analyze from data architecture perspective"
|
||||
examples:
|
||||
- /brainstorm:data-architect "user analytics data pipeline"
|
||||
- /brainstorm:data-architect "real-time data processing system"
|
||||
- /brainstorm:data-architect "data warehouse modernization"
|
||||
- /workflow:brainstorm:data-architect "user analytics data pipeline"
|
||||
- /workflow:brainstorm:data-architect "real-time data processing system"
|
||||
- /workflow:brainstorm:data-architect "data warehouse modernization"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:feature-planner
|
||||
name: planner
|
||||
description: Feature planner perspective brainstorming for feature development and planning analysis
|
||||
usage: /brainstorm:feature-planner <topic>
|
||||
usage: /workflow:brainstorm:feature-planner <topic>
|
||||
argument-hint: "topic or challenge to analyze from feature planning perspective"
|
||||
examples:
|
||||
- /brainstorm:feature-planner "user dashboard enhancement"
|
||||
- /brainstorm:feature-planner "mobile app feature roadmap"
|
||||
- /brainstorm:feature-planner "integration capabilities planning"
|
||||
- /workflow:brainstorm:feature-planner "user dashboard enhancement"
|
||||
- /workflow:brainstorm:feature-planner "mobile app feature roadmap"
|
||||
- /workflow:brainstorm:feature-planner "integration capabilities planning"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:innovation-lead
|
||||
name: innovation-lead
|
||||
description: Innovation lead perspective brainstorming for emerging technologies and future opportunities analysis
|
||||
usage: /brainstorm:innovation-lead <topic>
|
||||
usage: /workflow:brainstorm:innovation-lead <topic>
|
||||
argument-hint: "topic or challenge to analyze from innovation and emerging technology perspective"
|
||||
examples:
|
||||
- /brainstorm:innovation-lead "AI integration opportunities"
|
||||
- /brainstorm:innovation-lead "future technology trends"
|
||||
- /brainstorm:innovation-lead "disruptive innovation strategy"
|
||||
- /workflow:brainstorm:innovation-lead "AI integration opportunities"
|
||||
- /workflow:brainstorm:innovation-lead "future technology trends"
|
||||
- /workflow:brainstorm:innovation-lead "disruptive innovation strategy"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:product-manager
|
||||
name: product-manager
|
||||
description: Product manager perspective brainstorming for user needs and business value analysis
|
||||
usage: /brainstorm:product-manager <topic>
|
||||
usage: /workflow:brainstorm:product-manager <topic>
|
||||
argument-hint: "topic or challenge to analyze from product management perspective"
|
||||
examples:
|
||||
- /brainstorm:product-manager "user authentication redesign"
|
||||
- /brainstorm:product-manager "mobile app performance optimization"
|
||||
- /brainstorm:product-manager "feature prioritization strategy"
|
||||
- /workflow:brainstorm:product-manager "user authentication redesign"
|
||||
- /workflow:brainstorm:product-manager "mobile app performance optimization"
|
||||
- /workflow:brainstorm:product-manager "feature prioritization strategy"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:security-expert
|
||||
name: security-expert
|
||||
description: Security expert perspective brainstorming for threat modeling and security architecture analysis
|
||||
usage: /brainstorm:security-expert <topic>
|
||||
usage: /workflow:brainstorm:security-expert <topic>
|
||||
argument-hint: "topic or challenge to analyze from cybersecurity perspective"
|
||||
examples:
|
||||
- /brainstorm:security-expert "user authentication security review"
|
||||
- /brainstorm:security-expert "API security architecture"
|
||||
- /brainstorm:security-expert "data protection compliance strategy"
|
||||
- /workflow:brainstorm:security-expert "user authentication security review"
|
||||
- /workflow:brainstorm:security-expert "API security architecture"
|
||||
- /workflow:brainstorm:security-expert "data protection compliance strategy"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
name: brainstorm:synthesis
|
||||
name: synthesis
|
||||
description: Synthesize all brainstorming role perspectives into comprehensive analysis and recommendations
|
||||
usage: /brainstorm:synthesis
|
||||
usage: /workflow:brainstorm:synthesis
|
||||
argument-hint: "no arguments required - analyzes existing brainstorming session outputs"
|
||||
examples:
|
||||
- /brainstorm:synthesis
|
||||
- /workflow:brainstorm:synthesis
|
||||
allowed-tools: Read(*), Write(*), TodoWrite(*), Glob(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:system-architect
|
||||
name: system-architect
|
||||
description: System architect perspective brainstorming for technical architecture and scalability analysis
|
||||
usage: /brainstorm:system-architect <topic>
|
||||
usage: /workflow:brainstorm:system-architect <topic>
|
||||
argument-hint: "topic or challenge to analyze from system architecture perspective"
|
||||
examples:
|
||||
- /brainstorm:system-architect "user authentication redesign"
|
||||
- /brainstorm:system-architect "microservices migration strategy"
|
||||
- /brainstorm:system-architect "system performance optimization"
|
||||
- /workflow:brainstorm:system-architect "user authentication redesign"
|
||||
- /workflow:brainstorm:system-architect "microservices migration strategy"
|
||||
- /workflow:brainstorm:system-architect "system performance optimization"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:ui-designer
|
||||
name: ui-designer
|
||||
description: UI designer perspective brainstorming for user experience and interface design analysis
|
||||
usage: /brainstorm:ui-designer <topic>
|
||||
usage: /workflow:brainstorm:ui-designer <topic>
|
||||
argument-hint: "topic or challenge to analyze from UI/UX design perspective"
|
||||
examples:
|
||||
- /brainstorm:ui-designer "user authentication redesign"
|
||||
- /brainstorm:ui-designer "mobile app navigation improvement"
|
||||
- /brainstorm:ui-designer "accessibility enhancement strategy"
|
||||
- /workflow:brainstorm:ui-designer "user authentication redesign"
|
||||
- /workflow:brainstorm:ui-designer "mobile app navigation improvement"
|
||||
- /workflow:brainstorm:ui-designer "accessibility enhancement strategy"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
name: brainstorm:user-researcher
|
||||
name: user-researcher
|
||||
description: User researcher perspective brainstorming for user behavior analysis and research insights
|
||||
usage: /brainstorm:user-researcher <topic>
|
||||
usage: /workflow:brainstorm:user-researcher <topic>
|
||||
argument-hint: "topic or challenge to analyze from user research perspective"
|
||||
examples:
|
||||
- /brainstorm:user-researcher "user onboarding experience"
|
||||
- /brainstorm:user-researcher "mobile app usability issues"
|
||||
- /brainstorm:user-researcher "feature adoption analysis"
|
||||
- /workflow:brainstorm:user-researcher "user onboarding experience"
|
||||
- /workflow:brainstorm:user-researcher "mobile app usability issues"
|
||||
- /workflow:brainstorm:user-researcher "feature adoption analysis"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: workflow-execute
|
||||
name: execute
|
||||
description: Coordinate agents for existing workflow tasks with automatic discovery
|
||||
usage: /workflow:execute
|
||||
argument-hint: none
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-issue-close
|
||||
name: close
|
||||
description: Close a completed or obsolete workflow issue
|
||||
usage: /workflow:issue:close <issue-id> [reason]
|
||||
parent: /workflow:issue
|
||||
|
||||
examples:
|
||||
- /workflow:issue:close ISS-001
|
||||
- /workflow:issue:close ISS-001 "Feature implemented in PR #42"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-issue-create
|
||||
name: create
|
||||
description: Create a new issue or change request
|
||||
usage: /workflow:issue:create "issue description"
|
||||
parent: /workflow:issue
|
||||
|
||||
examples:
|
||||
- /workflow:issue:create "Add OAuth2 social login support"
|
||||
- /workflow:issue:create "Fix user avatar security vulnerability"
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
---
|
||||
name: workflow-issue-list
|
||||
name: list
|
||||
description: List and filter workflow issues
|
||||
usage: /workflow:issue:list
|
||||
parent: /workflow:issue
|
||||
examples:
|
||||
- /workflow:issue:list
|
||||
- /workflow:issue:list --open
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-issue-update
|
||||
name: update
|
||||
description: Update an existing workflow issue
|
||||
usage: /workflow:issue:update <issue-id> [changes]
|
||||
parent: /workflow:issue
|
||||
|
||||
examples:
|
||||
- /workflow:issue:update ISS-001
|
||||
- /workflow:issue:update ISS-001 --priority=critical
|
||||
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
name: workflow-plan-deep
|
||||
name: plan-deep
|
||||
description: Deep technical planning with Gemini CLI analysis and action-planning-agent
|
||||
usage: /workflow:plan:deep <task_description>
|
||||
usage: /workflow:plan-deep <task_description>
|
||||
argument-hint: "task description" | requirements.md
|
||||
examples:
|
||||
- /workflow:plan:deep "Refactor authentication system to use JWT"
|
||||
- /workflow:plan:deep "Implement real-time notifications across modules"
|
||||
- /workflow:plan:deep requirements.md
|
||||
- /workflow:plan-deep "Refactor authentication system to use JWT"
|
||||
- /workflow:plan-deep "Implement real-time notifications across modules"
|
||||
- /workflow:plan-deep requirements.md
|
||||
---
|
||||
|
||||
# Workflow Plan Deep Command (/workflow:plan:deep)
|
||||
# Workflow Plan Deep Command (/workflow:plan-deep)
|
||||
|
||||
## Overview
|
||||
Creates comprehensive implementation plans through deep codebase analysis using Gemini CLI and the action-planning-agent. This command enforces multi-dimensional context gathering before planning, ensuring technical decisions are grounded in actual codebase understanding.
|
||||
@@ -17,7 +17,7 @@ Creates comprehensive implementation plans through deep codebase analysis using
|
||||
## Key Differentiators
|
||||
|
||||
### vs /workflow:plan
|
||||
| Feature | /workflow:plan | /workflow:plan:deep |
|
||||
| Feature | /workflow:plan | /workflow:plan-deep |
|
||||
|---------|---------------|-------------------|
|
||||
| **Analysis Depth** | Basic requirements extraction | Deep codebase analysis |
|
||||
| **Gemini CLI** | Optional | **Mandatory (via agent)** |
|
||||
@@ -175,7 +175,7 @@ def process_plan_deep_command(input):
|
||||
|
||||
### Example 1: Cross-Module Refactoring
|
||||
```bash
|
||||
/workflow:plan:deep "Refactor user authentication to use JWT tokens across all services"
|
||||
/workflow:plan-deep "Refactor user authentication to use JWT tokens across all services"
|
||||
```
|
||||
Generates comprehensive plan analyzing:
|
||||
- Current auth implementation
|
||||
@@ -185,7 +185,7 @@ Generates comprehensive plan analyzing:
|
||||
|
||||
### Example 2: Performance Optimization
|
||||
```bash
|
||||
/workflow:plan:deep "Optimize database query performance in reporting module"
|
||||
/workflow:plan-deep "Optimize database query performance in reporting module"
|
||||
```
|
||||
Creates detailed plan including:
|
||||
- Current query patterns analysis
|
||||
@@ -195,7 +195,7 @@ Creates detailed plan including:
|
||||
|
||||
### Example 3: Architecture Enhancement
|
||||
```bash
|
||||
/workflow:plan:deep "Implement event-driven architecture for order processing"
|
||||
/workflow:plan-deep "Implement event-driven architecture for order processing"
|
||||
```
|
||||
Produces hierarchical plan with:
|
||||
- Current architecture assessment
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: workflow-plan
|
||||
name: plan
|
||||
description: Create implementation plans with intelligent input detection
|
||||
usage: /workflow:plan <input>
|
||||
argument-hint: "text description"|file.md|ISS-001|template-name
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: workflow-review
|
||||
name: review
|
||||
description: Execute review phase for quality validation
|
||||
usage: /workflow:review
|
||||
argument-hint: none
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-list
|
||||
name: list
|
||||
description: List all workflow sessions with status
|
||||
usage: /workflow:session:list
|
||||
parent: /workflow:session
|
||||
|
||||
---
|
||||
|
||||
# List Workflow Sessions (/workflow/session/list)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-pause
|
||||
name: pause
|
||||
description: Pause the active workflow session
|
||||
usage: /workflow:session:pause
|
||||
parent: /workflow:session
|
||||
|
||||
---
|
||||
|
||||
# Pause Workflow Session (/workflow:session:pause)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-resume
|
||||
name: resume
|
||||
description: Resume the most recently paused workflow session
|
||||
usage: /workflow:session:resume
|
||||
parent: /workflow:session
|
||||
|
||||
---
|
||||
|
||||
# Resume Workflow Session (/workflow:session:resume)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-start
|
||||
name: start
|
||||
description: Start a new workflow session
|
||||
usage: /workflow:session:start "task description"
|
||||
parent: /workflow:session
|
||||
|
||||
examples:
|
||||
- /workflow:session:start "implement OAuth2 authentication"
|
||||
- /workflow:session:start "fix login bug"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-status
|
||||
name: status
|
||||
description: Show detailed status of active workflow session
|
||||
usage: /workflow:session:status
|
||||
parent: /workflow:session
|
||||
|
||||
---
|
||||
|
||||
# Workflow Session Status (/workflow:session:status)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: workflow-session-switch
|
||||
name: switch
|
||||
description: Switch to a different workflow session
|
||||
usage: /workflow:session:switch <session-id>
|
||||
parent: /workflow:session
|
||||
|
||||
examples:
|
||||
- /workflow:session:switch WFS-oauth-integration
|
||||
- /workflow:session:switch WFS-user-profile
|
||||
|
||||
Reference in New Issue
Block a user