Claude Code Solo Guild: Structured Development with 4 Rules, Skills, and Subagents

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging, CLAUDE.md, Skills, MCP, Subagents
Original source: r/ClaudeCode post/comment

What problem this solves

Preventing LLMs from self-approving errors, ensuring clear task completion, avoiding re-litigating decisions, and optimizing token usage through strategic delegation in solo Claude Code projects.

Summary

A "solo guild" setup for Claude Code projects, utilizing 41 SKILL.md files, strategic subagent delegation, and four core rules to enforce separation of concerns (build vs. evaluate), define "done," manage irreversible actions, and persist decisions in a DECISIONS.md file.

Why it is useful

This workflow provides a robust, validated framework for managing complex solo development projects with Claude Code. Its emphasis on separation of concerns, explicit decision-making, and strategic delegation directly addresses common LLM limitations, leading to more reliable and efficient outcomes. The explicit testing of the "separate builder from evaluator" rule is a significant validation point, demonstrating a practical solution to a common LLM failure mode.

Workflow

1. Define individual tasks as separate SKILL.md files (e.g., requirements, implementation, review, testing, evaluation, risk check).
2. Implement a "router" (main session logic) to delegate tasks to appropriate agents/skills, picking the smallest party for the task.
3. Utilize subagents for specific tasks: an expensive model for big builds, and a cheap one for mechanical tasks (test runs, log collection) with a concise report format.
4. Apply Rule 1: Separate the "builder" from the "evaluator" (e.g., a separate reviewer and test runner) to prevent models from self-approving their own work.
5. Apply Rule 2: Define "done" as the existence of a run log, not merely model confidence.
6. Apply Rule 3: Implement a safety stop for irreversible actions (publish, pay, delete, overwrite, push), requiring user confirmation.
7. Apply Rule 4: Persist decisions in a DECISIONS.md file and instruct claude.md to read it before planning, preventing settled calls from being reopened.
8. Optimize delegation: For tasks under approximately 20k tokens of actual work, perform them inline in the main session to avoid subagent cold start costs.

Tools / artifacts

• SKILL.md files (41 total, 8 examples on GitHub)
• DECISIONS.md file
• claude.md file
• Subagents (expensive model, cheap model)
• GitHub repository (for shared skills)
• Run logs

Validation signals

• Explicit testing of Rule 1: A single session approved its own bug 4/5 times, while a new session (same model, same diff) caught it immediately.
• Observation: Weekly "we should restructure everything" suggestions stopped after implementing DECISIONS.md (Rule 4).
• Observation: Ability to "walk away from a running session" due to Rule 3 (safety stops for irreversible actions).
• Observation: Optimization for small tasks based on token cost (delegation isn't free).

Limitations

• The specific implementation of the "router" logic for picking the smallest party is not explicitly detailed.
• The full set of 41 skills is behind a paywall, which might limit full adoption for some users, though 8 free examples are provided.
• Low community engagement (score 1, 0 comments) means less external validation or refinement.

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.