{"id":30717791,"url":"https://github.com/jakeashcraft/claude-sub-agent-workflow","last_synced_at":"2025-09-03T09:04:07.671Z","repository":{"id":312672323,"uuid":"1048273405","full_name":"jakeashcraft/claude-sub-agent-workflow","owner":"jakeashcraft","description":"A comprehensive context-aware AI-driven development workflow system built on Claude Code's Sub-Agents feature, specifically designed for manufacturing industry applications.","archived":false,"fork":false,"pushed_at":"2025-09-01T08:13:06.000Z","size":181,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"master","last_synced_at":"2025-09-01T10:42:53.421Z","etag":null,"topics":["ai-driven-development","azure-deployment","claude-code","clean-architecture","dotnet-9","manufacturing","sub-agents","workflow-automation"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/jakeashcraft.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2025-09-01T07:38:24.000Z","updated_at":"2025-09-01T08:13:09.000Z","dependencies_parsed_at":"2025-09-01T10:42:55.147Z","dependency_job_id":"0d8d5bca-a8fd-4901-9486-db546aef6c72","html_url":"https://github.com/jakeashcraft/claude-sub-agent-workflow","commit_stats":null,"previous_names":["jakeashcraft/claude-sub-agent-workflow"],"tags_count":null,"template":false,"template_full_name":null,"purl":"pkg:github/jakeashcraft/claude-sub-agent-workflow","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jakeashcraft%2Fclaude-sub-agent-workflow","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jakeashcraft%2Fclaude-sub-agent-workflow/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jakeashcraft%2Fclaude-sub-agent-workflow/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jakeashcraft%2Fclaude-sub-agent-workflow/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/jakeashcraft","download_url":"https://codeload.github.com/jakeashcraft/claude-sub-agent-workflow/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jakeashcraft%2Fclaude-sub-agent-workflow/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":273417342,"owners_count":25101817,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-09-03T02:00:09.631Z","response_time":76,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ai-driven-development","azure-deployment","claude-code","clean-architecture","dotnet-9","manufacturing","sub-agents","workflow-automation"],"created_at":"2025-09-03T09:02:05.414Z","updated_at":"2025-09-03T09:04:07.655Z","avatar_url":"https://github.com/jakeashcraft.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Claude Sub-Agent Spec Workflow System\n\n[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)\n[![.NET 9](https://img.shields.io/badge/.NET-9-purple.svg)](https://dotnet.microsoft.com/)\n[![Claude Code](https://img.shields.io/badge/Claude%20Code-Sub--Agents-green.svg)](https://docs.anthropic.com/en/docs/claude-code/sub-agents)\n[![Manufacturing](https://img.shields.io/badge/Industry-Manufacturing-orange.svg)](https://github.com/jakeashcraft/claude-sub-agent)\n[![Azure](https://img.shields.io/badge/Cloud-Azure-blue.svg)](https://azure.microsoft.com/)\n[![Clean Architecture](https://img.shields.io/badge/Architecture-Clean-lightblue.svg)](https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html)\n\nA comprehensive context-aware AI-driven development workflow system built on Claude Code's Sub-Agents feature, specifically designed for **manufacturing industry applications**. This system transforms manufacturing project ideas into production-ready .NET 9 applications through specialized AI agents working in coordinated phases with intelligent iteration management, optimized for compliance, integration, and multi-facility deployment scenarios.\n\n## ⭐ Why This Workflow System?\n\n- **🏭 Manufacturing-First Design**: Built specifically for manufacturing software requirements\n- **🧠 Context-Aware Intelligence**: Reads existing project state to avoid unnecessary regeneration  \n- **⚡ 70% Token Reduction**: Intelligent agent selection for iterative development\n- **📁 Organized Documentation**: Structured hierarchy prevents document chaos\n- **🛡️ Compliance Ready**: Built-in FDA, HACCP, and ISO compliance patterns\n- **🔗 Integration Patterns**: Ready-to-use MES, SCADA, and ERP integration\n- **☁️ Azure-Optimized**: Production-ready Azure deployment configurations\n\n## Table of Contents\n\n- [Overview](#overview)\n- [System Architecture](#system-architecture)\n- [Installation](#installation)\n- [Quick Start](#quick-start)\n- [Context-Aware Workflow](#context-aware-workflow)\n- [Documentation Organization](#documentation-organization)\n- [Agent Reference](#agent-reference)\n- [Usage Examples](#usage-examples)\n- [Quality Gates](#quality-gates)\n- [Best Practices](#best-practices)\n- [Advanced Usage](#advanced-usage)\n- [Troubleshooting](#troubleshooting)\n\n## Overview\n\nThe Spec Workflow System leverages Claude Code's Sub-Agents capability to create a context-aware, multi-agent development pipeline optimized for .NET 9 manufacturing applications. Each agent is a specialized expert that understands existing project state, manufacturing domain requirements, and compliance needs while handling specific aspects of the industrial software development lifecycle.\n\n### Key Features\n\n- **Context-Aware Workflow**: Analyzes existing project state to avoid unnecessary regeneration\n- **Request Type Classification**: Automatically determines if this is a new project, bug fix, enhancement, or refactor\n- **Manufacturing Domain Focus**: Built-in understanding of compliance, integration, and multi-facility requirements\n- **Organized Documentation**: Structured folder hierarchy prevents document chaos\n- **Token Efficiency**: Minimal token usage through intelligent agent selection\n- **Iterative Development**: Supports continuous improvement without starting from scratch\n- **.NET 9 Manufacturing Stack**: Specialized for Clean Architecture, Entity Framework Core, and Azure deployment\n- **Quality Gates**: Automated checkpoints with manufacturing-specific validation criteria\n\n### Benefits\n\n- Eliminates document chaos through organized iteration folders\n- 70% reduction in token usage for iterative development\n- Context-aware agent selection prevents unnecessary work\n- Maintains project history through versioned iterations\n- Optimized for .NET 9, Clean Architecture, and Azure deployment\n- Built-in support for manufacturing compliance standards (FDA, HACCP, ISO)\n- Specialized patterns for MES, SCADA, and ERP system integration\n- Multi-facility deployment and configuration management\n\n## System Architecture\n\n```mermaid\ngraph TD\n    A[Project Request] --\u003e B[spec-orchestrator]\n    B --\u003e C[Context Analysis]\n    C --\u003e D{Project State}\n    D --\u003e|Existing Project| E[Request Classification]\n    D --\u003e|New Project| F[Full Workflow]\n    \n    E --\u003e G{Request Type}\n    G --\u003e|Bug Fix| H[Targeted Agent Chain]\n    G --\u003e|Enhancement| I[Selective Agent Chain] \n    G --\u003e|Refactor| J[Optimization Chain]\n    G --\u003e|Major Change| F\n    \n    H --\u003e K[spec-analyst Analysis]\n    K --\u003e L[spec-developer Fixes]\n    L --\u003e M[spec-validator Regression]\n    \n    I --\u003e N[spec-analyst Updates]\n    N --\u003e O[spec-architect Conditional]\n    O --\u003e P[spec-developer Implementation]\n    \n    J --\u003e Q[spec-architect Review]\n    Q --\u003e R[spec-developer Refactor]\n    \n    F --\u003e S[Complete Agent Chain]\n    S --\u003e T[spec-analyst Requirements]\n    T --\u003e U[spec-architect Design]\n    U --\u003e V[spec-developer Implementation]\n    \n    M --\u003e W[Quality Gate]\n    P --\u003e W\n    R --\u003e W\n    V --\u003e W\n    \n    W --\u003e|Pass ≥90%| X[spec-tester]\n    W --\u003e|Fail \u003c90%| Y[Targeted Feedback]\n    \n    Y --\u003e Z[Limited Retries ≤2]\n    Z --\u003e H\n    \n    X --\u003e AA[Production Ready]\n    \n    style B fill:#1a73e8,color:#fff\n    style C fill:#34a853,color:#fff\n    style W fill:#f9ab00,color:#fff\n    style AA fill:#34a853,color:#fff\n```\n\n## Installation\n\n### Prerequisites\n\n- Claude Code (latest version with Sub-Agents support)\n- Project directory initialized\n- .NET 9 SDK (for .NET projects)\n- Basic understanding of AI-assisted development\n\n### Setup Steps\n\n1. **Download the agents**\n\n   ```bash\n   # Option 1: Clone the repository\n   git clone https://github.com/jakeashcraft/claude-sub-agent.git\n   cd claude-sub-agent\n   \n   # Option 2: Download specific agents you need\n   # Individual agent files are available in the agents/ directory\n   ```\n\n2. **Copy agents and commands to your project's Claude Code directory**\n\n   ```bash\n   # Create .claude directory structure in your project\n   mkdir -p .claude/agents .claude/commands .claude/docs\n   \n   # Copy all agents from categorized directories\n   cp -r agents/*/*.md .claude/agents/\n   \n   # Copy the enhanced workflow command\n   cp commands/agent-workflow.md .claude/commands/\n   ```\n\n3. **Initialize documentation structure**\n\n   ```bash\n   # Create organized documentation folders\n   mkdir -p docs/{project,architecture,iterations,current,archive}\n   \n   # Initialize current state tracking\n   touch docs/current/{active-tasks.md,known-issues.md,recent-changes.md}\n   ```\n\n4. **Verify installation**\n\n   **Your project structure after installation:**\n\n   ```text\n   your-project/\n   ├── .claude/\n   │   ├── commands/\n   │   │   └── agent-workflow.md      # Enhanced context-aware workflow\n   │   ├── agents/\n   │   │   ├── spec-orchestrator.md   # .NET 9 Context-aware orchestrator\n   │   │   ├── spec-analyst.md        # Requirements analyst\n   │   │   ├── spec-architect.md      # .NET 9 system architect\n   │   │   ├── spec-developer.md      # .NET 9 implementation specialist\n   │   │   ├── spec-validator.md      # .NET 9 quality validator\n   │   │   ├── spec-tester.md         # .NET 9 testing specialist\n   │   │   └── ...                    # Other specialized agents\n   │   └── docs/                      # Organized documentation structure\n   │       ├── project/               # Core project docs (stable)\n   │       ├── architecture/          # System design docs\n   │       ├── iterations/            # Version-controlled iterations\n   │       ├── current/               # Active working state\n   │       └── archive/               # Completed work\n   ├── src/                           # .NET 9 source code\n   ├── tests/                         # xUnit test projects\n   ├── CLAUDE.md                      # Enhanced project guidance\n   └── README.md                      # This file\n   ```\n\n## Quick Start\n\n### Basic Usage (Context-Aware)\n\n```bash\n# For a new project\n/agent-workflow \"Create a .NET 9 Web API for managing inventory with Clean Architecture\"\n\n# For bug fixes on existing projects\n/agent-workflow \"The user login is failing with valid credentials\"\n\n# For enhancements to existing projects\n/agent-workflow \"Add real-time notifications using SignalR to the existing application\"\n\n# For refactoring existing code\n/agent-workflow \"Refactor the data access layer to use the Repository pattern\"\n```\n\n### Simple Example with Context Awareness\n\n```markdown\nYou: /agent-workflow \"The user authentication is broken\"\n\nClaude (spec-orchestrator): Analyzing existing project state...\nFound existing documentation in docs/\nClassification: BUG_FIX workflow\nCreating iteration: v2-bugfix-20241201-1430\n\n[Context Analysis - 5 minutes]\n✓ Existing requirements analyzed\n✓ Issue classified as authentication bug\n✓ Iteration v2-bugfix created\n✓ Targeted agent chain selected\n\n[Targeted Development - 45 minutes]  \n✓ Root cause identified in JWT validation\n✓ Authentication service fixed\n✓ Regression tests added\n✓ Quality Gate: PASSED (94/100)\n\nProject updated! Changes in iteration v2-bugfix:\n- AuthenticationService.cs updated\n- New regression tests added\n- Documentation updated in current/\n- No unnecessary regeneration of existing docs\n```\n\n## Context-Aware Workflow\n\n### Request Type Classification\n\nThe system automatically analyzes your request and existing project state to determine the optimal workflow:\n\n#### NEW_PROJECT\n- **Trigger**: No existing `docs/` structure\n- **Keywords**: \"create\", \"build\", \"new project\", \"from scratch\"\n- **Agent Chain**: Full workflow (analyst → architect → developer → validator → tester)\n- **Documentation**: Complete initial documentation set\n\n#### BUG_FIX  \n- **Trigger**: Existing project + issue description\n- **Keywords**: \"bug\", \"broken\", \"not working\", \"error\", \"fails\"\n- **Agent Chain**: Targeted (analyst analysis → developer fixes → validator regression)\n- **Documentation**: Issue analysis + fix documentation in iteration folder\n\n#### ENHANCEMENT\n- **Trigger**: Existing project + new functionality\n- **Keywords**: \"add\", \"new feature\", \"enhance\", \"improve\", \"extend\"\n- **Agent Chain**: Selective (analyst updates → architect if needed → developer → validator → tester)\n- **Documentation**: Requirements updates + implementation in iteration folder\n\n#### REFACTOR\n- **Trigger**: Code improvement without new functionality\n- **Keywords**: \"refactor\", \"clean up\", \"optimize\", \"improve code\"\n- **Agent Chain**: Optimization (architect review → developer refactor → validator compliance)\n- **Documentation**: Architecture improvements + refactoring notes\n\n### Smart Agent Selection\n\nThe orchestrator intelligently selects only necessary agents:\n\n```bash\n# Bug fix example - Only 3 agents needed instead of 8\nBug Fix: spec-analyst → spec-developer → spec-validator\n\n# Small enhancement - Skips architecture if no structural changes\nEnhancement: spec-analyst → spec-developer → spec-validator → spec-tester\n\n# Major feature - Includes architecture updates\nMajor Enhancement: spec-analyst → spec-architect → spec-developer → spec-validator → spec-tester\n\n# Refactoring - Focuses on code quality\nRefactor: spec-architect → spec-developer → spec-validator\n```\n\n## Documentation Organization\n\n### Structured Folder Hierarchy\n\n```\ndocs/\n├── project/                    # Core project docs (rarely change)\n│   ├── requirements.md         # Master requirements\n│   ├── project-charter.md      # Project overview\n│   ├── stakeholders.md         # Key contacts\n│   └── success-criteria.md     # Definition of done\n├── architecture/               # System design (update when needed)\n│   ├── system-architecture.md  # Clean Architecture design\n│   ├── api-specifications.md   # OpenAPI specs\n│   ├── data-models.md          # Entity Framework models\n│   ├── security-design.md      # Authentication \u0026 authorization\n│   └── deployment-strategy.md  # Azure deployment plan\n├── iterations/                 # Version-controlled changes\n│   ├── v1-initial-setup/       # Initial project creation\n│   │   ├── iteration-overview.md\n│   │   ├── implementation-plan.md\n│   │   ├── validation-report.md\n│   │   └── retrospective.md\n│   ├── v2-auth-bugfix/         # Authentication bug fixes\n│   ├── v3-reporting-feature/   # New reporting functionality\n│   └── v4-performance-opts/    # Performance optimizations\n├── current/                    # Active working state\n│   ├── request-analysis.md     # Current request classification\n│   ├── active-tasks.md         # Work in progress\n│   ├── known-issues.md         # Identified problems\n│   ├── next-priorities.md      # Upcoming work\n│   └── recent-changes.md       # Change log\n└── archive/                    # Completed/obsolete docs\n    └── old-requirements-v1.md\n```\n\n### Benefits of Organized Structure\n\n- **No Document Chaos**: Instead of 59+ scattered files, logical organization\n- **Version Control**: Each iteration has its own folder with complete context\n- **Easy Navigation**: Clear hierarchy makes finding information simple\n- **Change Tracking**: Complete history of what changed when and why\n- **Token Efficiency**: Agents read only relevant existing documentation\n\n## Agent Reference\n\n### Enhanced Agent Capabilities\n\nAll agents now include:\n- **Context Awareness**: Read existing project state before starting work\n- **Incremental Updates**: Update existing documents rather than recreate\n- **Iteration Management**: Organize work into versioned iterations  \n- **.NET 9 Optimization**: Specialized knowledge of .NET 9, Clean Architecture, EF Core\n- **Azure Integration**: Deployment-ready configurations for Azure App Service/AKS\n\n### Core Workflow Agents (.NET 9 Enhanced)\n\n| Agent | Purpose | Context-Aware Features | .NET 9 Specialization |\n|-------|---------|----------------------|---------------------|\n| spec-orchestrator | Workflow coordination \u0026 request classification | Analyzes existing docs, selects optimal agent chain | .NET project structure, quality gates |\n| spec-analyst | Requirements analysis | Updates existing requirements incrementally | C# domain modeling, user stories |\n| spec-architect | System design | Enhances existing architecture, minimal changes | Clean Architecture, EF Core, Azure |\n| **database-specialist** | **Manufacturing database expertise** | **Auto-included for database-intensive requests** | **Historian integration, FDA compliance, time-series optimization** |\n| spec-developer | Implementation | Follows existing patterns, targeted changes | Modern C# 13, ASP.NET Core, Entity Framework |\n| spec-validator | Quality validation | .NET-specific quality criteria, regression testing | Code coverage, security, performance |\n| spec-tester | Testing | Extends existing test suites, regression focus | xUnit, integration tests, mocking patterns |\n\n### Quality Gate Integration\n\nEach agent contributes to .NET-specific quality metrics:\n\n- **Requirements Coverage**: 95% (business rules clearly defined)\n- **Clean Architecture Compliance**: 90% (proper layer separation)\n- **Code Coverage**: 85% (xUnit tests with meaningful assertions)\n- **Security Score**: 95% (OWASP compliance, proper authentication)\n- **Performance Score**: 90% (response times, memory usage)\n- **Azure Readiness**: 85% (deployment configuration, monitoring)\n\n## Usage Examples\n\n### Example 1: New .NET 9 Enterprise Application\n\n```bash\n/agent-workflow \"Create a .NET 9 enterprise application for managing manufacturing processes across 5 US facilities with Entra authentication and role-based access control, real-time monitoring, and Azure deployment\"\n\n# Expected behavior:\n# - Classification: NEW_PROJECT\n# - Full agent chain executed\n# - Complete documentation structure created\n# - Clean Architecture with .NET 9\n# - Entity Framework Core for data access  \n# - Azure App Service deployment configuration\n# - Comprehensive test suite with xUnit\n```\n\n### Example 2: Bug Fix for Existing Project\n\n```bash\n/agent-workflow \"User authentication is failing after the recent Azure AD B2C integration\"\n\n# Expected behavior:\n# - Classification: BUG_FIX\n# - Reads existing authentication architecture\n# - Creates iteration v3-auth-bugfix/\n# - Targeted agent chain: analyst → developer → validator\n# - Minimal documentation updates\n# - Regression tests added\n# - No unnecessary architecture regeneration\n```\n\n### Example 3: Adding New Feature\n\n```bash\n/agent-workflow \"Add real-time inventory tracking with SignalR to the existing manufacturing application\"\n\n# Expected behavior:\n# - Classification: ENHANCEMENT  \n# - Updates existing requirements in new iteration\n# - Evaluates if architecture changes needed (yes, SignalR)\n# - Selective agent chain: analyst → architect → developer → validator → tester\n# - Extends existing test suite\n# - Documents SignalR configuration\n```\n\n### Example 4: Database-Intensive Manufacturing Enhancement\n\n```bash\n/agent-workflow \"Add Wonderware Historian integration for real-time SPC control charts with FDA audit trail\"\n\n# Expected behavior:\n# - Classification: ENHANCEMENT  \n# - Database keywords detected: \"wonderware\", \"historian\", \"real-time\", \"FDA audit trail\"\n# - Agent chain: analyst → architect → database-specialist → developer → validator → tester\n# - Database-specialist provides: Historian integration patterns, time-series optimization, FDA compliance schemas\n# - Creates manufacturing-specific database models and queries\n# - Implements regulatory compliance audit trails\n# - Extends test suite with historian integration tests\n```\n\n### Example 5: Performance Refactoring\n\n```bash\n/agent-workflow \"Optimize the data access layer performance using EF Core best practices and caching\"\n\n# Expected behavior:\n# - Classification: REFACTOR\n# - Reviews existing architecture\n# - Agent chain: architect → developer → validator\n# - Focuses on Entity Framework optimization\n# - Implements Redis caching\n# - Validates no functionality changes\n# - Performance benchmarking tests\n```\n\n## Quality Gates\n\n### .NET 9 Specific Quality Gates\n\n#### Gate 1: Planning Quality (95% threshold)\n- Requirements completeness and .NET alignment\n- Clean Architecture feasibility assessment  \n- Entity Framework model validity\n- Azure deployment strategy validation\n- Security design compliance\n\n#### Gate 2: Development Quality (90% threshold)\n- C# code quality (StyleCop, analyzers)\n- Unit test coverage (≥85% with xUnit)\n- Clean Architecture layer compliance\n- Entity Framework performance patterns\n- Security implementation (authentication, authorization)\n\n#### Gate 3: Production Readiness (85% threshold)\n- Overall quality score aggregation\n- Azure deployment readiness\n- Application Insights monitoring configuration\n- Documentation completeness\n- Operational runbook validation\n\n### Context-Aware Quality Assessment\n\nQuality gates now consider project context:\n- **Bug Fixes**: Focus on regression prevention and fix validation\n- **Enhancements**: Validate integration with existing system\n- **Refactoring**: Ensure no functional changes occurred\n- **New Projects**: Full comprehensive quality assessment\n\n## Best Practices\n\n### 1. Leveraging Context Awareness\n\n- **Start Small**: Begin with bug fixes to understand the system\n- **Trust Classification**: Let the orchestrator determine the optimal workflow\n- **Review Iterations**: Check iteration folders to understand project evolution\n- **Maintain Clean State**: Keep current/ folder updated with active work\n\n### 2. .NET 9 Development\n\n- **Follow Clean Architecture**: Use the established layer patterns\n- **Entity Framework Best Practices**: Leverage EF Core optimizations\n- **Modern C# Features**: Use records, pattern matching, nullable reference types\n- **Azure Integration**: Design for cloud-native deployment from the start\n\n### 3. Documentation Management\n\n- **Stable vs Dynamic**: Keep core docs in project/, changes in iterations/\n- **Version Control**: Each significant change gets its own iteration folder\n- **Change Tracking**: Always update recent-changes.md with summaries\n- **Archive Old**: Move obsolete documents to archive/ folder\n\n### 4. Token Optimization\n\n- **Precise Requests**: Be specific about what needs to be changed\n- **Trust Context**: Let agents read existing state rather than re-explaining\n- **Incremental Work**: Make small, focused changes rather than large rewrites\n- **Validate Scope**: Ensure changes are necessary before starting\n\n## Advanced Usage\n\n### Custom Workflow Configuration\n\n```json\n{\n  \"requestClassification\": {\n    \"forceType\": \"ENHANCEMENT\",\n    \"skipAnalysis\": false\n  },\n  \"qualityThresholds\": {\n    \"planning\": 90,\n    \"development\": 85,\n    \"validation\": 80\n  },\n  \"agentSelection\": {\n    \"skipArchitect\": false,\n    \"forceTesting\": true,\n    \"customValidation\": [\"security-scan\", \"performance-benchmark\"]\n  },\n  \"documentationStrategy\": {\n    \"iterationNaming\": \"v{version}-{type}-{timestamp}\",\n    \"archiveThreshold\": \"30 days\",\n    \"contextDepth\": 3\n  }\n}\n```\n\n### Integration with CI/CD\n\n```yaml\n# GitHub Actions with context-aware validation\nname: .NET Context-Aware Validation\non: [pull_request]\n\njobs:\n  validate-changes:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions/checkout@v4\n      \n      - name: Detect Change Type\n        id: change-detection\n        run: |\n          # Analyze docs/current/recent-changes.md\n          # Determine if this requires validation\n          echo \"change-type=${{ env.CHANGE_TYPE }}\" \u003e\u003e $GITHUB_OUTPUT\n          \n      - name: Context-Aware Validation\n        if: steps.change-detection.outputs.change-type != 'documentation'\n        run: |\n          # Run appropriate validation based on change type\n          /agent-workflow \"Validate recent changes\" --phase=validation\n```\n\n### Manufacturing Facility Deployment\n\n```bash\n# Specialized deployment for manufacturing environments\n/agent-workflow \"Deploy the inventory system to Facility #3 in with local compliance requirements and integration with existing MES systems\"\n\n# Context considerations:\n# - Multi-facility deployment patterns\n# - Manufacturing execution system integration  \n# - Compliance and audit requirements\n# - Real-time production data integration\n# - Facility-specific configurations\n```\n\n## Troubleshooting\n\n### Context-Aware Issues\n\n1. **Wrong Request Classification**\n   ```bash\n   # Force specific request type\n   /agent-workflow \"Add reporting feature\" --force-type=ENHANCEMENT\n   ```\n\n2. **Missing Context**\n   ```bash\n   # Check if docs/ structure exists\n   ls -la docs/\n   \n   # Initialize if missing\n   /agent-workflow \"Initialize project context\" --force-type=NEW_PROJECT\n   ```\n\n3. **Document Chaos (Legacy Projects)**\n   ```bash\n   # Migrate existing scattered docs to organized structure\n   /agent-workflow \"Organize existing documentation into iteration structure\"\n   ```\n\n4. **Agent Selection Issues**\n   ```bash\n   # Override agent selection\n   /agent-workflow \"Fix authentication bug\" --agents=\"spec-developer,spec-validator\"\n   ```\n\n### .NET 9 Specific Issues\n\n1. **Clean Architecture Violations**\n   - Check validation reports in iterations/\n   - Review architecture compliance scores\n   - Use spec-architect for architectural reviews\n\n2. **Entity Framework Performance**\n   - Check query analysis in validation reports\n   - Review data access patterns\n   - Consider using spec-validator for performance assessment\n\n3. **Azure Deployment Issues**\n   - Validate deployment configuration\n   - Check Application Insights setup\n   - Review security configurations\n\n### Debug Mode\n\n```bash\n# Enable comprehensive debugging\n/agent-workflow \"Debug request classification and agent selection\" --debug=true --verbose=true\n```\n\n## Migration from v1\n\nIf you're migrating from the original workflow system:\n\n1. **Backup Current Work**\n   ```bash\n   cp -r docs/ docs-backup/\n   ```\n\n2. **Initialize New Structure**\n   ```bash\n   /agent-workflow \"Migrate existing project to context-aware structure\" --migration-mode=true\n   ```\n\n3. **Verify Migration**\n   ```bash\n   # Check that all existing docs are properly organized\n   ls -la docs/\n   ```\n\n## Contributing\n\n[![Contributors Welcome](https://img.shields.io/badge/contributors-welcome-brightgreen.svg)](CONTRIBUTING.md)\n[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](CONTRIBUTING.md)\n\nWe welcome contributions to improve the context-aware workflow system! See our [Contributing Guide](CONTRIBUTING.md) for details.\n\n### Quick Contribution Guide\n1. Follow .NET coding standards and Clean Architecture principles\n2. Add comprehensive documentation with examples\n3. Include context-aware behavior in new agents\n4. Test with the enhanced orchestrator\n5. Submit PR with detailed description of improvements\n\n### Ways to Contribute\n- 🐛 **Bug Reports**: Help us identify and fix issues\n- ✨ **Feature Requests**: Suggest new capabilities\n- 🤖 **New Agents**: Create specialized agents for specific domains\n- 🏭 **Manufacturing Use Cases**: Share industry-specific scenarios\n- 📚 **Documentation**: Improve guides and examples\n- 🧪 **Testing**: Add test coverage and validation scenarios\n\n## License\n\nMIT License - see LICENSE file for details\n\n## Acknowledgments\n\n- Built on Claude Code's Sub-Agents feature\n- Optimized for .NET 9 and Clean Architecture patterns\n- Inspired by enterprise software development best practices\n- Community contributions from manufacturing industry specialists\n\n## 📊 Project Stats\n\n[![GitHub stars](https://img.shields.io/github/stars/jakeashcraft/claude-sub-agent.svg?style=social\u0026label=Star)](https://github.com/jakeashcraft/claude-sub-agent)\n[![GitHub forks](https://img.shields.io/github/forks/jakeashcraft/claude-sub-agent.svg?style=social\u0026label=Fork)](https://github.com/jakeashcraft/claude-sub-agent/fork)\n[![GitHub issues](https://img.shields.io/github/issues/jakeashcraft/claude-sub-agent.svg)](https://github.com/jakeashcraft/claude-sub-agent/issues)\n[![GitHub pull requests](https://img.shields.io/github/issues-pr/jakeashcraft/claude-sub-agent.svg)](https://github.com/jakeashcraft/claude-sub-agent/pulls)\n\n## 🔗 Quick Links\n\n**📚 Documentation \u0026 Learning**\n- [📖 Examples Directory](examples/) - Practical workflow examples\n- [🤝 Contributing Guide](CONTRIBUTING.md) - How to contribute\n- [📋 Changelog](CHANGELOG.md) - Version history and updates\n- [❓ FAQ \u0026 Discussions](https://github.com/jakeashcraft/claude-sub-agent/discussions)\n\n**🔧 Development Resources**\n- [Claude Code Documentation](https://docs.anthropic.com/en/docs/claude-code) - Official Claude Code docs\n- [Sub-Agents Guide](https://docs.anthropic.com/en/docs/claude-code/sub-agents) - Sub-agents feature guide\n- [.NET 9 Documentation](https://docs.microsoft.com/en-us/dotnet/) - Microsoft .NET documentation\n- [Clean Architecture Guide](https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html) - Architecture principles\n\n**🐛 Support \u0026 Issues**\n- [🐛 Report Issues](https://github.com/jakeashcraft/claude-sub-agent/issues/new/choose) - Bug reports and feature requests\n- [💬 GitHub Discussions](https://github.com/jakeashcraft/claude-sub-agent/discussions) - Community discussions\n- [📧 Contact](https://github.com/jakeashcraft) - Direct contact with maintainer\n\n---\n\n**Manufacturing Compliance Standards:**\n- [FDA 21 CFR Part 11](https://www.fda.gov/regulatory-information/search-fda-guidance-documents/part-11-electronic-records-electronic-signatures-scope-and-application) - Electronic Records and Electronic Signatures\n- [HACCP Guidelines](https://www.fda.gov/food/guidance-regulation-food-and-dietary-supplements/hazard-analysis-critical-control-points-haccp) - Hazard Analysis Critical Control Points\n- [ISO 22000:2018](https://www.iso.org/standard/65464.html) - Food Safety Management Systems\n- [SOX Compliance](https://www.sec.gov/page/oxsarbanesoxleyact) - Sarbanes-Oxley Act Requirements\n- [GMP Guidelines](https://www.fda.gov/drugs/pharmaceutical-quality-resources/current-good-manufacturing-practice-cgmp-regulations) - Current Good Manufacturing Practice\n\n**System Integration Resources:**\n- [MES Integration Patterns](https://www.mesa.org/en/modelinglibrary/mesa-model.asp) - Manufacturing Execution Systems\n- [SCADA System Architecture](https://www.automationworld.com/factory/scada/article/13316495/scada-system-architecture-and-design) - Supervisory Control and Data Acquisition\n- [Azure Industrial IoT](https://azure.microsoft.com/en-us/solutions/industry/manufacturing/) - Cloud Manufacturing Solutions","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjakeashcraft%2Fclaude-sub-agent-workflow","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjakeashcraft%2Fclaude-sub-agent-workflow","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjakeashcraft%2Fclaude-sub-agent-workflow/lists"}