Agent use case pack · Games

Tag every decision in your game's log with who made it

by PaperChaseWebb

Thirteen weeks into a fishing and exploration game, a solo developer keeps a Decisions.md with more than 350 entries, each tagged [USER] or [PROPOSED], so the agent knows which choices are settled and which it may revisit.

Preview card for Tag every decision in your game's log with who made it
Works withClaude CodePlain .md
Price
Free
Difficulty
Beginner
Setup
15 min
Format
.md file
Free sample

tag-every-decision-in-your-game-s-log-with-who-made-it.md · 2 KB · direct download, no signup

Download free

What you end up with

An untagged decision log lets an agent treat its own old guesses as your rules.

What you get

  • A plain-language summary of the workflow
  • A fill-in prompt template
  • What to watch out for
  • A link to the original source

Who it is for

Builders who already use AI agents and want a proven workflow they can copy into their own project.

Works with

Claude CodePlain .md

Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.

Tools needed

Claude Codebuilds the game and proposes decisions
Manager sessionplans and hands work to sessions at set effort levels
You needAn AI coding agent or chat model
You needA small real task to try it on

Cost to run: Free with the agent plan you already use.
Time to result: One working session

How it works

  1. Create Decisions.md with one line per decision and a date

    Create Decisions.md with one line per decision and a date

    Expected: Done before you move to the next step.

  2. Tag each line [USER] or [PROPOSED]

    Tag each line [USER] or [PROPOSED]

    Expected: Done before you move to the next step.

  3. Rule: [USER] lines change only when I say so

    Rule: [USER] lines change only when I say so

    Expected: Done before you move to the next step.

  4. Ask the agent to add [PROPOSED] lines whenever it makes a non-obvious

    Ask the agent to add [PROPOSED] lines whenever it makes a non-obvious choice

    Expected: Done before you move to the next step.

  5. Review the proposed lines weekly and promote or remove them

    Review the proposed lines weekly and promote or remove them

    Expected: Done before you move to the next step.

Sample prompt from the pack

Workflow template · Claude Code, Manager session
Apply this workflow to [your project]:
1. Create Decisions.md with one line per decision and a date
2. Tag each line [USER] or [PROPOSED]
3. Rule: [USER] lines change only when I say so
4. Ask the agent to add [PROPOSED] lines whenever it makes a non-obvious choice
5. Review the proposed lines weekly and promote or remove them
Stop and ask me before anything irreversible: deploys, payments, sends or deletes.

Adapted by PaperChaseWebb. Not the original author's prompt.

Free preview of the file

tag-every-decision-in-your-game-s-log-with-who-made-it.md (excerpt)2 KB total
# Tag every decision in your game's log with who made it

PaperChase agent use case (free feed entry), version 1.0. Source: [u/RUSuper on r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/comments/1xgoj4i/week_13_of_making_fishing_and_exploration_game/), 2026-10-27.

## What they did

The developer logs every design and technical decision in one file. Choices they made are tagged [USER] and treated as fixed; choices the agent suggested are tagged [PROPOSED] and can be challenged later. User decisions win any conflict. Work is split across sessions at different effort levels, with one manager session planning and handing tasks out, and the log is how later sessions avoid undoing earlier choices.

## Worth knowing

An untagged decision log lets an agent treat its own old guesses as your rules. One tag per line fixes that. The decision count is the author's.

Worth knowing

  • An untagged decision log lets an agent treat its own old guesses as your rules. One tag per line fixes that. The decision count is the author's.
  • Figures are as reported by the original author and were not re-measured by us.

Questions

Where does this come from?

A public post credited to u/RUSuper on r/ClaudeAI. Source: https://www.reddit.com/r/ClaudeAI/comments/1xgoj4i/week_13_of_making_fishing_and_exploration_game/

Is it free?

Yes. Feed entries are free to read and download.

Details

Version 1.0 · Updated Oct 27, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms

claude-codegame-devdecision-logworkflow