game-start

Run the project state detection first to confirm the project is empty, then choose an engine and scaffold the recommended directory layout with design, docs, src, assets, tests, and production folders. Starter documents like a concept doc and TODO list are generated alongside the structure.

The Skill detects a mature or in-progress project by scanning source files, git history, and documentation. It then performs an architecture audit, rates documentation coverage, counts TODOs and FIXMEs, and produces an orientation report with prioritized actions.

For 2D pixel art, Godot is lightweight and fast to prototype. Unity offers the broadest ecosystem and learning resources, while Unreal targets high-end 3D visuals. The Skill recommends the engine your team already knows, since switching engines mid-project is a common failure cause.

Yes, detection falls back to file-system signals like engine project files, source file counts, and docs directories when git history is unavailable. Fields such as project age and contributors simply report as unknown rather than blocking the workflow.

At minimum a game concept document, a technical architecture note with engine rationale, and a task tracking file such as TODO.md. The Skill generates these as starter documents during scaffolding and flags missing sections against the eight required GDD sections.

Do not use it for brainstorming game ideas or prototyping mechanics, since those belong to dedicated brainstorm and prototype workflows. It is designed for project setup, state assessment, and structural health checks, not creative ideation.