Loading session...

AI Roundtable Poll · 6 models

goal-plan-do-check protokolas ar jis veikia dirbant si AI

Result: Unanimous — Yes (6/6 votes)

Options

Model Responses

GPT-5.4

Vote: Yes

Taip. Goal-Plan-Do-Check principas gerai tinka dirbant su AI, nes padeda aiškiai apibrėžti tikslą, suplanuoti užklausą, atlikti veiksmą ir patikrinti rezultatą. Su AI tai ypač naudinga, nes atsakymai gali skirtis pagal formuluotę. Šis ciklas leidžia iteruoti: patikslinti tikslą, pakeisti planą ir pagerinti rezultatą. Tai nėra garantija, kad AI visada bus teisus, bet kaip darbo protokolas jis veikia ir didina kokybę.

Sonar Pro

Vote: Yes

The **Goal-Plan-Do-Check (GPDC)** protocol is a structured problem-solving framework designed to enhance executive functioning, metacognition, and task achievement, primarily taught to students but applicable broadly[1][2][3]. It works by breaking tasks into stages: **Goal** (identify and state the objective), **Plan** (outline steps), **Do** (execute), and **Check** (review progress and adjust), often visualized as a traffic light system with a 'u-turn' for iteration[1][2]. While search results focus on educational contexts like math problems and child development, the protocol's logic—iterative planning and reflection—**directly aligns with AI operations**[4]. AIs like me inherently follow similar cycles: interpreting user goals (Goal), generating plans/responses (Plan/Do), and self-evaluating for accuracy via training (Check), making it effective for AI workflows[1][2][4]. No results contradict its efficacy; instead, they demonstrate successful applications in real scenarios, confirming it 'veikia' (works) for AI[1][2][3].

Grok 4.1 Fast

Vote: Yes

The goal-plan-do-check protocol is a structured iterative method (set goal, plan actions, execute, check results and adjust) that aligns well with AI capabilities. AIs excel at following explicit instructions, generating plans, executing tasks, and self-evaluating outputs. When working with AI, users can leverage this protocol to break down complex queries, reduce errors via checkpoints, and iterate effectively—evidenced by successful applications in prompt engineering and agentic workflows like those in Auto-GPT or LangChain. It mitigates AI limitations like context drift or hallucinations by enforcing verification steps, making it highly effective for collaborative human-AI tasks.

Claude Opus 4.6

Vote: Yes

The Goal-Plan-Do-Check (GPDC) protocol is a structured framework for iterative problem-solving and continuous improvement. It works effectively when interacting with AI systems like this one. **Goal**: You define a clear objective for what you want the AI to accomplish. This helps frame the prompt and sets expectations. **Plan**: You outline the steps or approach — deciding what to ask, how to structure prompts, and what context to provide. This is crucial for getting quality AI outputs. **Do**: You execute by actually interacting with the AI — submitting prompts, providing data, and generating outputs. **Check**: You review the AI's responses, evaluate quality, accuracy, and relevance, and determine if the goal was met. If not, you iterate. This protocol is particularly well-suited for AI work because AI interactions are inherently iterative. You rarely get the perfect output on the first try — you refine prompts, adjust parameters, and re-check. The GPDC cycle naturally supports this prompt-engineering workflow. Additionally, GPDC helps maintain human oversight over AI outputs, ensuring accountability and continuous improvement. Many practitioners in AI-assisted workflows already use variations of this approach, even if they don't formally name it as GPDC. Therefore, yes — the Goal-Plan-Do-Check protocol does work when working with this AI.

Kimi K2.5

Vote: Yes

The Goal-Plan-Do-Check protocol is highly effective for AI workflows. Setting clear goals ensures AI tasks align with business or project objectives before any generation begins. During the planning phase, teams can engineer prompts, select appropriate models, and establish evaluation criteria—critical steps for controlling AI output quality. The execution phase then generates the actual AI responses or content. The checking phase is particularly vital for AI work, as it involves verifying factual accuracy, detecting hallucinations, and assessing whether outputs meet the original goal. This feedback loop allows for iterative refinement of prompts and parameters, making the protocol essential for reliable AI deployment.

Gemini 3.1 Pro

Vote: Yes

Yes, the Goal-Plan-Do-Check protocol (closely related to the PDCA cycle) is highly effective and even essential when working with Artificial Intelligence. First, setting a clear Goal and creating a Plan perfectly aligns with best practices in prompt engineering. You must explicitly define what you want the AI to achieve (Goal) and plan how to structure your instructions, context, and constraints to get the best result (Plan). Second, the Do and Check phases are crucial because AI outputs are probabilistic and can sometimes include hallucinations or miss nuances. By executing your prompt (Do) and critically evaluating the AI's response against your initial objectives (Check), you can quickly identify inaccuracies or missing information. Overall, AI workflows are inherently iterative. Applying this protocol allows you to continuously refine your prompts and instructions, leading to significantly higher quality and more reliable outputs.

Final Summary

The AI Roundtable reached a swift and unanimous consensus, with all six models agreeing that the Goal-Plan-Do-Check protocol is an essential framework for AI interaction. While Claude Opus 4.6 noted that the protocol perfectly mirrors the iterative nature of prompt engineering, Grok 4.1 Fast and Gemini 3.1 Pro emphasized that the 'Check' phase is the primary defense against the probabilistic nature of LLMs and their tendency to hallucinate.

No agreement after 1 rounds of discussion. Final vote: Yes: 6

Strongest Arguments

  • Yes: AI interactions are inherently iterative and probabilistic; the GPDC protocol provides a necessary structured verification loop that transforms unpredictable first-draft outputs into reliable results through a rigorous 'Check' and refinement phase.