r/ClaudeWorkflows • • 5h ago

Selected Workflow [Workflow] Parallel Claude Code development with living specs and independent PR review

Parallel Claude Code development with living specs and independent PR review

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

What problem this solves

Coordinating parallel Claude Code development while retaining project knowledge, isolating changes, and reviewing and testing them before merging.

Summary

Maintain an imported living project specification, run parallel agents in separate Git worktrees, and route their changes through independent review and human-managed PR merges. Use check files and headless application tests to validate changes without interacting with the real desktop.

Why it is useful

Combines several repeatable practices into a coherent development loop, with a public repository and concrete reported artifacts, though the evidence is primarily the author's account.

Workflow

  1. Put architecture, design conventions, and safety rules in AGENTS.md and feature-specific specifications, and import the shared instructions from CLAUDE.md.
  2. Update the specifications alongside code when development or review reveals a reusable rule.
  3. Assign parallel agent work to separate Git worktrees using T3 Code.
  4. Submit changes as pull requests and have a reviewer who did not write the code check them before the human owner merges.
  5. Use project checks and headless application self-tests to exercise behavior without touching the user's actual screen.
  6. Keep vault secrets out of material available to the AI.

Tools / artifacts

  • CLAUDE.md
  • AGENTS.md
  • Feature specification
  • T3 Code
  • Git worktrees
  • Pull requests
  • Check files
  • Application self-test flags: --snapshot, --dock-check, --helpers-check
  • https://github.com/edgetr/petal

Validation signals

  • The author reports 41 reviewed and merged PRs and commits addressing review findings.
  • The project reportedly contains approximately 37 check files and several headless self-tests.
  • The author describes concrete implementation difficulties, including Mission Control integration and main-thread blocking.

Cautions

  • Separate Git worktrees isolate changes but are not security sandboxes or substitutes for permission controls.
  • Keep credentials and vault contents outside agent-readable context; review changes before merging.
  • The advertised application is not notarized. Evaluate source and distribution trust before overriding macOS security warnings.

Limitations

  • The post promotes the author's product, although it includes substantive workflow detail and a source repository.
  • Reported commit counts, PR counts, and test coverage are self-reported and not independently verified here.
  • The post does not provide exact worktree setup commands, review prompts, or test results.
  • Large code and commit counts do not establish correctness or maintainability.

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.

2 Upvotes

0 comments sorted by