grace-ask
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 conventionsdocs/knowledge-graph.xml— module map, dependencies, exportsdocs/requirements.xml— use cases and requirementsdocs/technology.xml— stack, runtime, librariesdocs/development-plan.xml— phases, modules, contractsdocs/verification-plan.xml— tests, traces, log markers, and execution gatesdocs/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
More from osovv/grace-marketplace
grace-explainer
Complete GRACE methodology reference. Use when explaining GRACE to users, onboarding new projects, or when you need to understand the GRACE framework - its principles, semantic markup, knowledge graphs, contracts, testing, and unique tag conventions.
49grace-multiagent-execute
Execute a GRACE development plan in controller-managed parallel waves with selectable safety profiles, verification-plan excerpts, batched shared-artifact sync, and scoped reviews.
30grace-execute
Execute the full GRACE development plan step by step with controller-managed context packets, verification-plan excerpts, scoped reviews, level-based verification, and commits after validated sequential steps.
28grace-status
Show the current health status of a GRACE project. Use to get an overview of project artifacts, codebase metrics, knowledge graph health, verification coverage, and suggested next actions.
27grace-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.
27grace-refresh
Synchronize GRACE shared artifacts with the actual codebase. Use targeted refresh after controlled waves, or full refresh after refactors and when you suspect wider drift between the graph, verification plan, and code.
27