mcpField
G
grace-explainer

grace-explainer

github.com/osovvDevelopment25661 installsUpdated 5w ago
Repository

About grace-explainer

A skill for working with GRACE 4 projects through their `.grace` project model and CLI workflow. It covers project setup, change specification and planning, execution, validation, status checks, and migration from GRACE 3.

Key features

  1. 01Initialize `.grace` structure
  2. 02Create change specs and plans
  3. 03Execute approved implementation plans
  4. 04Run lint and status checks
  5. 05Migrate GRACE 3 projects

Use cases

  1. 01Setting up a GRACE 4 project
  2. 02Preparing a change for approval and execution
  3. 03Checking project validation and health
  4. 04Migrating an existing GRACE 3 project

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/osovv/grace-marketplace --skill grace-explainer

After installing, type/grace-explainerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
contract-driven-dev.md
knowledge-graph.md
semantic-markup.md
unique-tag-convention.md
verification-driven-dev.md

Details

From the project README
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>
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.

Comments

Markdown supported