<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Workflow on SoloSoft</title><link>https://www.solosoft.dev/tags/ai-workflow/</link><description>Recent content in AI Workflow on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 31 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/ai-workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>CRAFT Framework Guide for Structured AI Workflows</title><link>https://www.solosoft.dev/post/craft-framework-complete-guide-2026/</link><pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/craft-framework-complete-guide-2026/</guid><description>&lt;p&gt;Most teams still use AI in a fragile way. Someone opens ChatGPT, Claude, or a coding assistant, pastes a task, gets a decent answer, and then starts over the next day because the context is gone. That works for one-off prompts, but it breaks down when a project stretches across weeks, when multiple people need to reuse the same AI workflow, or when the output has to follow a repeatable standard. &lt;strong&gt;CRAFT Framework&lt;/strong&gt; exists to address that gap. Rather than introducing a new model, it introduces structure around model usage: project variables, recipes, comments, personas, and handoff files that preserve continuity between sessions. Based on the public GitHub repository, official documentation, and related explanatory materials, CRAFT is best understood as a framework for turning AI conversations into durable operating systems for ongoing work. That makes it relevant not just to developers, but also to content teams, operators, and consultants who rely on AI repeatedly and need more than a clever prompt. In 2026, as AI tools increasingly become part of daily production workflows, CRAFT is interesting because it focuses on the layer many teams still lack: process discipline.&lt;/p&gt;</description></item></channel></rss>