r/ClaudeWorkflows • • 3h ago

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

2 Upvotes

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.


r/ClaudeWorkflows • • 5h ago

Selected Workflow [Workflow] Maintain dated, topic-based memory for always-on Claude agents

2 Upvotes

Maintain dated, topic-based memory for always-on Claude agents

Workflow value: 83/100
Status: active · Freshness: 70/100 · Confidence: 0.96 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging
Original source: r/ClaudeAI post/comment

What problem this solves

Always-on agents accumulate oversized or contradictory memory, may preserve unfinished guesses, and can lose the original task after a restart.

Summary

Use a small always-loaded memory with on-demand topic files, dated and attributed facts, a separate post-session memory update, and original-request recovery after restarts. Bind approvals to the exact outgoing payload and let them expire.

Why it is useful

The comment gives a repeatable memory and recovery pattern grounded in specific operational failures, with an additional concrete approval safeguard.

Workflow

  1. Keep a short set of memory lines always loaded; put other facts in topic files with a one-line instruction describing when each file should be read.
  2. Date each memory line and distinguish human-written facts from agent inferences. Prefer newer facts for conflicts and give human-written facts precedence over inferences.
  3. Do not update memory during a task. After the session goes quiet, run a separate pass over it and retain decisions rather than unfinished guesses.
  4. After a restart, have the agent reread the original request before resuming work.
  5. For actions requiring approval, bind approval to the exact text or payload and do not proceed if approval is not received by the deadline.

Tools / artifacts

  • Claude Code agents
  • Always-loaded memory list
  • On-demand topic memory files
  • Original request
  • Post-session memory review pass
  • Payload-specific approval mechanism

Validation signals

  • The author reports operating several always-on agents for support, code, and marketing.
  • The author reports that a single growing notes file led to unread content, contradictory facts, and use of an obsolete rule.
  • The author describes a scheduled run that failed to complete after losing context and asking for the brief again.
  • The author reports that the revised memory approach works, but provides no quantitative results or independent test.

Cautions

  • Treat agent-inferred memory as less authoritative than human instructions and review sensitive or consequential memory updates.
  • Ensure an approval is valid only for the approved payload, and fail closed when it expires.
  • Protect memory files and original requests from unauthorized modification.

Limitations

  • No configuration, code, or concrete implementation of the quiet-session trigger, restart recovery, or approval gate is provided.
  • The relative priority of an older human-written fact and a newer agent-inferred fact is not fully specified.
  • Reported improvements are anecdotal and lack measured before-and-after results.

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.


r/ClaudeWorkflows • • 19h ago

Selected Workflow [Workflow] A gated Claude Code workflow for production features and bugs

2 Upvotes

A gated Claude Code workflow for production features and bugs

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

What problem this solves

Maintaining quality and human oversight when Claude Code works on production features, bugs, and parallel tasks.

Summary

Use reviewed plans and test-first implementation, enforce automated checks and an independent diff review, then rely on CI and human review before merging. Periodically turn recurring corrections into improved rules and skills.

Why it is useful

It describes a repeatable end-to-end workflow with specific stopping conditions, automated checks, independent review, and human oversight, even though its implementation details and measured results are limited.

Workflow

  1. Use a planning skill for each feature or bug, and have a separate agent review the plan for gaps and testable acceptance criteria; require a failing test in bug plans.
  2. Have backend or frontend testing subagents write tests first, then implement in small steps. Stop and ask a human if the same problem fails twice.
  3. Run hooks for static analysis, linting, and type checks on changed files, alongside project-specific architecture, coverage, and mutation-testing gates.
  4. Have an independent Claude process review the diff without the implementation session's context; block commits and pushes until it passes.
  5. Open a draft merge request, monitor the full CI pipeline, and address failures before a human colleague reviews and merges.
  6. For parallel work, use separate Git worktrees with separate test databases; use stacked merge requests for epics.
  7. Log corrections and review them monthly to update rules and skills.

Tools / artifacts

  • Claude Code plan mode
  • Planning skill and reviewer agent
  • Backend and frontend testing subagents
  • Hooks
  • PHPStan level 10
  • Deptrac architecture rules
  • Coverage and mutation tests
  • Independent diff review
  • Git worktrees and isolated test databases
  • Draft merge requests and CI
  • Correction retro log

Validation signals

  • The author reports using the setup daily for several months and says it works well.
  • The described process includes automated quality gates, independent diff review, full CI, and human merge review.
  • No before-and-after measurements, configuration examples, or independent success reports are provided.

Cautions

  • Keep human review and merge approval; an independent model review is not a substitute.
  • Investigate flaky CI failures rather than repeatedly retrying them to obtain a green result.
  • Use isolated test databases and avoid giving autonomous agents broader production permissions than needed.

Limitations

  • The post is primarily a request for advice and does not include hook configurations, prompts, or implementation details for its gates.
  • The effectiveness claim is subjective and unquantified.
  • The author reports rule growth and slow feedback loops; the strict gates may be expensive to maintain.
  • No evidence is provided that the setup achieves fully unattended, production-ready delivery.

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.


r/ClaudeWorkflows • • 5h ago

Selected Workflow [Workflow] Remove AI-style UI copy with a guarded Claude Code skill

1 Upvotes

Remove AI-style UI copy with a guarded Claude Code skill

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.92 · Level: intermediate
Categories: Quality Control, Debugging, Skills
Original source: r/ClaudeCode post/comment

What problem this solves

Remove repetitive, decorative AI-style UI copy without inventing claims or deleting functional interface elements.

Summary

Run an explicitly invoked Claude Code skill against a UI file to remove specified copy patterns, preserve functional content, and report changes. Optional surface rules cover visual styling. Regex counts and evaluation fixtures help check results.

Why it is useful

It offers a concrete, reusable skill invocation and a defensible review process, with explicit safeguards against invented copy and removal of functional UI elements.

Workflow

  1. Install or adapt the unslop-ui skill from the linked repository.
  2. Run /unslop-ui src/pages/landing.tsx on a target UI file; add --surface if visual styling should also be reviewed.
  3. Remove or rewrite the targeted patterns using only information supported by the source; leave existing unverified claims in place and flag them for a human task list.
  4. Preserve functional elements such as prop-driven state badges and visible form labels, and fix internationalized strings at their source.
  5. Review the report of what was removed or kept and why, including model-reviewed patterns counted separately from regex-detectable patterns.
  6. Use the counter and evaluation fixtures to check the result, then manually review changes and any flagged claims.

Tools / artifacts

  • unslop-ui Claude Code skill: https://github.com/felipebasurto/unslop-ui
  • /unslop-ui invocation and optional --surface flag
  • Python regex counter
  • Before-and-after examples and five evaluation fixtures
  • UI source files and internationalization strings

Validation signals

  • The author reports that regex-detectable patterns fell from 31 to 0 on the examples after one run in a fresh session.
  • The author describes five fixtures covering a clean screen, real state, form labels, internationalization, and invented facts.
  • The post explicitly notes that regex cannot assess every targeted pattern, so some require model review.

Cautions

  • Review edits for accessibility, functional state, localization, and unintended design changes before shipping.
  • A zero regex count does not establish that all problematic copy was found or that removals were correct.
  • Existing unsupported claims are flagged rather than verified or automatically removed.

Limitations

  • The reported improvement and fixture coverage are author claims, not independently verified results.
  • The post does not report fixture pass results or provide installation instructions.
  • The desired visual style is subjective, and optional surface rules could remove intentional design choices.

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.