gaia-problem-solving

Structured problem-solving workflows orchestrate a plan-approve-execute cycle, gathering context automatically to produce a problem-solving artifact for complex feature requests. It delegates analysis and routes results directly to story creation or feature enhancement paths.

Automated context gathering for incident resolution aggregates data across a 30K token budget distributed into six sub-budgets. It collects architecture, PRD, test artifacts, and decision logs to generate a structured problem-solving artifact.

Yes, an explicit planning gate is required before execution in this problem-solving workflow. The plan-approve-execute gate ensures formal review of the gathered context before delegating analysis and routing downstream.

Design problem analysis results route directly to downstream integration paths like story creation or feature enhancement. If issues require higher-level intervention, the workflow supports escalation to an architect or PM.

The 30K token context budget is distributed across six sub-budgets, limiting the volume of architecture, PRD, and test artifacts gathered simultaneously. Delegation to Nova handles analysis, but extreme context overflow requires manual trimming before routing.