quick-design

Generate dated markdown Quick Design Specs for small gameplay or XR changes.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill quick-design-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-design
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/quick-design
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill quick-design-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The quick-design skill solves the problem of overbuilding or delaying changes by letting you capture intent and rules for small XR/game updates without writing a full GDD.

Core Features & Use Cases

  • Lightweight spec authoring: Produces a Quick Design Spec for changes that are too small for full GDD authoring (about 4 hours of implementation).
  • Change classification & guardrails: Guides you to classify the change as Tuning, Tweak, Addition, or New Small System and redirects to design-system when scope grows.
  • Context scanning & conflict avoidance: Checks the relevant existing GDD, systems index (if present), and previous quick specs to avoid contradictions.
  • Structured acceptance criteria: Writes testable acceptance criteria and, when needed, clearly flags whether a GDD update requires separate approval.

Quick Start

Run quick-design with a brief description of the change you want to make so it generates a new design/quick-specs specification you can reference in your story.

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 minor gameplay tweak without a full game design document?

A Quick Design Spec captures intent, rules, and testable acceptance criteria for small gameplay changes taking roughly 4 hours to one week, preventing overbuilding or delaying updates that do not justify full GDD authoring.

What's the best way to document small XR system adjustments for rapid implementation?

The best way to document small XR system adjustments is generating a dated markdown Quick Design Spec with structured acceptance criteria, which clearly defines scope and optionally flags whether a GDD update requires separate approval.

When should I write a quick design spec instead of updating the full game design document?

You should write a quick design spec instead of updating the full GDD when handling tuning adjustments, minor tweaks, small additions, or standalone new small systems that require roughly 4 hours to one week of implementation time.

Does quick-design check existing GDD context to avoid contradictions when adding new systems?

Yes, it scans relevant existing GDDs, systems indexes, and previous quick specs to avoid contradictions, ensuring your new lightweight design spec aligns with established game development documentation and prior tuning adjustments.

How do I classify gameplay changes to determine if they need full GDD authoring or a lightweight spec?

You classify gameplay changes into Tuning, Tweak, Addition, or New Small System categories to determine if a lightweight spec suffices, with built-in guardrails redirecting you to full GDD authoring if the scope grows beyond small additions.