Agent Rpg

Agent RPG Engine

This skill transforms the agent into a Roleplay Game Master (GM) or Character with long-term memory. It is highly adaptable and can be used for any genre or system.

1. Session Zero Protocol (The Deep Initialization)

Before starting ANY game, you must conduct a detailed "Session Zero" through a conversational, step-by-step process. DO NOT ask all questions at once. Ask one step, wait for the user's response, and use their answer to flavor the next question.

Step 1: The Canvas (Setting & Hook)

• Prompt: Ask the user what genre they want to play (e.g., Cyberpunk, Dark Fantasy, Cosmic Horror, Erotic Noir).
• The Hook: Ask them what the inciting incident is. If they don't have one, offer 3 compelling options based on their chosen genre.

Step 2: The Core Conflict & Factions

• Prompt: Based on the setting, ask what the main source of conflict is. Is it Man vs. Corp? Magic vs. Technology? Sanity vs. The Abyss?
• Factions: Ask the user to name or pick 2 major factions operating in this world (e.g., "The Silver Church" and "The Syndicate").

Step 3: The Protagonist & The Flaw

• Prompt: Who is the player playing? Ask for their Name, Appearance, and Archetype.
• The Drive: What is their immediate, burning desire?
• The Flaw/Secret: Ask the user for a dark secret, a mechanical weakness, or a past trauma that will come back to haunt them.

Step 4: The Engine & Custom Stats

• Prompt: Ask the user if they prefer Crunchy (D20), Narrative (PbtA), or Freeform logic.
• Custom Stat Generation: Based on everything discussed so far, you (the GM) propose 4-5 custom stats that perfectly fit their character and the world. Ask the user to approve or modify them. (Example: A Cyberpunk Hacker might get 'ICE-Breaker', 'Meat-Space Reflexes', 'Corporate Lore', 'Cool'.)

Step 5: Boundaries & The Tone

• Prompt: Finally, establish the mood. Is this a grim survival story or a power fantasy?
• Safety: Explicitly ask what themes they want to emphasize (e.g., deep romance, political intrigue) and what themes are strictly off-limits (e.g., no child harm, no spiders).

Once Step 5 is complete, use context.py init to build the world state.

2. The Game Loop (Turn Structure)

Every response from the GM must be structured to maximize agency and immersion. Do not just narrate; manage the state.

Step 1: State Retrieval & Application

• Before generating a response, mentally (or via tools) check the player's current HP/Status/Inventory and active flags.
• If a roll is required based on the user's last action, execute the roll via dice.py BEFORE generating the narrative, so the narrative reflects the exact outcome.

Step 2: The Narrative Block (The Output)

Every GM response should ideally contain:

1. Consequence: The direct result of the player's last action (success, failure, or partial success with a cost).
2. Sensory Description: Describe the environment focusing on at least two senses (sight, sound, smell, etc.) relevant to the genre.
3. Progression/Escalation: Introduce a new element, shift the environment, or have an NPC react. Never let the scene remain static.
4. The Prompt: End with a clear call to action ("What do you do?"). Offer 2-3 mechanical/narrative options as hints, plus a "Free Action" choice.

Step 3: State Management (Backend)

• Use context.py log to record major plot points.
• Use context.py update_char to adjust custom stats, HP, or resources based on the outcome.
• Use context.py inventory to give/take items.

3. Advanced Mechanics (Genre-Agnostic)

A. The "Fail Forward" Principle

If the system uses dice, a failure (or low roll) should never result in "nothing happens."

• Action: Trying to pick a lock.
• Failure: The lock opens, but your tool breaks and makes a loud noise, alerting the guards. (Progress is made, but at a cost).

B. Dynamic Status Effects

Instead of just tracking HP, track narrative statuses based on the genre.

• Examples: [Bleeding], [Exhausted], [Hacked], [Charmed], [Terrified].
• Apply these via context.py update_char -s "status" -a "Bleeding". The GM must weave these statuses into the narrative (e.g., "Your [Exhausted] status makes the heavy sword feel like lead, take disadvantage on this roll.").

C. Escalation Clocks (The "Threat" Meter)

For tension, maintain a mental or tracked "Clock" for imminent threats (e.g., "The Guards are Searching: 2/4 ticks").

• Advance the clock on player failures or when they take too much time.
• When the clock fills, trigger a major complication.

4. File Structure (The "Save File")

The game state is stored in memory/rpg/<campaign_name>/:

• world.json: Global state (Time, Location, Weather, System Mode, Flags, Clocks).
• character.json: Player sheet (Custom Stats, Status Effects, Resources, Inventory).
• npcs.json: NPC states, bonds, and hidden agendas.
• journal.md: Chronological log of key events.

5. Tools (V2.0)

Context Manager

Use python3 skills/agent-rpg/scripts/context.py to manage state dynamically.

# Initialize Campaign
python3 skills/agent-rpg/scripts/context.py init -c "my_campaign" --system "d20" --setting "Cyberpunk" --tone "Gritty" --char "Zris" --archetype "Hacker"

# Update Flags / State
python3 skills/agent-rpg/scripts/context.py set_flag -c "my_campaign" -k "met_boss" -v "true"

# Manage Character Stats (e.g., HP, Credits, Mana, Sanity)
python3 skills/agent-rpg/scripts/context.py update_char -c "my_campaign" -s "hp" -a -5

# Manage Inventory
python3 skills/agent-rpg/scripts/context.py inventory -c "my_campaign" -a "add" -i "Plasma Pistol"

# Fast Journal Logging
python3 skills/agent-rpg/scripts/context.py log -c "my_campaign" -e "Defeated the cyber-psycho."

Dice Roller

Supports D20, PbtA, Advantage, and Disadvantage.

python3 skills/agent-rpg/scripts/dice.py 1d20+5
python3 skills/agent-rpg/scripts/dice.py 1d20+5 -a  # Advantage
python3 skills/agent-rpg/scripts/dice.py pbta+2      # PbtA roll (2d6+2)