grace-ask
Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
@osovvInstall SkillDevelopment
Skill
/grace-explainer
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
Claude Code
$ npx -y skills add osovv/grace-marketplace --skill grace-explainer --agent claude-code
Codex
$ npx skills add osovv/grace-marketplace --skill grace-explainer -a codex -y
Cursor
$ npx skills add osovv/grace-marketplace --skill grace-explainer -a cursor -y
Gemini CLI
$ npx skills add osovv/grace-marketplace --skill grace-explainer -a gemini-cli -y
GitHub Copilot
$ npx skills add osovv/grace-marketplace --skill grace-explainer -a github-copilot -y
OpenCode
$ npx skills add osovv/grace-marketplace --skill grace-explainer -a opencode -y
Windsurf
$ npx skills add osovv/grace-marketplace --skill grace-explainer -a windsurf -y
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>
Stats
266
Stars
60
Forks
Maintained
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
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.
26015 skills
Stars on GitHub
Momentum
- stars in total
- 260
Other skills on grace-marketplace.
@osovvInstall Skillgrace-cli
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
@osovvInstall Skillgrace-execute
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized…
@osovvInstall Skillgrace-fix
Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.
@osovvInstall Skillgrace-init
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
@osovvInstall Skillgrace-migrate
Agent-applied GRACE 3 to GRACE 4 migration workflow. CLI validates the result but does not convert or delete files.
@osovvInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about grace-explainer.
- Which coding agents can use grace-explainer?
- grace-explainer installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.