Gdd Compare

Community

hegemonart

gdd-compare

Compute the delta between the `DESIGN.md` baseline (from explore) and the `DESIGN-VERIFICATION.md` result (from verify), reporting per-category score delta, anti-pattern delta (resolved vs new), must-have pass/fail change, and design drift (regressions without covering tasks in `DESIGN-PLAN.md`). Use after `verify` to measure whether a design pipeline cycle actually improved the design. Writes `.design/COMPARE-REPORT.md`. Activates for requests involving diffing a design baseline against verification output, or a before-after design delta.

Overview

Publisher	hegemonart
Repository	`get-design-done`
Skill name	`gdd-compare`
Stars	3
Forks	1
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by hegemonart on GitHub. Read the source before you install it.

Installation

Install the Gdd Compare AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/compare
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/hegemonart/get-design-done.git /tmp/get-design-done
mkdir -p .claude/skills
cp -r /tmp/get-design-done/scripts/skill-templates/compare .claude/skills/gdd-compare

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gdd Compare in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gdd Compare on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gdd Compare is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

gdd-compare - Baseline vs Result Delta

Standalone delta command. Computes the difference between the scan baseline (DESIGN.md) and the verification result (DESIGN-VERIFICATION.md), and flags design drift for any regression not covered by an explicit task in DESIGN-PLAN.md. Writes one artifact: .design/COMPARE-REPORT.md.

For the full step-by-step methodology (score parsing, set arithmetic for anti-patterns, drift-coverage map, screenshot-delta probe, and COMPARE-REPORT.md template), see ./compare-rubric.md. For the cross-skill output discipline (artifact prefix, completion marker, MUST-NOT-write list, connection-probe pattern), see ../../reference/shared-preamble.md#output-contract-reminders and ../../reference/shared-preamble.md#connection-handshake-summary. For the underlying 0–10 category-scoring rubric the delta is computed against, see ../../reference/audit-scoring.md.

Scope

This command is standalone - not a pipeline stage:

Scoped strictly to delta between two existing files (COMP-02): DESIGN.md (baseline, from scan) and DESIGN-VERIFICATION.md (result, from verify).
Does NOT require or implement a snapshot mechanism - multi-run history is deferred to V2-06.
Does NOT mutate any pipeline artifact (DESIGN.md, DESIGN-VERIFICATION.md, DESIGN-SUMMARY.md, DESIGN-CONTEXT.md, DESIGN-PLAN.md, .design/STATE.md).
Writes exactly ONE file: .design/COMPARE-REPORT.md.
Output artifact prefix COMPARE-REPORT is distinct from the pipeline namespace (DESIGN-*.md). No naming conflict.

Pre-Flight Checks (Pitfall 3)

Required files - abort if either is missing:

.design/DESIGN.md missing → "No baseline found. Run /get-design-done scan first."
.design/DESIGN-VERIFICATION.md missing → "No verification result found. Run /get-design-done verify first to produce DESIGN-VERIFICATION.md."

Optional files (graceful degradation if absent):

.design/DESIGN-CONTEXT.md - used for must-have delta. If missing, skip the Must-Have Status section and emit note: "Must-have delta skipped: DESIGN-CONTEXT.md not found."
.design/DESIGN-PLAN.md - used for drift detection. If missing, skip DRIFT flagging and emit note: "Drift detection skipped: no DESIGN-PLAN.md."

Confirm .design/ directory exists. If absent: mkdir -p .design/.

Probe preview connection per ../../reference/shared-preamble.md#connection-handshake-summary (ToolSearch → live call → STATE.md write). Result drives Step 5B (screenshot delta).

Workflow

Parse Category Scores - extract baseline + result score tables, normalize names, flag unmatched. Detail: ./compare-rubric.md#step-1--parse-category-scores.
Compute Score Delta - delta = result - baseline, classify (improvement/no_change/regression). Detail: ./compare-rubric.md#step-2--compute-score-delta-comp-03.
Anti-Pattern Delta - set arithmetic on baseline vs result anti-pattern sets (resolved / new / unchanged). Detail: ./compare-rubric.md#step-3--anti-pattern-delta.
Must-Have Pass/Fail Change - read <must_haves> from DESIGN-CONTEXT.md, status from DESIGN-VERIFICATION.md. Detail: ./compare-rubric.md#step-4--must-have-passfail-change.
Design Drift Detection (COMP-04) - build coverage map from DESIGN-PLAN.md Type: fields; for each regression not in coverage_map → emit DRIFT: [category] .... Detail: ./compare-rubric.md#step-5--design-drift-detection-comp-04.
Screenshot Delta (preview: available only) - capture per-route screenshots to .design/screenshots/{before,after}/<route>.png. Detail: ./compare-rubric.md#step-5b--screenshot-delta-when-preview-available.
Write .design/COMPARE-REPORT.md - full template at ./compare-rubric.md#step-6--compare-reportmd-template.

Constraints

This command MUST NOT (per ../../reference/shared-preamble.md#output-contract-reminders):

Write to DESIGN.md, DESIGN-VERIFICATION.md, DESIGN-SUMMARY.md, DESIGN-CONTEXT.md, DESIGN-PLAN.md, or .design/STATE.md.
Require or implement a snapshot system (V2-06 deferred).
Reinterpret or silently normalize category names that do not match between files - report mismatches in the Notes section.
Invoke design-auditor or any other pipeline agent.
Produce more than one output file: .design/COMPARE-REPORT.md.

Must abort with a clear actionable error message if either input file (DESIGN.md baseline, DESIGN-VERIFICATION.md result) is missing.

Completion

After writing .design/COMPARE-REPORT.md, print a summary:


Compare complete. Improvements: N. Regressions: M. Drift flags: K. See .design/COMPARE-REPORT.md.

Where N = improvement count, M = regression count, K = DRIFT-flag count (0 if drift detection was skipped or no regressions). Do not summarize individual issues - the file contains the full detail.

COMPARE COMPLETE

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

compare-rubric.md7 KB

Frequently asked questions

What does the Gdd Compare AI skill do?

Why use Gdd Compare on TypingMind?

Because you install it once and use it with any model. Gdd Compare is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gdd Compare in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/compare. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Gdd Compare?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gdd Compare?

As many as you like. As long as a model supports skills, you can use Gdd Compare with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gdd Compare AI skill free?

Yes. It is published on GitHub by hegemonart under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Context And Decisions

affaan-m

CommunityPopular

Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require…

Docs Governance

Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks…

Ecc Conventions

Development conventions and patterns for ECC. JavaScript project with conventional commits.

Mcp Dependency Review

affaan-m

CommunityPopular

Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

gdd-compare - Baseline vs Result Delta

Scope

Pre-Flight Checks (Pitfall 3)

Workflow

Constraints

Completion

COMPARE COMPLETE

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now