mcpbeat

Grace Explainer

osovv/grace-marketplace-grace-explainer

Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.

This is a copy. The original lives at osovv/grace-explainer.

6k tokens
context cost
the whole folder, loaded on every use
7
files
instructions only
0
copies elsewhere
how many repositories repackaged it
231
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/osovv/grace-marketplace --skill grace-explainer

The instruction itself

as written by the author

<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>

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

</workflow>

</skill>

How to use it

Copy the folder

Take osovv/grace-marketplace-grace-explainer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.