osovv/grace-marketplace Skills

Add a new module to a GRACE project with contract and knowledge graph entry. Use when you need to introduce a new module that wasn't part of the original plan — designs the contract, updates planning artifacts, generates code, and verifies integration.

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.

Execute the full GRACE development plan step by step, generating code for each pending module with validation and commits. Use when the architecture is planned and you want to generate all modules sequentially with review checkpoints.

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, and unique tag conventions.

Debug an issue using GRACE semantic navigation. Use when encountering bugs, errors, or unexpected behavior — navigates the knowledge graph to locate the relevant module, traces to the specific semantic block, analyzes the mismatch between contract and implementation, and applies a targeted fix.

Generate code for a specific GRACE module with full semantic markup. Use when a module has been planned and contracted in development-plan.xml and you need to generate the actual implementation code with MODULE_CONTRACT, MODULE_MAP, semantic blocks, and knowledge graph updates.

Bootstrap GRACE framework structure for a new project. Use when starting a new project with GRACE methodology — creates docs/ directory, AGENTS.md, and XML templates for knowledge graph, requirements, technology, and development 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, and build the knowledge graph. Produces development-plan.xml and knowledge-graph.xml.

Synchronize the GRACE knowledge graph with the actual codebase. Use after manual code changes, refactoring, or when you suspect drift between the knowledge graph and the code — scans all source files, detects missing/orphaned modules and stale CrossLinks, and proposes fixes.

GRACE integrity reviewer. Use when validating semantic markup correctness, contract completeness, knowledge graph consistency, or after code changes to ensure GRACE conventions are maintained.

Show the current health status of a GRACE project. Use to get an overview of project artifacts, codebase metrics, knowledge graph health, and suggested next actions — helps identify drift, missing contracts, or unpaired semantic blocks.