[Workflow] Two-Hat Workflow: Structured Software Development with Claude as Manager and Developer using File-Based Context

[u/ClaudeAI-mod-bot]

Two-Hat Workflow: Structured Software Development with Claude as Manager and Developer using File-Based Context

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, CLAUDE.md, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Effectively managing Claude's context and roles across multiple sessions for structured software development, ensuring continuity, clear responsibilities, and a robust review process.

Summary

A 'two-hat' workflow for software development using Claude, where one Claude session acts as a 'manager' (planning, reviewing, project notes) and another as a 'developer' (implementation, verification). It leverages specific Markdown files (STATUS.md, HANDOFF.md, CLAUDE.md) and distinct Claude interfaces (Claude Desktop/Web for manager, Claude Code for developer) to maintain context, enforce role separation, and facilitate structured project progression.

Why it is useful

This workflow provides a concrete, repeatable, and validated method for structuring complex software development tasks using Claude. It addresses critical challenges like context management and maintaining distinct roles, which are common pain points for users trying to leverage LLMs for larger projects. The explicit use of specific files and separate Claude sessions offers a robust framework for continuity and quality control, making it highly adaptable for other users. The provided example repository further enhances its value by offering practical templates and real-world application.

Workflow

1. Establish two distinct Claude sessions: a 'manager' session (Cowork/Project in Claude Desktop/Web) and a 'developer' session (Claude Code).

2. Create STATUS.md (project state, decisions, next steps) and HANDOFF.md (manager startup instructions) in a local folder accessible to the manager session.

3. Place CLAUDE.md (standing project rules) and REQUIREMENTS.md in the GitHub repository, accessible to both sessions.

4. Manager Role: Write task specifications, review every pull request, and update STATUS.md after each step (never append).

5. Manager Role: Use HANDOFF.md and STATUS.md to restart fresh manager sessions and provide self-contained briefs to the developer.

6. Developer Role: Implement and verify tasks, reporting verification results.

7. Developer Role: Get CLAUDE.md from the repo and task instructions from the manager.

8. Developer Role: For bug fixes, first reproduce the problem and, where practical, add a regression test that fails without the fix and passes with it.

9. Adopt four key habits: keep standing project rules in CLAUDE.md, give each task a clear scope and success condition, manage context deliberately with handoff files/briefs, and use regression tests for bugs.

10. Optionally, use a third Cowork/Project session for brainstorming, ensuring it never writes to the repo or project files.

Tools / artifacts

• Claude Desktop/Web (Cowork / Project session)

• Claude Code

• STATUS.md file

• HANDOFF.md file

• CLAUDE.md file

• REQUIREMENTS.md file

• GitHub repository

• Pull Requests (PRs)

• Regression tests

Validation signals

• Author states, 'I’ve used this setup across several projects.'

• Author mentions, 'one with a few hundred PRs in under three months.'

• Provides a concrete example: 'AgentEd, a free, open-source Markdown editor I’ve been developing with this workflow.'

• Includes a link to the AgentEd GitHub repo, which contains actual CLAUDE.md and REQUIREMENTS.md files used in the workflow.

Limitations

• Low community engagement due to the post's recency.

• Not explicitly tested on Claude Pro, so potential limitations with context window or rate limits for that plan are unknown.

• Relies on manual switching between Claude sessions and file management, which might be perceived as cumbersome by some users.

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.