quick-design

Draft a Quick Design Spec for small changes with acceptance criteria.

Updated Apr 8, 2026

Search Tags:#design #documentation #software-design #change-management #gdd #quick-spec

Ready to run

npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill quick-design-hechaoyannet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quick-design
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/quick-design
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill quick-design-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This quick design path eliminates the need for full GDD authoring for small changes by producing a concise design spec that fits directly into existing story files.

Core Features & Use Cases

Lightweight: Produces a compact spec when a full GDD would be overkill.
Direct Integration: Embeds into existing story files for easy reference.
Governance: Keeps consistency with the design system by reusing existing terminology and structure.

Quick Start

Generate a quick design spec for the specified small change.

Frequently Asked Questions about quick-design

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

FAQPage Schema

When do I need a quick design spec instead of a full GDD?▼

You need a quick design spec when a change is too small to warrant a full GDD. It produces a concise document capturing type, scope, and acceptance criteria for small software-design modifications.

How do I draft design documentation for small changes?▼

To draft design documentation for small changes, analyze the design context and prior specs to ensure consistency. This generates a compact spec that embeds directly into existing story files under design/quick-specs.

Does generating a quick design spec prevent cross-system conflicts?▼

Yes, generating a quick design spec prevents cross-system conflicts. It analyzes relevant design context and prior specs to ensure consistency, reusing existing terminology and structure from the design system.

What is the best way to maintain governance for small software-design changes?▼

The best way to maintain governance for small software-design changes is generating a lightweight spec that reuses existing terminology and structure. This ensures consistency and prevents cross-system conflicts without overhead.

Can I embed quick specs directly into existing story files?▼

Yes, you can embed quick specs directly into existing story files. This direct integration provides easy reference for small changes, outputting a ready-to-file document under the design/quick-specs directory.