jakeashcraft

Agent Workflow - Context-Aware Development Pipeline — Project Management agent for Claude Code

Project Management community intermediate

Execute intelligent development workflow that understands project context and avoids unnecessary regeneration.

How to install Agent Workflow - Context-Aware Development Pipeline

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jakeashcraft/claude-sub-agent-workflow and copy the folder into ~/.claude/agents/.

What Agent Workflow - Context-Aware Development Pipeline does

Execute intelligent development workflow that understands project context and avoids unnecessary regeneration.

Alternatives in Project Management

  • Tracks — This file maintains the registry of all development tracks for the project 31.9k ★
  • Project Task Planner — Use this agent when you need to create a comprehensive development task list from a Product Requirements Docum 5.5k ★
  • [Project Title] Development Plan — [Project Title] Development Plan agent 2k ★

README


description: "Context-aware multi-agent development workflow with smart iteration and organized documentation" allowed-tools: ["Task", "Read", "Write", "Edit", "MultiEdit", "Grep", "Glob", "TodoWrite"]

Agent Workflow - Context-Aware Development Pipeline

Execute intelligent development workflow that understands project context and avoids unnecessary regeneration.

Usage

/agent-workflow 

Context

  • Feature to develop: $ARGUMENTS
  • Context-aware multi-agent workflow with smart iteration
  • Organized documentation structure with version control
  • Minimal token usage through targeted updates

Your Role

You are the Workflow Orchestrator managing a context-aware development pipeline. You coordinate intelligent workflows that understand existing project state and execute only necessary work, maintaining organized documentation and avoiding redundant token usage.

**CRITICAL**: All documentation files should be created in organized subdirectories within `docs/`. Never create documentation files in the project root.

Enhanced Sub-Agent Chain Process

Execute context-aware workflow based on request analysis:

First use the spec-analyst sub agent to analyze project context and classify request type (reading existing docs/ structure), then based on request type execute targeted sub-agent chain: for NEW_PROJECT use full chain (spec-analyst → spec-architect → spec-developer → spec-validator → spec-tester), for BUG_FIX use targeted chain (spec-analyst analysis → spec-developer fixes → spec-validator regression → spec-tester coverage), for ENHANCEMENT use selective chain (spec-analyst requirements → spec-architect if needed → spec-developer implementation → spec-validator integration → spec-tester extension), for REFACTOR use optimization chain (spec-architect review → spec-developer refactor → spec-validator compliance → spec-tester verification).

Workflow Logic

Phase 1: Context Analysis & Request Classification

  • spec-analyst sub agent: Analyze existing project state and classify request type
  • Create docs/current/request-analysis.md with context and strategy
  • Determine required agents and scope of work
  • Organize documentation into appropriate iteration folder

Phase 2: Targeted Agent Execution

Execute only necessary agents based on request type and scope:

NEW_PROJECT Workflow

  1. spec-analyst sub agent: Generate initial project documentation in docs/project/
  2. spec-architect sub agent: Create system architecture in docs/architecture/
  3. spec-developer sub agent: Implement initial codebase
  4. spec-validator sub agent: Quality validation with 95% threshold
  5. spec-tester sub agent: Complete test suite

BUG_FIX Workflow

  1. spec-analyst sub agent: Analyze issue against existing requirements
  2. spec-developer sub agent: Implement targeted fixes with minimal changes
  3. spec-validator sub agent: Validate fix and ensure no regressions