mcpField
G
grace-ask

grace-ask

github.com/osovvDevelopment25637 installsUpdated 5w ago
Repository

About grace-ask

grace-ask is a skill for answering questions about GRACE project requirements, architecture, verification, and active changes. It checks routed project artifacts, cites supporting anchors, and distinguishes current state from change intent.

Key features

  1. 01Inspect context and graph documents
  2. 02Trace verification coverage
  3. 03Review active change artifacts
  4. 04Cite evidence for key claims
  5. 05Report uncertainty and safe next lookup

Use cases

  1. 01Answer questions about project requirements and design
  2. 02Check which modules own graph elements
  3. 03Distinguish current behavior from proposed changes

Install

Copy the command and run it in a terminal.

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

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

Bundled filesagents/openai.yaml

Details

From the project README
1. `.grace/context/*.xml` for requirements, technology, principles, deployment, and UX constraints. 2. `.grace/graph/index.xml` then routed graph documents for `M-*` and `DF-*` ownership. 3. `.grace/verification/index.xml` then routed verification documents for `V-M-*` coverage. 4. `.grace/changes/active/C-*` for in-flight approved or draft work. 5. File-local `MODULE_CONTRACT`, `MODULE_MAP`, `LINKS:`, `START_CONTRACT`, and `START_BLOCK_` anchors.

<answer_rules>

  • Cite the artifact or anchor that supports each important claim.
  • Distinguish durable current state from active change intent.
  • If legacy GRACE 3 docs are present, explain that they require grace-migrate and are not GRACE 4 truth.
  • Do not invent missing graph or verification facts; report uncertainty and the safest next lookup. </answer_rules>

Comments

Markdown supported