<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel>
<title>For Users — Planning</title>
<link>https://forusers.org/</link>
<description>Community questions, answered and written up as clear, readable guides.</description>
<language>en-us</language>
<atom:link rel="self" href="https://forusers.org/topic/planning/rss.xml" type="application/rss+xml"/>
<atom:link rel="hub" href="https://pubsubhubbub.appspot.com/"/>
<atom:link rel="hub" href="https://pubsubhubbub.superfeedr.com/"/>
<item>
<title>How to Build Iterative Workflows in Claude Code</title>
<link>https://forusers.org/25342087-iterative-workflows-in-claude-code/</link>
<guid isPermaLink="true">https://forusers.org/25342087-iterative-workflows-in-claude-code/</guid>
<pubDate>Sun, 02 Aug 2026 04:12:53 +0000</pubDate>
<category>claude code</category>
<category>iterative workflows</category>
<category>ai coding</category>
<category>planning</category>
<description>Users build iterative workflows in Claude Code by starting with a planning phase to outline goals and deliverables, then implementing changes, and refining through feedback loops. The approach works for code reviews, debugging, project planning, and data analysis. To manage Claude&#039;s context window and avoid repetition, users externalize state into files like plan.md and CLAUDE.md so Claude can read relevant sections on demand. This keeps sessions focused without re-establishing context each time</description>
<enclosure url="https://forusers.org/assets/img/25342087c6bfb6fa10fce76710bce565829e68a7-1.jpg" length="83611" type="image/jpeg"/>
</item>
<item>
<title>Claude Code Best Practices for Context and Workflows</title>
<link>https://forusers.org/3ccfd3f5-claude-code-best-practices/</link>
<guid isPermaLink="true">https://forusers.org/3ccfd3f5-claude-code-best-practices/</guid>
<pubDate>Wed, 29 Jul 2026 23:29:19 +0000</pubDate>
<category>claude code</category>
<category>best practices</category>
<category>context management</category>
<category>claudemd</category>
<description>Treat Claude as a capable but context-limited junior developer by managing its context carefully and planning tasks before implementation. Keep your CLAUDE.md files short, ideally under 200 lines, focusing only on tech stacks, conventions, and domain rules Claude cannot infer on its own. Use MEMORY.md files and the /compact command to retain knowledge across sessions and compress context when responses degrade. Always use plan mode for complex tasks, break work into small incremental steps, and </description>
<enclosure url="https://forusers.org/assets/img/3ccfd3f506ddb712c417d740ea5bd4fcc97eb749-1.jpg" length="178891" type="image/jpeg"/>
</item>
</channel></rss>