<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Agentic Workflow on Haxlys's Blog</title><link>https://hugo-blog-static-site.haxlys.workers.dev/frameworks/agentic-workflow/</link><description>Recent content in Agentic Workflow on Haxlys's Blog</description><generator>Hugo -- 0.152.2</generator><language>kr-ko</language><lastBuildDate>Thu, 29 Jan 2026 15:54:26 +0900</lastBuildDate><atom:link href="https://hugo-blog-static-site.haxlys.workers.dev/frameworks/agentic-workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>에이전틱 코딩의 80% 문제</title><link>https://hugo-blog-static-site.haxlys.workers.dev/software/the-80-problem-in-agentic-coding/</link><pubDate>Thu, 29 Jan 2026 15:54:26 +0900</pubDate><guid>https://hugo-blog-static-site.haxlys.workers.dev/software/the-80-problem-in-agentic-coding/</guid><description>AI 코딩 에이전트가 빠르게 80%를 만들고도 나머지 20%에서 막히는 이유(맥락·검증·루프)와 이를 넘기 위한 협업·테스트·작업 분할 제언을 정리합니다.</description></item></channel></rss>