Skill
grace-ask
Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
@osovvView SkillDevelopment
Skill
/grace-explainer
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
Install
$ npx -y skills add osovv/grace-marketplace --skill grace-explainer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/grace-explainer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
SKILL.md
grace-explainer.SKILL.mdname: grace-explainer description: Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
<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>
Ships withgrace-marketplace
GRACE means Graph-RAG Anchored Code Engineering: a contract-first AI engineering methodology built around semantic markup, .grace XML artifacts, knowledge-graph navigation, assertions, scopes, and log-driven verification.
Get the whole plugin
Stats
245
Stars
55
Forks
Active
Maintenance
TypeScript
Language
MIT
License
13d ago
Last commit
7mo ago
Created
Repo: osovv/grace-marketplace
Other skills on grace-marketplace.
@osovvView SkillSkill
grace-cli
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
@osovvView SkillSkill
grace-execute
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
@osovvView SkillSkill
grace-fix
Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.
@osovvView SkillSkill
grace-init
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
@osovvView SkillSkill
grace-migrate
Agent-applied GRACE 3 to GRACE 4 migration workflow. CLI validates the result but does not convert or delete files.
@osovvView Skill