---
name: Grace Explainer
slug: grace-explainer
category: AI Engineering
description: Grace Explainer explains the GRACE 4 project model, `.grace` artifacts, semantic anchors, and the change lifecycle. Use it when you need to understand verification, migration boundaries, or how GRACE files are organized.
github: "https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-explainer"
language: TypeScript
stars: 239
forks: 54
install: "npx degit https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-explainer ~/.claude/skills/grace-explainer"
installs_to: ~/.claude/skills/grace-explainer
source_path: skills/grace/grace-explainer/SKILL.md
collection_size: 15
category_size: 2793
collection_url: "https://dirskills.com/collections/osovv/grace-marketplace"
added: 2026-09-03T06:03:51.812Z
last_synced: 2026-09-03T06:03:51.812Z
canonical_url: "https://dirskills.com/skills/grace-explainer"
---

# Grace Explainer

Grace Explainer explains the GRACE 4 project model, `.grace` artifacts, semantic anchors, and the change lifecycle. Use it when you need to understand verification, migration boundaries, or how GRACE files are organized.

**Install:**

```bash
npx degit https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-explainer ~/.claude/skills/grace-explainer
```

## README

<skill>
<core_model>
GRACE 4 uses `.grace` as the durable project model:

- `.grace/context` stores requirements, technology, principles, deployment, and UX constraints.
- `.grace/graph` stores graph indexes and routed graph documents with `GD-*`, `M-*`, and `DF-*` tags.
- `.grace/verification` stores verification indexes and routed `V-M-*` entries.
- `.grace/changes` stores active and archived `C-*` change bundles with `GraceChangeSpec`, optional non-normative design context, and `GraceChangePlan`.
</core_model>

<workflow>
1. `grace-init` creates the `.grace` skeleton.
2. `grace-spec` creates an active change spec and waits for approval.
3. `grace-plan` creates assertions, scopes, and `T-*` implementation tasks.
4. `grace-execute` runs sequential or parallel-safe mode from the approved plan.
5. `grace lint` and `grace status` provide validation and health evidence.
6. Existing GRACE 3 projects use `grace-migrate`; the CLI validates the result but does not convert legacy docs directly.
</workflow>
</skill>