Skill

grace-ask

Answers questions about GRACE projects by loading artifacts like AGENTS.md and knowledge-graph.xml, navigating modules, and citing code blocks for codebase, architecture, or implementation details.

developer-tools

documentation

npx claudepluginhub osovv/grace-marketplace --plugin grace

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Answer a question about the current GRACE project.

Supporting Assets

agents/openai.yaml

SKILL.md

Similar Skills

grace-status

Shows health status of GRACE projects: artifact existence/versions, codebase metrics like MODULE_CONTRACT coverage and semantic blocks, knowledge graph/verification health, recent changes, suggested actions.

1 file

grace

understand-chat

7.9k

Answers questions about a codebase by querying the knowledge graph at .understand-anything/knowledge-graph.json. Searches nodes, edges, layers for code structure, dependencies, and relationships.

understand-anything

project-conventions

Defines project structure, naming conventions, directory layouts, and three-layer documentation model for consistent codebase organization across skills. Useful for project setup, init, or structure discussions.

6 files

digital-innovation-agents

Stats

Parent Repo Stars92

Parent Repo Forks23

Last CommitApr 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Answer a question about the current GRACE project.

Process

Step 1: Load Project Context

Read the following files (skip any that don't exist):

AGENTS.md — project principles and conventions
docs/knowledge-graph.xml — module map, dependencies, exports
docs/requirements.xml — use cases and requirements
docs/technology.xml — stack, runtime, libraries
docs/development-plan.xml — phases, modules, contracts
docs/verification-plan.xml — tests, traces, log markers, and execution gates
docs/operational-packets.xml — canonical packet, delta, and failure handoff shapes

Step 2: Identify Relevant Modules

Based on the question, find the most relevant modules:

Use the knowledge graph to locate modules related to the question
Follow CrossLinks to find connected modules
Read MODULE_CONTRACTs of relevant modules for detailed context
Read matching verification entries when the question is about behavior, failure modes, or testing

If the optional grace CLI is available, you may use:

grace module find <query> --path <project-root> to resolve module IDs from names, paths, dependencies, or verification refs
grace module show M-XXX --path <project-root> --with verification to pull the shared/public module snapshot
grace file show <path> --path <project-root> --contracts --blocks to pull file-local/private context for the implementation details

Step 3: Dive Into Code If Needed

If the question is about specific behavior or implementation:

Use MODULE_MAP to locate relevant functions/blocks
Read the specific START_BLOCK/END_BLOCK sections
Read function CONTRACTs for intent vs implementation details
Read nearby tests or log-marker assertions when they are the strongest evidence for expected behavior

Step 4: Answer

Provide a clear, concise answer grounded in the actual project artifacts. Always cite which files/modules/blocks your answer is based on.

Important

Never guess — if the information isn't in the project artifacts, say so
If the question reveals a gap in documentation or contracts, mention it
If the question reveals a gap in tests, traces, or verification docs, mention it
If the answer requires changes to the project, suggest the appropriate $grace-* skill