Skip to content
Skills Library
AI & agents · Learning & explanation

using-gdd

/using-gdd

Use when starting any GDD session - establishes how to find and apply GDD skills.

Licence
MIT
Last repository change
06.07.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when starting any GDD session - establishes how to find and apply GDD skills.

Original author description

Use when starting any GDD session - establishes how to find and apply GDD skills.

How it works

  1. The 1% rule
  2. Red flags - Thought → Reality
  3. Skill priority order
  4. Instruction priority
  5. GDD pipeline flow
Original SKILL.md headings · 74 lines, 679 words
SKILL.md preview
---
name: using-gdd
description: "Use when starting any GDD session - establishes how to find and apply GDD skills."
disable-model-invocation: true
---
<SUBAGENT-STOP>

# Using GDD

This is the bootstrap discipline contract for every Get Design Done session. Read it
first; it tells you how to find and apply the right GDD skill before you act.

## The 1% rule

**If you think there is even a 1% chance a skill might apply, you ABSOLUTELY MUST invoke the skill.**

In GDD, almost every request maps to a pipeline stage - brief, explore, plan, design,
verify - or to a cross-cutting skill (discuss, audit, style, darkmode). When in doubt,
search for and read the skill's body. The cost of reading a skill is trivial; the cost of
free-handing a stage is rework, scope creep, and a broken pipeline state.

## Red flags - Thought → Reality

When you catch yourself thinking any of the following, STOP and check for a skill.

| Thought | Reality |
| --- | --- |
| This is just a simple design question. | Questions are tasks. Check for a skill. |
| I'll just tweak the CSS directly. | Token changes go through the pipeline - check /gdd:design. |
| I already know the codebase, skip explore. | Explore probes connections you haven't re-checked this cycle. |
| This change is too small to plan. | Plan-skipped tasks blow scope per cycle telemetry. Run /gdd:plan. |
| I can write the brief later. | No brief means no shared problem statement - /gdd:brief comes first. |
| The user clearly wants X, I'll skip discuss. | Ambiguity hides here. /gdd:discuss surfaces the real constraint. |
| I'll verify by eyeballing it. | Verification is a stage with criteria - run /gdd:verify, don't guess. |
| It's obviously a dark-mode tweak. | Color-scheme work has its own skill - check /gdd:darkmode. |
| Let me just compare these two designs quickly. | Comparison is an audit task - /gdd:compare has the rubric. |
| This is a one-off, no skill needed. | "One-off" is the most common rationalization in the telemetry. Check anyway. |
| I'll refactor the style tokens by hand. | /gdd:style owns token edits so the pipeline stays consistent. |
| The audit can wait until after I ship. | An un-audited cycle is an unverified cycle - /gdd:audit before close. |

## Skill priority order

When more than one skill could apply, resolve in this order:

1. **Process** - brief / explore / discuss. Establish the problem and context first.
2. **Implementation** - design / style / darkmode. Only after process is settled.
3. **Audit** - verify / compare / audit. Close the loop before declaring done.

Never run an Implementation skill before the Process skills that gate it have produced
their artifact. Never declare a cycle complete without an Audit skill.

## Instruction priority

When instructions conflict, obey this precedence (highest first):

1. **The user's CLAUDE.md** - project- and user-level directives always win.
2. **GDD skills** - the skill body is the source of truth for how a stage runs.
3. **Defaults** - your own general training and habits come last.

If a GDD skill contradicts the user's CLAUDE.md, the CLAUDE.md wins and you flag the
conflict. If your instinct contradicts a GDD skill, the skill wins.

## GDD pipeline flow

The core flow is **Brief → Explore → Plan → Design → Verify**, with branch points:

- **Brief** captures the problem (`/gdd:brief`). Branch: a rough idea can sketch or spike
  off the brief before exploration; a changed problem loops back via `--re-brief`.
- **Explore** scans the codebase and connections (`/gdd:explore`) - even on a familiar
  repo, because connections drift each cycle.
- **Plan** decomposes work into tasks (`/gdd:plan`). Skipping it is the top cause of scope
  blow-up; small tasks still get a plan.
- **Design** implements (`/gdd:design`, with `/gdd:style` and `/gdd:darkmode` as
  implementation peers). Implementation never runs ahead of an approved plan.
- **Verify** checks against criteria (`/gdd:verify`), then `/gdd:audit` / `/gdd:compare`
  close the loop. On pass the cycle completes; on fail it loops back to the failing stage.

`/gdd:discuss` runs alongside any stage to resolve ambiguity before it propagates.

Versions

RepositoryScoreLicence
This page · hegemonart/get-design-done90MIT
hegemonart/get-design-done90MIT

Database snapshot: 13.11.2026 · package version dd1498129307 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100using-superjawn
    Establishes how to find and use skills before any response or action. Use when starting any conversation.
  • 95gdd-list-pins
    Lists pinned skill aliases per harness with their source skill and pin timestamp. Use when you want to see which gdd skills have been pinned as standalone shortcuts and where.
  • 95gdd-list-pins
    Lists pinned skill aliases per harness with their source skill and pin timestamp. Use when you want to see which gdd skills have been pinned as standalone shortcuts and where.
  • 90using-14all
    Use when starting any conversation - establishes how to find and use 14All skills, requiring a skill check before any response, including clarifying questions
  • 100gdd-sync
    Syncs the game design document (docs/GDD.md) and the game code in both directions. Matches the IDs in the GDD's Appendix A sync table against `GDD: <ID>` markers in code to find mismatch, missing and orphan items, aligns values in the given direction (GDD→code or code→GDD), then…
  • 100propagate-design-change
    Finds architecture decisions (ADRs) made stale by a changed GDD and walks through resolving each. Use when the user changed a number or rule in a GDD and asks which ADRs or architecture decisions are now out of date.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.