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

Files

catlog22 5b80c9c242 feat: Streamline agents to pure executor roles with enhanced workflow architecture

## Agent Streamlining
- **code-developer.md**: Reduce from 315 to 122 lines - pure code execution focus
- **action-planning-agent.md**: Reduce from 502 to 124 lines - pure planning execution
- Remove complex decision logic - commands layer now handles control flow
- Add clean code rules: minimize debug output, GBK compatibility, ASCII-only

## Workflow Architecture Enhancements
- Enhanced workflow-architecture.md with progressive complexity system
- Clear separation: Commands (control) → Agents (execution) → Output
- Improved task decomposition and TODO_LIST.md examples
- Added Gemini CLI standards references

## Command System Updates
- Updated task and workflow commands with enhanced functionality
- Better integration with streamlined agents
- Improved error handling and user experience

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

Co-Authored-By: Claude <noreply@anthropic.com>

2025-09-10 21:41:58 +08:00

4.9 KiB

Raw Blame History

name: plan description: Create implementation plans with intelligent input detection usage: /workflow:plan argument-hint: "text description"|file.md|ISS-001|template-name examples: - /workflow:plan "Build authentication system" - /workflow:plan requirements.md - /workflow:plan ISS-001 - /workflow:plan web-api

Workflow Plan Command (/workflow:plan)

Overview

Creates actionable implementation plans with intelligent input source detection. Supports text, files, issues, and templates through automatic recognition.

Core Principles

File Structure: @~/.claude/workflows/workflow-architecture.md

Usage

/workflow/plan <input>

Input Detection Logic

The command automatically detects input type:

File Input (Auto-detected)

/workflow:plan requirements.md
/workflow:plan PROJECT_SPEC.txt
/workflow:plan config.json
/workflow:plan spec.yaml

Triggers: Extensions: .md, .txt, .json, .yaml, .yml Processing: Reads file contents and extracts requirements

Issue Input (Auto-detected)

/workflow:plan ISS-001
/workflow:plan ISSUE-123
/workflow:plan feature-request-45

Triggers: Patterns: ISS-, ISSUE-, -request- Processing: Loads issue data and acceptance criteria

Template Input (Auto-detected)

/workflow:plan web-api
/workflow:plan mobile-app
/workflow:plan database-migration
/workflow:plan security-feature

Triggers: Known template names Processing: Loads template and prompts for customization

Text Input (Default)

/workflow:plan "Build user authentication with JWT and OAuth2"
/workflow:plan "Fix performance issues in dashboard"

Triggers: Everything else Processing: Parse natural language requirements

Automatic Behaviors

Session Management

Creates new session if none exists
Uses active session if available
Generates session ID: WFS-[topic-slug]

Complexity Detection

Simple: <5 tasks → Direct IMPL_PLAN.md
Medium: 5-15 tasks → IMPL_PLAN.md + TODO_LIST.md
Complex: >15 tasks → Full decomposition

Task Generation

Automatically creates .task/ files when complexity warrants
Generates hierarchical task structure (max 3 levels)
Updates session state with task references

Implementation Field Requirements

⚠️ CRITICAL: All generated tasks must include detailed implementation guidance

Auto-fill Strategy:

Sufficient Information: Auto-fill implementation field based on user input and project context

Insufficient Information: Mark analysis_source as "gemini" and prompt:

⚠️ Implementation details incomplete, recommend using gemini analysis:
gemini --all-files -p "@{relevant-file-patterns} @{CLAUDE.md} 
Analyze task: [task description]
Extract: 1) File locations and code snippets 2) Modification logic and data flow 3) Risks and dependencies"

Required Implementation Sub-fields:

files: Must contain at least 1 file with detailed info (path, location, original_code, modifications)
context_notes: Dependencies, risks, performance considerations
analysis_source: manual|gemini|auto-detected

Quality Standards:

logic_flow must use specified symbols (───►, ◊───, ◄───)
Each file must have specific location (function name or line range)
risks array cannot be empty, must contain at least 1 risk assessment

Session Check Process

⚠️ CRITICAL: Check for existing active session before planning

Check Active Session: Check for .workflow/.active-* marker file
Session Selection: Use existing active session or create new
Context Integration: Load session state and existing context

Output Documents

IMPL_PLAN.md (Always Created)

# Implementation Plan - [Project Name]
*Generated from: [input_source]*

## Requirements
[Extracted requirements from input source]

## Task Breakdown
- **IMPL-001**: [Task description]
- **IMPL-002**: [Task description]

## Success Criteria
[Measurable completion conditions]

Optional TODO_LIST.md (Auto-triggered)

Created when complexity > simple or task count > 5

Task JSON Files (Auto-created)

Generated in .task/ directory when decomposition enabled

Error Handling

Input Processing Errors

File not found: Clear error message with suggestions
Invalid issue: Verify issue ID exists
Unknown template: List available templates
Empty input: Prompt for valid input

Integration Points

/workflow:session:start - Create new session first
/context - View generated plan
/task/execute - Execute decomposed tasks
/workflow:execute - Run implementation phase

Template System

Available templates:

web-api: REST API development
mobile-app: Mobile application
database-migration: Database changes
security-feature: Security implementation

System ensures: Unified planning interface with intelligent input detection and automatic complexity handling

4.9 KiB Raw Blame History