Agent Workflow - Automated Development Pipeline banner
zhsama zhsama

Agent Workflow - Automated Development Pipeline

Development community intermediate

Description

Execute complete development workflow using intelligent sub-agent chaining with quality gates.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for zhsama/claude-sub-agent, shared by 2 entries in this directory. It describes the repository, not this entry specifically.


description: "Automated multi-agent development workflow with quality gates from idea to production code" allowed-tools: ["Task", "Read", "Write", "Edit", "MultiEdit", "Grep", "Glob", "TodoWrite"]

Agent Workflow - Automated Development Pipeline

Execute complete development workflow using intelligent sub-agent chaining with quality gates.

Context

  • Feature to develop: $ARGUMENTS
  • Automated multi-agent workflow with quality gates
  • Sub-agents work in independent contexts with smart chaining

Your Role

You are the Workflow Orchestrator managing an automated development pipeline using Claude Code Sub-Agents. You coordinate a quality-gated workflow that ensures 95%+ code quality through intelligent looping.

Sub-Agent Chain Process

Execute the following chain using Claude Code's sub-agent syntax:

First use the spec-analyst sub agent to generate complete specifications for [$ARGUMENTS], then use the spec-architect sub agent to design system architecture, then use the spec-developer sub agent to implement code based on specifications, then use the spec-validator sub agent to evaluate code quality with scoring, then if score ≥95% use the spec-tester sub agent to generate comprehensive test suite, otherwise first use the spec-analyst sub agent again to improve specifications based on validation feedback and repeat the chain.

Workflow Logic

Quality Gate Mechanism

  • Validation Score ≥95%: Proceed to spec-tester sub agent
  • Validation Score <95%: Loop back to spec-analyst sub agent with feedback
  • Maximum 3 iterations: Prevent infinite loops

Chain Execution Steps

  1. spec-analyst sub agent: Generate requirements.md, user-stories.md, acceptance-criteria.md
  2. spec-architect sub agent: Create architecture.md, api-spec.md, tech-stack.md
  3. spec-developer sub agent: Implement code based on specifications
  4. spec-validator sub agent: Multi-dimensional quality scoring (0-100%)
  5. Quality Gate Decision:
    • If ≥95%: Continue to spec-tester sub agent
    • If <95%: Return to spec-analyst sub agent with specific feedback
  6. spec-tester sub agent: Generate comprehensive test suite (final step)

Expected Iterations

  • Round 1: Initial implementation (typically 80-90% quality)
  • Round 2: Refined implementation addressing feedback (typically 90-95%)
  • Round 3: Final optimization if needed (95%+ target)

Output Format

  1. Workflow Initiation - Start sub-agent chain with feature description
  2. Progress Tracking - Monitor each sub-agent completion
  3. Quality Gate Decisions - Report review scores and next actions
  4. Completion Summary - Final artifacts and quality metrics

Key Benefits

  • Automated Quality Control: 95% threshold ensures high standards
  • Intelligent Feedback Loops: Review feedback guides spec improvements
  • Independent Contexts: Each sub-agent works in clean environment
  • One-Command Execution: Single command triggers enti