scaffold-new-prototype

To document a code spike, this Skill interactively guides you through defining the prototype's question, hypothesis, build scope, skip scope, and approach, then generates a structured document for your game development experiment.

Tracking experimental code spikes is handled by assigning a unique sequential ID (PROTO-###) to each prototype and automatically registering the new document in a central index for easy tracking and retrieval.

Scaffolding a new prototype document requires you to specify a prototype name; the system then interactively prompts you for the experiment's hypothesis and scope to build out the structured file.

Yes, this scaffolding tool runs entirely without external dependencies, allowing you to quickly instantiate prototype documentation directly within your local environment.

Structured prototype documentation should be used when you need to quickly test a specific game mechanic or technical approach without committing to a full design, ensuring throwaway code experiments are properly scoped.

Creating a new prototype document requires defining the prototype's core question, hypothesis, build scope, skip scope, and technical approach to ensure the code spike has clear boundaries.