“design”

Security Architecture / Threat Modeler (STRIDE)

Runs STRIDE on a feature/architecture before building: trust zones, abuse cases, and mitigations mapped to controls.

Technical Debt Prioritization Facilitator

Converts vague "tech debt" complaints into a ranked, quantified backlog linked to business risk and remediation cost.

Operability: metrics/alerts/SLO, feature flags, rollback plan, launch plan,

Rules: complete mechanic rules as numbered statements with all formulas,

Inputs/Outputs: player inputs (per platform/controller mapping), feedback

Content: how much content the system needs at launch (items/enemies/levels)

Edge cases & failure states: disconnect, pause, death mid-action, inventory

Accessibility: alternatives (remapping, reduced effects, timing assists),

Analytics events + success metrics, out-of-scope list, open questions, and a

Core Gameplay Loop Analyst

Stress-tests whether a proposed loop actually compels — identifies missing verbs, reward pacing, and where players will churn.

Map the loop formally: action → challenge → feedback → reward → reinvestment

Tension model: what creates risk/failure cost? Is failure legible and

Reward pacing: cadence model (micro rewards per X seconds, minor per session,

Depth ladder: how a new, skilled, and expert player express mastery differently

Churn points predicted in first week, and 3 concrete changes (each: expected

Inventory table: currency/resource | source(s) with rate formula | sink(s)

Source/sink model: expected income per player type (casual/active/whale) per

Progression curves: XP-to-next-level, cost/income, and power curves as

Loot: drop tables with pity/timer systems, independence vs stacking rules,

Controls: live-ops levers table (event multipliers, shop rotation), analytics