Skip to content

[deep-report] Tighten Design Decision Gate prompt to reduce turn count and resource usage #27376

@github-actions

Description

@github-actions

The Design Decision Gate workflow has been flagged by the observability system (#27293) with 2 consecutive resource_heavy_for_domain HIGH assessments and the turn count growing 4 → 8 → 10 across three runs today. The latest run also triggered poor_agentic_control MEDIUM. The agent is using 9 distinct tool types in broad exploratory posture, with ~50% of turns being pure data-gathering that could be deterministic pre-steps.

The fix is to narrow the workflow's instructions: replace open-ended "analyze the decision" framing with a specific, scoped question template; pre-fetch relevant data in a deterministic step before the agent runs; and add explicit turn limits/stopping criteria in the prompt.

Expected Impact: Estimated 40–60% reduction in turn count (target: ≤ 5 turns), lower cost per run, and removal of the resource_heavy_for_domain flag that is currently triggering escalation alerts.

Suggested Agent: A coding agent reviewing .github/workflows/design-decision-gate.yml and its associated prompt

Estimated Effort: Medium (1–4 hours) — prompt engineering and workflow restructuring.

Data Source: DeepReport Intelligence Briefing 2026-04-20 (§24673982657); observability escalation #27293.

Generated by DeepReport - Intelligence Gathering Agent · ● 375K ·

  • expires on Apr 22, 2026, 3:16 PM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions