Skip to content
ย 
ย 

Latest commit

ย 

History

6 Commits

Folders and files

NameName
Last commit message
Last commit date
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Claude Code Multi-Agent Workflow System

License: MIT Claude Code

Transform your development workflow from manual command chains to automated expert teams with 95% quality assurance.

๐Ÿš€ From Manual Commands to Automated Workflows

Before: Manual command chains requiring constant oversight

/ask โ†’ /code โ†’ /test โ†’ /review โ†’ /optimize
# 1-2 hours of manual orchestration, context pollution, quality uncertainty

After: One-command automated expert workflows

/requirements-pilot "Implement JWT user authentication system"
# 30 minutes of automated execution, 90% quality gates, zero manual intervention

๐ŸŽฏ Core Value Proposition

This repository provides a meta-framework for Claude Code that implements:

  • ๐Ÿค– Multi-Agent Orchestration: Specialized AI teams working in parallel
  • โšก Quality Gate Automation: 95% threshold with automatic optimization loops
  • ๐Ÿ”„ Workflow Automation: From requirements to production-ready code
  • ๐Ÿ“Š Context Isolation: Each agent maintains focused expertise without pollution

๐Ÿ“‹ Two Primary Usage Patterns

1. ๐Ÿญ Requirements-Driven Workflow (Automated Expert Teams)

Architecture: Requirements-focused workflow with quality gates

requirements-generate โ†’ requirements-code โ†’ requirements-review โ†’ (โ‰ฅ90%?) โ†’ requirements-testing
         โ†‘                                              โ†“ (<90%)
         โ†โ†โ†โ†โ†โ† Automatic optimization loop โ†โ†โ†โ†โ†โ†

Usage:

# Complete development workflow in one command
/requirements-pilot "Build user management system with RBAC"

# Advanced multi-stage workflow
First use requirements-generate, then requirements-code, then requirements-review, 
then if score โ‰ฅ90% use requirements-testing

Quality Scoring (Total 100%):

  • Functionality (40%)
  • Integration (25%)
  • Code Quality (20%)
  • Performance (15%)

2. ๐ŸŽ›๏ธ Custom Commands (Manual Orchestration)

Architecture: Individual slash commands for targeted expertise

/ask     # Technical consultation and architecture guidance
/spec    # Interactive requirements โ†’ design โ†’ tasks workflow  
/code    # Feature implementation with constraints
/debug   # Systematic problem analysis using UltraThink
/test    # Comprehensive testing strategy
/review  # Multi-dimensional code validation
/optimize # Performance optimization coordination

Progression Example:

# Step-by-step development with manual control
/ask "Help me understand microservices architecture requirements"
/spec "Generate API gateway specifications" 
/code "Implement gateway with rate limiting"
/test "Create load testing suite"
/review "Validate security and performance"

๐Ÿš€ Quick Start

1. Setup Configuration

Clone or copy the configuration structure:

# Your project directory
โ”œโ”€โ”€ commands/          # 12 specialized slash commands
โ”œโ”€โ”€ agents/           # 7 expert agent configurations  
โ””โ”€โ”€ CLAUDE.md         # Project-specific guidelines

2. Basic Usage

Complete Feature Development:

/spec-workflow "Implement OAuth2 authentication with refresh tokens"

Manual Development Flow:

/ask "Design principles for scalable microservices"
/spec "OAuth2 service specifications"
/code "Implement OAuth2 with security best practices"

3. Expected Outputs

Automated Workflow Results:

  • โœ… Requirements confirmation with 90+ quality score
  • โœ… Implementation-ready technical specifications
  • โœ… Production-ready code with best practices
  • โœ… Comprehensive test suite (unit + integration + functional)
  • โœ… 90%+ quality validation score

๐Ÿ—๏ธ Architecture Overview

Core Components

Commands Directory (/commands/)

  • Specification: /spec - Interactive requirements โ†’ design โ†’ tasks
  • Consultation: /ask - Architecture guidance (no code changes)
  • Implementation: /code - Feature development with constraints
  • Quality Assurance: /test, /review, /debug
  • Optimization: /optimize, /refactor
  • Operations: /deploy-check, /cicd

Agents Directory (/agents/)

  • requirements-generate: Technical specification generation optimized for code generation
  • requirements-code: Direct implementation agent with minimal architectural overhead
  • requirements-review: Pragmatic code review focused on functionality and maintainability
  • requirements-testing: Practical testing agent focused on functional validation
  • bugfix: Bug resolution specialist for analyzing and fixing software defects
  • bugfix-verify: Fix validation specialist for objective assessment
  • code: Development coordinator for direct implementation
  • debug: UltraThink systematic problem analysis
  • optimize: Performance optimization coordination

Multi-Agent Coordination System

4 Core Specialists:

  1. Requirements Generator - Implementation-ready technical specifications
  2. Code Implementer - Direct, pragmatic code implementation
  3. Quality Reviewer - Practical quality review with scoring
  4. Test Coordinator - Functional validation and testing

Key Features:

  • Implementation-First Approach: Direct technical specs for code generation
  • Quality Gates: 90% threshold for automatic progression
  • Iterative Improvement: Automatic optimization loops
  • Practical Focus: Working solutions over architectural perfection

