quick-design

Draft Quick Design Specs for small game or product changes.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill quick-design-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-design
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/quick-design
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill quick-design-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn small, well-scoped changes into a written Quick Design Spec instead of spending time authoring a full design document. It is built for changes that are important enough to document, but too small to justify heavyweight system-level planning.

Core Features & Use Cases

  • Change classification: Separates tuning, tweaks, additions, and new small systems so the right spec shape is used from the start.
  • Context-aware drafting: Routes between game and product workflows, then scans the relevant design and policy context before writing.
  • Approval-first workflow: Produces a ready-to-review spec, asks for permission before writing files, and flags when a change has grown beyond quick-spec scope.
  • Use case: A product owner wants a small CLI flag change, or a designer wants a minor balance adjustment, and needs a crisp implementation-ready spec without opening a full CDD effort.

Quick Start

Ask the quick-design skill to classify your small change and draft a Quick Design Spec for it.

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 design document?

To write a design spec for a small game change without a full design document, use a quick-spec workflow to classify the change and draft lightweight implementation-ready notes. This approach skips heavyweight system-level planning while still satisfying context scanning and handoff requirements.

What is the best way to document minor product API and config tweaks?

The best way to document minor product API and config tweaks is to draft a Quick Design Spec that applies an approval-first workflow. This method scans relevant policy context and produces a ready-to-review spec tailored for small workflow and config adjustments.

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

You need a quick design spec instead of a full CDD when handling tuning, tweaks, additions, or small standalone systems that are important enough to document but too small to justify heavyweight system-level planning. It separates change types to apply the right spec shape immediately.

How does change classification work for lightweight spec drafting?

Change classification for lightweight spec drafting works by separating tuning, tweaks, additions, and new small systems before writing begins. This routing ensures the correct game or product workflow is applied and the relevant design context is scanned for precise spec drafting.

What happens if a small product change outgrows a quick-spec workflow?

If a small product change outgrows a quick-spec workflow, the drafting process flags that the change has moved beyond quick-spec scope. It maintains an approval-first workflow by asking for permission before writing files, ensuring complex changes are redirected to full design documents.

Can I use quick-design for game balance adjustments and CLI flag changes?

Yes, you can use quick-design for game balance adjustments and CLI flag changes. It routes context-aware drafting between game and product workflows to generate crisp, implementation-ready specs for both minor game tuning and small product CLI modifications.