map-systems

Decompose game concepts into a systems inventory with dependencies and priority ordering.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill map-systems-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-systems
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/map-systems
Command: npx skills add https://github.com/easonlao/jiazi-game --skill map-systems-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents vague game concepts from stalling production by decomposing the idea into a complete set of systems, mapping dependencies, and ordering design work so teams know what to build next.

Core Features & Use Cases

  • Systems decomposition: Enumerates explicit and implicit game systems and organizes them into categories for review.
  • Dependency mapping: Determines which systems must be designed first, identifies bottlenecks and circular dependencies, and prepares a layered build order.
  • Prioritization and index creation: Assigns systems to MVP/Alpha/Full tiers, drafts the systems index, and hands off individual system authoring to the appropriate workflow.

Quick Start

Run map-systems in full mode to create or update the systems index, then choose to design the next highest-priority undesigned system.

Frequently Asked Questions about map-systems

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a game concept into a systems inventory for production?

Systems decomposition for game design enumerates explicit and implicit mechanics, organizing them into structured categories. It converts a vague game concept into an actionable inventory, preventing production stalls by clarifying exactly what mechanics require design work.

How do I map dependencies and prioritize systems for a game design document?

Dependency mapping determines design order by identifying bottlenecks and circular dependencies, creating a layered build order. Systems are then assigned to MVP, Alpha, or Full tiers to establish a clear priority sequence for game design documentation authoring.

What is the best way to turn game design ideas into a build-ready systems plan?

Transforming game ideas into a build-ready systems plan requires decomposing mechanics, mapping dependencies, and assigning priority tiers. This workflow converts early-stage design concepts into a structured systems index, ensuring teams know exactly what to build next.

Do I need existing game concept documents to generate a systems index?

Generating a systems index requires reading design inputs from existing game concept documents. The workflow validates the presence of these design inputs before guiding user approvals through question checkpoints and writing the final systems index file.

When should I not use automated systems decomposition for game design?

Automated systems decomposition is not suited for projects lacking initial game concept documents, as it requires reading design inputs to validate and process. It should be bypassed if your game mechanics are already mapped and dependency-ordered.