๐Ÿ“š Workflow Examples

Enterprise User Authentication System

Input:

/requirements-pilot "Enterprise JWT authentication with RBAC, supporting 500 concurrent users, integrated with existing LDAP"

Automated Process:

  1. Requirements Confirmation (Quality: 92/100) - Interactive clarification

    • Functional clarity, technical specificity, implementation completeness
    • Decision: โ‰ฅ90%, proceed with implementation
  2. Round 1 (Quality: 83/100) - Basic implementation

    • Issues: Error handling incomplete, integration concerns
    • Decision: <90%, restart with improvements
  3. Round 2 (Quality: 93/100) - Production ready

    • Decision: โ‰ฅ90%, proceed to functional testing

Final Deliverables:

  • Requirements confirmation with quality assessment
  • Implementation-ready technical specifications
  • Pragmatic JWT implementation with RBAC
  • LDAP integration with proper error handling
  • Functional test suite focusing on critical paths

API Gateway Development

Input:

/ask "Design considerations for high-performance API gateway"
# (Interactive consultation phase)

/spec "Microservices API gateway with rate limiting and circuit breakers"
# (Specification generation)

/code "Implement gateway based on specifications"
# (Implementation phase)

Results:

  • Architectural consultation on performance patterns
  • Detailed specifications with load balancing strategy
  • Production-ready implementation with monitoring

๐Ÿ”ง Advanced Usage Patterns

Custom Workflow Composition

# Debug โ†’ Fix โ†’ Validate workflow
First use debug to analyze [performance issue], 
then use code to implement fixes, 
then use spec-validation to ensure quality

# Complete development + optimization pipeline  
First use spec-generation for [feature], 
then spec-executor for implementation,
then spec-validation for quality check,
then if score โ‰ฅ95% use spec-testing,
finally use optimize for production readiness

Quality-Driven Development

# Iterative quality improvement
First use spec-validation to score [existing code],
then if score <95% use code to improve based on feedback,
repeat until quality threshold achieved

๐ŸŽฏ Benefits & Impact

Dimension Manual Commands Sub-Agent Workflows
Complexity Manual trigger for each step One-command full pipeline
Quality Subjective assessment 90% objective scoring
Context Pollution, requires /clear Isolated, no pollution
Expertise AI role switching Focused specialists
Error Handling Manual discovery/fix Automatic optimization
Time Investment 1-2 hours manual work 30 minutes automated

๐Ÿ”ฎ Key Innovations

1. Specialist Depth Over Generalist Breadth

Each agent focuses on their domain expertise in independent contexts, avoiding the quality degradation of role-switching.

2. Intelligent Quality Gates

90% objective scoring with automatic decision-making for workflow progression or optimization loops.

3. Complete Automation

One command triggers end-to-end development workflow with minimal human intervention.

4. Continuous Improvement

Quality feedback drives automatic specification refinement, creating intelligent improvement cycles.

๐Ÿ› ๏ธ Configuration

Setting Up Sub-Agents

  1. Create Agent Configurations: Copy agent files to your Claude Code configuration
  2. Configure Commands: Set up workflow trigger commands
  3. Customize Quality Gates: Adjust scoring thresholds if needed

Workflow Customization

# Custom workflow with specific quality requirements
First use requirements-generate with [strict security requirements],
then requirements-code with [performance constraints],
then requirements-review with [90% minimum threshold],
continue optimization until threshold met

๐Ÿ“– Command Reference

Requirements Workflow

  • /requirements-pilot - Complete requirements-driven development workflow
  • Interactive requirements confirmation โ†’ technical specifications โ†’ implementation โ†’ testing

Development Commands

  • /ask - Architecture consultation (no code changes)
  • /code - Feature implementation with constraints
  • /debug - Systematic problem analysis
  • /test - Comprehensive testing strategy
  • /review - Multi-dimensional code validation

Optimization Commands

  • /optimize - Performance optimization coordination
  • /refactor - Code refactoring with quality gates
  • /deploy-check - Deployment readiness validation

๐Ÿค Contributing

This is a Claude Code configuration framework. Contributions welcome:

  1. New Agent Configurations: Specialized experts for specific domains
  2. Workflow Patterns: New automation sequences
  3. Quality Metrics: Enhanced scoring dimensions
  4. Command Extensions: Additional development phase coverage

๐Ÿ“„ License

MIT License - see LICENSE file for details.

๐Ÿ™‹ Support

  • Documentation: Check /commands/ and /agents/ for detailed specifications
  • Issues: Use GitHub issues for bug reports and feature requests
  • Discussions: Share workflow patterns and customizations

๐ŸŽ‰ Getting Started

Ready to transform your development workflow? Start with:

/requirements-pilot "Your first feature description here"

Watch as your one-line request becomes a complete, tested, production-ready implementation with 90% quality assurance.

Remember: Professional software comes from professional processes. Requirements-driven workflows give you a tireless, always-expert virtual development team.

Let specialized AI do specialized work - development becomes elegant and efficient.

About

Cladue Code Auto Workflow

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors