quick-design

Generate lightweight design specs for small Y3 gameplay changes.

Updated Apr 4, 2026

Search Tags:#acceptance criteria #game design #balancing #quick spec #story integration #GDD referencing #Y3 Editor

Ready to run

npx skills add https://github.com/WindXRan/y3td --skill quick-design-windxran

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents small gameplay or balancing changes from getting stuck in heavyweight full GDD authoring by producing an appropriately scoped quick rationale and implementation-ready spec.

Core Features & Use Cases

Change classification: Automatically determines whether your update is Tuning, Tweak, Addition, or a New Small System (and redirects to the full design path when it’s too large).
Context-aware drafting: Scans the most relevant GDD sections and prior quick specs to avoid contradictions, and pulls tuning values from the correct data files when applicable.
Implementation-ready outputs: Produces a Quick Design Spec that embeds directly into story files, including clear design delta, affected systems, and measurable acceptance criteria.

Quick Start

Run the quick-design skill with an argument describing the change, and it will draft a quick spec ready to file under design/quick-specs.

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 quick design spec for small Y3 gameplay changes without a full GDD?▼

To write a quick design spec for small Y3 gameplay changes, you use a tool that generates lightweight specifications from YAML metadata. It categorizes your update and outputs an implementation-ready spec with testable acceptance criteria.

What is the best way to document game balancing tweaks and minor behavioral adjustments?▼

Documenting game balancing tweaks is best handled by generating a categorized quick spec instead of a full GDD. This lightweight document provides a clear design delta, affected systems, and measurable acceptance criteria for the tuning adjustments.

When do I need a quick spec instead of a full game design document for Y3 Editor features?▼

You need a quick spec instead of a full game design document when your Y3 Editor feature is small in scope and time-boxed. It applies to tuning adjustments, minor behavioral tweaks, small additions, and standalone features.

How do I generate implementation-ready design specs with testable acceptance criteria?▼

You generate implementation-ready design specs by providing a YAML-defined metadata file containing a required name and description. The system scans relevant GDD sections and prior quick specs to produce a spec with testable acceptance criteria.

Does the quick design spec process check for contradictions with existing GDD references?▼

Yes, the quick design spec process checks for contradictions by scanning the most relevant GDD sections and prior quick specs. It also pulls tuning values from the correct data files when applicable to ensure context-aware drafting.

What happens if my proposed gameplay addition is too large for a lightweight design spec?▼

If your proposed gameplay addition is too large for a lightweight design spec, the change classification process automatically identifies the scope and redirects you to the full GDD authoring path to ensure proper documentation.