quick-design

Generate lightweight Quick Design Specs for small game changes.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill quick-design-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-design
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/quick-design
Command: npx skills add https://github.com/scomofo/dragon-forge --skill quick-design-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

quick-design helps teams avoid slowing down small but important gameplay changes by skipping full GDD authoring when a system GDD already exists or the change is too minor to justify a heavyweight document.

Core Features & Use Cases

  • Classify the change quickly (Tuning, Tweak, Addition, or New Small System) so the output matches the right level of rigor.
  • Scan existing design context to find the most relevant GDD references and detect conflicts with prior quick specs.
  • Generate a ready-to-embed Quick Design Spec that includes precise replacement rules and acceptance criteria for implementation and story linkage.

Quick Start

Run quick-design with a one-line description of the change so it can classify, draft, and (after approval) write the Quick Design Spec into design/quick-specs with today’s date.

Frequently Asked Questions about quick-design

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

FAQPage Schema
How do I write lightweight game design specs for minor tuning changes without a full GDD?

Lightweight game design specs for minor tuning changes are produced by generating a Quick Design Spec that classifies the change and embeds directly into story files. This avoids full GDD overhead for small adjustments like tuning or behavioral tweaks.

What is a quick design spec used for in game development?

A quick design spec documents small game changes like tuning adjustments, minor behavioral tweaks, or small mechanics additions. It provides precise replacement rules and acceptance criteria for implementation while preventing heavyweight documentation overhead.

How do I draft design documentation for small gameplay additions quickly?

Drafting design documentation for small gameplay additions quickly involves classifying the change type, scanning existing GDD references for conflicts, and generating a ready-to-embed spec with acceptance criteria in the quick-specs directory.

Can I embed quick specs directly into story files for story handoff?

Yes, quick specs can embed directly into story files to support context scanning and story handoff. The generated Quick Design Spec includes YAML frontmatter metadata and provides acceptance criteria for implementation linkage.

When should I avoid using a full game design document and use a quick spec instead?

You should use a quick spec instead of a full game design document when a system GDD already exists or the change is too minor to justify heavyweight documentation. This applies to tuning adjustments, minor behavioral tweaks, and small standalone systems.

Does the quick design spec format support scanning existing GDD references for conflicts?

Yes, the quick design spec format supports scanning existing design context to find relevant GDD references and detect conflicts with prior quick specs. This ensures new tuning adjustments or mechanical tweaks align with established documentation.