grace-ask
npx machina-cli add skill osovv/grace-marketplace/grace-ask --openclawAnswer 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, contracts
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
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
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 answer requires changes to the project, suggest the appropriate
$grace-*skill
Source
git clone https://github.com/osovv/grace-marketplace/blob/main/codex-skills/grace-ask/SKILL.mdView on GitHub Overview
grace-ask answers questions about the current GRACE project by loading full project context, traversing the knowledge graph, and consulting MODULE_MAPs and CONTRACTs to ground replies. It cites the exact files and blocks it used, and flags gaps when documentation is missing.
How This Skill Works
Step 1 loads artifacts: AGENTS.md, docs/knowledge-graph.xml, docs/requirements.xml, docs/technology.xml, and docs/development-plan.xml. Step 2 identifies relevant modules using the knowledge graph and reads MODULE_CONTRACTs. Step 3 dives into code if needed: locate functions via MODULE_MAP, read START_BLOCK/END_BLOCK, and consult CONTRACTs before answering.
When to Use It
- Asked about codebase, architecture, modules, or implementation of the current GRACE project.
- Need answers grounded in actual project artifacts with precise citations.
- Seeking how a module interacts with others via the knowledge graph.
- Verifying behavior or implementation details before making changes or debugging.
- Highlighting gaps or missing documentation in AGENTS/docs files.
Quick Start
- Step 1: Load project context from AGENTS.md, docs/knowledge-graph.xml, docs/requirements.xml, docs/technology.xml, and docs/development-plan.xml.
- Step 2: Use the knowledge graph to identify relevant MODULEs and read MODULE_CONTRACTs.
- Step 3: If needed, drill into code with MODULE_MAP, START_BLOCK/END_BLOCK, and CONTRACTs, then answer with citations.
Best Practices
- Load all listed project context files before answering.
- Ground every claim with citations to files/modules/blocks.
- Do not guess—if artifacts don't contain an answer, say so.
- Cross-reference MODULE_CONTRACTs and MODULE_MAP for accuracy.
- Keep answers concise and actionable for developers.
Example Use Cases
- Q: How does module X implement feature Y? A: Answer grounded in knowledge graph and MODULE_MAP with citations.
- Q: Why does function foo behave this way? A: Refer to START_BLOCK/END_BLOCK and CONTRACTs.
- Q: What are the dependencies of module Z? A: Citations to docs/knowledge-graph.xml and MODULE_CONTRACTs.
- Q: Is there a documented gap in docs/requirements.xml? A: Acknowledge missing content and suggest fixes.
- Q: How should I modify the code to fix Bug 123? A: Cite related artifacts and suggest $grace-* skill changes if needed.
