metaprogression-loop

name	metaprogression-loop
description	Shape between-run or long-term progression with unlocks, retention beats, reset value, and pacing. Use for roguelites, service games, or multi-session arcs.

Metaprogression Loop

When to use

Shape between-run or long-term progression with unlocks, retention beats, reset value, and pacing. Use for roguelites, service games, or multi-session arcs.

Inputs to gather

• run/session structure
• unlock model
• power curve
• player return reasons

Recommended roles

• progression_designer
• systems_designer
• economy_designer

Primary docs / outputs

• studio/docs/templates/economy-tuning.md
• studio/docs/templates/feature-brief.md

Workflow

1. Inspect the current repo/docs state first and cite concrete evidence.
2. Choose the smallest useful output that moves the project forward.
3. Express the work as a feature, mechanic, or content contract that engineering and QA can consume.
4. Update or create durable docs when the result should persist.
5. Recommend the next best role or skill if more work remains.

Category rules

• Lead with player outcome, then define scope, acceptance criteria, and edge cases.
• Keep mechanics and content contracts buildable by engineering and testable by QA.
• Surface tradeoffs among clarity, depth, scope, and production cost.

Deliverables

• meta loop brief
• unlock cadence
• retention hooks
• balance watchlist

Validation bar

• acceptance criteria present
• risks/dependencies surfaced
• next implementation or test path clear