Game Remake Research

Turn an existing game into source-backed remake documentation. Use this skill for remake teardowns, benchmarks, competitor studies, or vertical-slice research packs, not for generic brainstorming or casual comparisons.

Start

• Lock the target game, edition or era, platform set, region, and time slice before writing conclusions.
• If the target is live-service and the user says latest, current, live, today, or similar, browse first and cite exact dates or build windows.
• Treat repo-local GDDs, spreadsheets, and technical docs as target-state inputs, not evidence about the original game.
• Pick one primary archetype lens. Read references/template-selection.md first, then load only one explicit pair unless a secondary lens is clearly required: mmo -> template-mmo.md + metrics-mmo.md, arpg -> template-arpg.md + metrics-arpg.md, roguelike -> template-roguelike.md + metrics-roguelike.md, card -> template-card.md + metrics-card.md.
• Scaffold the output pack before deep research. For packs that will be audited or handed off, pass a concrete --version-scope and usually add --with-support-files.
• Scaffold templates currently support only --language en. Keep the working research pack in English if you still need audit_remake_pack.py, audit_evidence_links.py, build_pack_status_report.py, or build_handoff_bundle.py. If the final deliverable must ship in another language, translate a derived dossier or handoff artifact after the English pack is complete.