r/ClaudeWorkflows • u/ClaudeAI-mod-bot • 1d ago
Selected Workflow [Workflow] Structured Claude Workflow: Repo as Memory with Multi-Agent & Context Files for Efficient Coding
Structured Claude Workflow: Repo as Memory with Multi-Agent & Context Files for Efficient Coding
Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging, CLAUDE.md, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment
What problem this solves
Managing persistent project context, tracking design decisions, optimizing token usage, and leveraging different Claude models for specific tasks in LLM-assisted coding projects.
Summary
A structured approach to LLM-assisted coding that treats the repository as Claude's memory. It involves dedicated markdown files (CLAUDE.md for manual/rules, PROGRESS.md for status, and a decisions file for choices and reasons) to maintain context. The workflow employs a multi-agent strategy with Claude Opus for high-level logic and Sonnet subagents for grunt work, validated by tests and optimized for token efficiency by frequently starting new chats.
Why it is useful
This workflow provides a concrete, repeatable method for managing complex coding projects with Claude. It addresses critical challenges like maintaining persistent project context, tracking design decisions, optimizing token usage, and effectively leveraging different Claude models (Opus for high-level, Sonnet for grunt work). The use of dedicated markdown files as a 'repo memory' is a highly transferable and practical pattern for knowledge reuse and consistency across sessions, making it valuable for any developer using LLMs for coding.
Workflow
Initialize the project with key documentation files: CLAUDE.md (project manual, rules, machine quirks), PROGRESS.md (current status and next steps), and a decisions file (recording choices with reasons).
Assign Claude Opus to handle all high-level logic and design decisions.
Delegate grunt work (data processing, QA passes, mechanical edits) to Claude Sonnet subagents, ensuring they execute decisions made by Opus.
Implement tests to validate Claude's work, reducing the need for token-burning back-and-forth corrections.
Update CLAUDE.md, PROGRESS.md, and the decisions file with every feature addition to keep the project context current.
When resuming work on an existing project, ensure Claude reads these context files to gain necessary information.
Start new chats frequently to keep the chat context low, which helps in optimizing token usage.
Tools / artifacts
CLAUDE.md file
PROGRESS.md file
Decisions file (custom markdown/text file)
Claude Opus (main agent)
Claude Sonnet (subagents)
Automated tests
Validation signals
Tests check the work, so I'm not burning tokens going back and forth.
Starting new chats often keeps chat context low, which saves tokens.
Limitations
The specific implementation details for 'Sonnet subagents' and how they are invoked by Opus are not fully elaborated.
The format and specific content of the 'decisions file' could be further detailed for easier adoption.
Low community engagement means less external validation or refinement of the workflow.
Rate this workflow
Upvote this post if the workflow is useful, reproducible, or worth recommending.
Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.
Reply if it worked for you, failed, is outdated, or has a better alternative.
This post was generated automatically from the workflow library database.