# Small documents your AI can keep for you
Ask the AI to create/update these only in your approved practice workspace. If it cannot write files, ask for text you can save. The documents record facts and decisions; they do not grant new access or override your current instructions.

## PROJECT_BRIEF.md
Game idea in my words:
Player action / objective / challenge:
Mood, references and what each reference means:
First edition / excluded ideas:
Tools/version / spending limit:
Approved decisions / unresolved questions:

## WORKING_AGREEMENT.md
Who chooses direction and who implements:
Intake completion cue:
When to act independently / when to ask:
Update style and useful proof:
Muted audio / accessibility preferences:
Working-version and rollback rule:

## HANDOFF.md
Current milestone:
Exact working project/version:
What was changed:
Checks actually run and results:
What remains untested:
First exact error or issue:
Next small action:
Relevant file/reference paths:

## ASSET_REGISTER.md
Asset title / creator / original item URL:
License/version / download date / retained license file:
Commercial use / required credit / redistribution conditions:
Modifications / where used:
Unclear rights to resolve before integration:

## CHANGE_REQUEST.md
Target or screenshot location:
What happens now:
What I want instead:
What should stay consistent:
How we will tell it worked:
These labels are a learning scaffold. You can speak naturally once the shared context is clear.