quick-design

Name: quick-design
Availability: InStock
Author: NuoYan

Convert small game changes into implementation-ready design specifications.

47|12|Updated Jun 14, 2026

Search Tags:#acceptance criteria #game design #feature scoping #gdd workflow #quick specification #mechanics tuning

Ready to run

npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill quick-design-nuoyanruoshui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quick-design
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/quick-design
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill quick-design-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents small game changes from being implemented without clear scope, rationale, acceptance criteria, or alignment with existing system documentation.

Core Features & Use Cases

Change Classification: Categorizes work as tuning, tweak, addition, or a new small system, and redirects larger changes to full system design.
Context-Aware Specification: Reviews relevant GDDs, system indexes, prior quick specs, and tuning data before drafting requirements.
Implementation-Ready Output: Produces concise quick design specs with rules, affected systems, tuning values, acceptance criteria, and handoff guidance.
Use Case: Use it to document a new parry window, rebalance an enemy patrol speed, or add a small achievement popup without authoring a full game design document.

Quick Start

Use the quick-design skill to create an implementation-ready specification for the requested small game change.

Frequently Asked Questions about quick-design

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

FAQPage Schema

How do I write a design spec for a small game change without a full GDD?▼

A quick specification workflow classifies small game changes like tuning or tweaks, then drafts concise, implementation-ready specs with rules, tuning values, and acceptance criteria without requiring a full GDD.

What is the difference between a quick spec and a full game design document?▼

A quick specification handles small, standalone features, minor mechanics, and behavioral tweaks, whereas a full game design document is required for larger system changes that fall outside the scope of tuning adjustments.

How do I document game mechanics tuning and behavioral tweaks for developers?▼

Document game mechanics tuning by drafting a quick design spec that reviews relevant GDDs, prior specs, and tuning data to produce handoff guidance, affected systems, and specific tuning values for developers.

When do I need to review existing GDDs and dependency indexes before scoping a feature?▼

You need to review existing GDDs, dependency indexes, and data files before drafting a quick specification to ensure the small game change aligns with current system documentation and avoids conflicting dependencies.

How do I define acceptance criteria for minor game mechanics and standalone features?▼

Define acceptance criteria by generating a quick design spec that validates the drafted requirements against relevant tuning data and existing system documentation before obtaining approval and filing the feature.

Does quick-design work for large system overhauls and major game mechanics?▼

No, this quick specification process redirects larger changes that require extensive documentation to a full system design workflow, focusing exclusively on minor mechanics, behavioral tweaks, and standalone features.