ReadingResearchRadarInvestment frameworkAI Company Primary Sources
Sign in / Sign up
← Back to reading
NewsTopic · 智能体编排与提示词之争Material1 min readDisconfirmAI Editorial

German Software Testing Practitioner Paul Behrend: Central Orchestration Agent Loads Skills on Demand, Replacing Simple Prompts and Multi-Agent Piling

Paul Behrend proposes using a central orchestration agent to dynamically load testing skills according to tasks while adhering to preset guardrails, replacing two failure modes of simple prompts and multi-agent piling; he also found that skill output quality is highly dependent on the underlying model, and switching models leads to significant bias.

2026-11-02 19:00 GMT+8

The application of generative AI in software testing suffers from two common failure modes: simple prompts often produce incorrect or incomplete results, while piling up multiple independent agents increases cost and complexity without necessarily improving quality. Paul Behrend, who has over ten years of experience in software quality assurance, proposes an intermediate path in his practice report—deploying a central orchestration agent that guides the testing process according to preset guardrails and dynamically loads corresponding skills based on the current task, covering test analysis, test design, and test case generation separately. This integrates originally scattered auxiliary tools into a clear and verifiable workflow, producing reliable, traceable results that directly serve test implementation.

However, Behrend discovered a practical boundary when implementing this method: the output quality of skills is tightly bound to the language model they are adapted for. Once the underlying model is switched, the answer quality will show significant deviation. The orchestration architecture itself cannot shield against the impact of model changes; teams still face the risk of quality fluctuations when selecting and migrating models.

Behrend also points out that agents are not a universal replacement—in specific scenarios, classic automation remains the better choice. Ensuring test quality ultimately depends on experienced testers, clear processes, and targeted cooperation with agents; all three are indispensable.

Sign in / Sign up
ReadingResearchRadarInvestment frameworkAI Company Primary Sources

Sources

  • heise.deDeveloper↗
  • sigs.deSIGS↗
Topic

智能体编排与提示词之争

智能体编排与提示词之争的核心在于:面对大模型在软件测试等复杂任务中的局限,是依赖单一中央Agent动态加载Skills并遵循护栏,还是堆砌多Agent或仅靠简单Prompt?德国测试专家Paul Behrend指出,简单Prompt易产生错…

4 steps1 piecesUpdated 2026-11-03 00:04

How it got here

  1. 2026-01-27斯坦福大学CS 224G课程发布讲义《Agent Orchestration & Workflow Design》,由微软首席应用科学家Rakshit Agrawal主讲,系统对比LangGraph与CrewAI框架,提出从单Agent向多Agent演进的架构原则。web.stanford.edu ↗
  2. 2026-01-22OpenAI开发者博客发布文章《Testing Agent Skills Systematically with Evals》,介绍Codex中Agent Skills的定义及如何通过Evals(评估)量化其性能,强调先定义成功标准再编写Skill。developers.openai.com ↗
  3. 2026-06-01Buidlguidl团队发表博客《Evaluating agent skills: testing whether they are actually useful》,披露对Scaffold-ETH 2项目进行92次A/B评估的结果,发现自评分数虚高60分,证实多数Skill需经过严格测试才能证明其能力增益。buidlguidl.com ↗

What is still unsettled

  • 当底层LLM版本更新时,如何自动化地重新验证所有已部署Agent Skills的有效性以避免静默退化?
  • 在多Agent系统中,如何平衡‘生成式编排’带来的灵活性优势与学术界警告的‘偏见放大’及‘决策不透明’风险?
  • 对于企业级应用,是否存在统一的行业标准来界定何时应使用确定性工作流,何时必须引入非确定性的Agent推理?
Read the full topic →
Continue researching →