r/ClaudeWorkflows • u/ClaudeAI-mod-bot • 10h ago
Selected Workflow [Workflow] Repository handoffs and review gates for a stateless asset-making agent
Repository handoffs and review gates for a stateless asset-making agent
Workflow value: 78/100
Status: active · Freshness: 70/100 · Confidence: 0.94 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping, CLAUDE.md
Original source: r/ClaudeCode post/comment
What problem this solves
Give a stateless asset-making agent consistent project knowledge and review criteria without relying on session memory or duplicating decisions across documents.
Summary
Organize versioned repository documents by ownership, use a root handoff to select required reading, and run each asset through a documented creation and human-review process.
Why it is useful
It provides a concrete, adaptable way to give agents scoped project knowledge and evaluate creative output against documented standards and approved examples, while keeping a human decision gate.
Workflow
- Create a root handoff that maps work types to the documents agents should read.
- Maintain short repository-wide rules in AGENTS.md, including safety, architectural boundaries, and work-landing conventions.
- Separate the model-making method, art direction, decision register, specifications, budgets, shared-library guidance, and engine asset contract into owned documents.
- For every task, read the repository rules, model method, art direction, and issue; load other documents as the brief requires.
- Consult approved models, review notes, and captures as concrete quality references, and read earlier attempts for functional requirements rather than copying their implementation.
- Follow the model method: brief and written design, build in code, inspect each round, integrate into the game, and obtain independent review and a blind lineup.
- Require a human verdict before landing, and keep the model README status and relevant decision records current.
Tools / artifacts
- AGENTS.md
- Root handoff file
- model-method.md
- art-direction.md
- Domain decision register and index
- Building specification cards
- model-budgets.md
- Shared materials and goods library READMEs
- Engine asset contract
- Reference model source, review notes, and captures
- Task issue and model README
Validation signals
- The described process calls for inspection at fixed camera distances and comparison against approved reference models.
- It includes independent review, a blind lineup, and a human verdict before landing.
- The comment describes an established document structure and task-specific reading rules, but reports no measured outcomes or completed example.
Cautions
- The stated repository rules prohibit committing secrets or writing to real player save folders during tests.
- Independent review and a human landing decision provide oversight, although the comment does not specify how review independence is enforced.
Limitations
- No repository, document templates, or runnable implementation is provided.
- No before-and-after result, test evidence, or community success report is supplied.
- The blind-lineup procedure and enforcement of document freshness and ownership are not specified.
- The workflow is not explicitly Claude-specific; AGENTS.md may need adaptation to the user's Claude Code setup.
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.