Agent skill

grace-ask

Answer a question about a GRACE project using full project context. Use when the user has a question about the codebase, architecture, modules, or implementation — loads all GRACE artifacts, navigates the knowledge graph, and provides a grounded answer with citations.

View SKILL.md on GitHub Repository
Stars 120
Forks 30

Install this agent skill to your Project

npx add-skill https://github.com/osovv/grace-marketplace/tree/main/plugins/grace/skills/grace/grace-ask

SKILL.md

Answer a question about the current GRACE project.

Process

Step 1: Load Project Context

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

  1. AGENTS.md — project principles and conventions
  2. docs/knowledge-graph.xml — module map, dependencies, exports
  3. docs/requirements.xml — use cases and requirements
  4. docs/technology.xml — stack, runtime, libraries
  5. docs/development-plan.xml — phases, modules, contracts
  6. docs/verification-plan.xml — tests, traces, log markers, and execution gates
  7. 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:

  1. Use the knowledge graph to locate modules related to the question
  2. Follow CrossLinks to find connected modules
  3. Read MODULE_CONTRACTs of relevant modules for detailed context
  4. 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:

  1. Use MODULE_MAP to locate relevant functions/blocks
  2. Read the specific START_BLOCK/END_BLOCK sections
  3. Read function CONTRACTs for intent vs implementation details
  4. 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

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

osovv/grace-marketplace

grace-verification

Design and enforce testing, traces, and log-driven verification for a GRACE project. Use when modules need stronger automated tests, execution-trace checks, or a maintained verification-plan.xml that autonomous and multi-agent workflows can trust.

120 30
Explore
osovv/grace-marketplace

grace-refactor

Refactor GRACE-governed code safely: rename, move, split, merge, or extract modules while keeping contracts, graph, verification, and semantic markup synchronized.

120 30
Explore
osovv/grace-marketplace

grace-fix

Debug an issue using GRACE semantic navigation. Use when encountering bugs, errors, or unexpected behavior - navigate through the graph, verification plan, and semantic blocks to analyze the mismatch and apply a targeted fix.

120 30
Explore
osovv/grace-marketplace

grace-cli

Operate the optional `grace` CLI against a GRACE project. Use when you want to lint GRACE artifacts, resolve modules from names or file paths, inspect shared/public module context, or inspect file-local/private markup through `grace lint`, `grace module find`, `grace module show`, and `grace file show`.

120 30
Explore
osovv/grace-marketplace

grace-plan

Run the GRACE architectural planning phase. Use when you have requirements and technology decisions defined and need to design the module architecture, create contracts, map data flows, and establish verification references. Produces development-plan.xml, verification-plan.xml, and knowledge-graph.xml.

120 30
Explore
osovv/grace-marketplace

grace-reviewer

GRACE integrity reviewer. Use for fast scoped gate reviews during execution, or full integrity audits at phase boundaries and after broader code, graph, or verification changes.

120 30
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results