mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-10 02:24:35 +08:00

Files

catlog22 2c3e04b6fc 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>

2025-09-09 15:06:06 +08:00

1.9 KiB

Raw Blame History

name, description, usage, examples

name

description

usage

examples

start

Start a new workflow session

/workflow:session:start "task description"

/workflow:session:start "implement OAuth2 authentication"

/workflow:session:start "fix login bug"

Start Workflow Session (/workflow:session:start)

Purpose

Initialize a new workflow session for the given task description.

Usage

/workflow/session/start "task description"

Automatic Behaviors

Session Creation

Generates unique session ID: WFS-[topic-slug]
Creates .workflow/.active-[session-name] marker file
Deactivates any existing active session

Complexity Detection

Automatically determines complexity based on task description:

Simple: Single module, <5 tasks
Medium: Multiple modules, 5-15 tasks
Complex: Large scope, >15 tasks

Directory Structure

Creates session directory with:

.workflow/WFS-[topic-slug]/
├── workflow-session.json    # Session metadata
├── IMPL_PLAN.md            # Initial planning template
├── .task/                  # Task management
└── reports/                # Report generation

Phase Initialization

Simple: Ready for direct implementation
Medium/Complex: Ready for planning phase

Session State

Creates workflow-session.json with:

Session ID and description
Current phase: INIT → PLAN
Document tracking
Task system configuration
Active marker reference

Next Steps

After starting a session:

Use /workflow/plan to create implementation plan
Use /workflow/execute to begin implementation
Use /context to view session status

Error Handling

Duplicate session: Warns if similar session exists
Invalid description: Prompts for valid task description
Directory conflicts: Handles existing directories gracefully

Creates: New active workflow session ready for planning and execution

1.9 KiB Raw Blame History