← ClaudeAtlas

grace-asklisted

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.
createusernam/setup_project · ★ 0 · AI & Automation · score 62
Install: claude install-skill createusernam/setup_project
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