map-systems

Decompose a game concept into systems, map dependencies, and create a prioritized systems index.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a high-level game concept into an actionable design plan is hard: concept documents rarely enumerate every system, hidden dependencies cause design-order mistakes, and teams lack a shared index tracking which systems are designed. This Skill decomposes a game concept into a complete, dependency-sorted, priority-tiered systems index. ## Core Features & Use Cases - Systems Enumeration: Extracts explicit systems from the concept doc and infers implicit ones (e.g., combat implies damage calculation, status effects, combat UI), then validates the list with the user. - Dependency Mapping & Prioritization: Builds a layered dependency graph (Foundation through Polish), detects circular dependencies and bottleneck systems, and assigns MVP/Vertical Slice/Alpha/Full Vision priority tiers. - Systems Index & Handoff: Writes design/gdd/systems-index.md with a progress tracker, then hands off individual system GDD authoring to the /design-system skill. - Use Case: After brainstorming a game concept, run /map-systems to get a full systems breakdown, then run /map-systems next to automatically pick the highest-priority undesigned system and start its GDD. ## Quick Start Ask the AI to run /map-systems to decompose the game concept in design/gdd/game-concept.md into a prioritized systems index.

Frequently Asked Questions about map-systems

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

FAQPage Schema
How do I break down a game concept into individual systems?

Run /map-systems after creating design/gdd/game-concept.md. The skill extracts explicit systems from the concept, infers implicit ones (like save systems behind inventory), and validates the full list with you before writing the index.

How do I decide which game system to design first?

The skill sorts systems into dependency layers (Foundation, Core, Feature, Presentation, Polish) and combines that with MVP priority tiers to produce a design order. Use /map-systems next to automatically pick the highest-priority undesigned system.

What happens if the game concept file is missing?

The skill fails with a clear message telling you to run /brainstorm first to create design/gdd/game-concept.md. The concept document is required context and the decomposition cannot proceed without it.

Does map-systems write the individual system design documents?

No. It owns only the systems index at design/gdd/systems-index.md. Individual system GDDs are authored by the /design-system skill, which map-systems hands off to once you select a system.

Can I update an existing systems index instead of recreating it?

Yes. If design/gdd/systems-index.md already exists, the skill resumes from it, shows current status, and asks whether you want to add new systems, design the next undesigned system, or revise priorities.