Advanced Project Planning and Automated Daily Code Review with Claude Code's /goal and /loop

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, CLAUDE.md, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Efficiently planning large software projects and establishing an automated daily review and bug detection process using Claude Code's /goal and /loop commands.

Summary

The author describes using Claude Code's Fable model with /goal for detailed project planning, including task breakdown, dependency analysis, and a task lifecycle (commit, review, test). They also outline a /loop command for daily automated review of commits, bug detection, task creation, and work log generation, leveraging a spawned Sonnet agent.

Why it is useful

This workflow demonstrates a sophisticated and practical application of Claude Code's /goal and /loop commands for managing complex software development. It provides concrete, detailed prompts for project planning, including dependency analysis and a structured task lifecycle. Furthermore, it outlines an automated daily process for reviewing commits, identifying bugs, and generating work logs, significantly enhancing code quality and team integration. The specificity and reusability of the prompts make it highly valuable for intermediate to advanced users looking to leverage Claude Code for end-to-end project management and quality assurance.

Workflow

1. Initiate a chat with Fable, setting 'high effort' for comprehensive analysis.
2. Provide Fable with a high-level description of the project vision and requirements, emphasizing enterprise product considerations and deep research.
3. Prompt Fable to break down the project into epics and tasks, considering all possibilities.
4. Execute the /goal command with a detailed prompt:

• Read the current session and create a checklist of all important information.
• Write all identified tasks into a tasks directory (create if it doesn't exist).
• Before writing, review tasks for blind spots using dependency graphs, issue trees, and decision tables.
• Define a task lifecycle: after finishing each task, commit it, review it, write tests, and test it. If successful, proceed; otherwise, re-run the loop to fix the issue.

5. Set up a daily automated review using the /loop command:

• Schedule the loop (e.g., /loop 1d at 08:00).
• Specify an agent to spawn (e.g., spawn a agent sonnet 4.6 high).
• Instruct the agent to load the last day's work log.
• Instruct the agent to review all commits from the past 24 hours.
• If issues or bugs are found, create a new task in the tasks directory with relevant tags for easy identification.
• Instruct the agent to write a work log with the exact date and time (using the date command).

Tools / artifacts

• Claude Code (Fable model)
• /goal command
• /loop command
• tasks directory
• Dependency graph (conceptual tool for Fable)
• Issue tree (conceptual tool for Fable)
• Decision table (conceptual tool for Fable)
• Work log
• Git commits
• Sonnet agent

Validation signals

• Author's strong positive sentiment ("Holy shit!", "unbelievable").
• Author's intent to share results on GitHub (promise of future validation).

Limitations

• Low community validation due to the post's age.
• The 'high effort' setting can be token-intensive, requiring careful cost management.
• No concrete code examples or GitHub link are provided yet.

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.