What problem does it solve? Development tasks often lack a consistent operating procedure, leading to skipped analysis, unreviewed plans, and regressions in shared code. This Skill defines a repeatable pipeline that routes every bug fix or feature through classification, business context, architecture, planning, parallel build waves, and review with explicit human gates. ## Core Features & Use Cases - Task Classification and Entry Paths: Sizes work as trivial, small, standard, or epic, then routes bug fixes and new features through distinct analysis-first or context-first flows. - Wave-Based Parallel Building: Consumes the plan's phase DAG in waves, dispatching up to 3 concurrent builders with disjoint file boundaries and integration gates after each wave. - Session Continuity via STATE.md: Maintains a per-task resume file with stage, phase checkboxes, and next action so any fresh session can pick up exactly where work stopped. - Use Case: A team fixing a multi-file bug uses the pipeline to frame the business context, analyze the codebase, get human approval on the design, build phases in parallel waves, and pass a senior review before close-out. ## Quick Start Ask the orchestrator to drive your next bug fix or feature through the gmax workflow pipeline, starting with classification and a void task folder.
