From grace
Shows health status of GRACE projects: artifact existence/versions, codebase metrics like MODULE_CONTRACT coverage and semantic blocks, knowledge graph/verification health, recent changes, suggested actions.
npx claudepluginhub osovv/grace-marketplace --plugin graceThis skill uses the workspace's default tool permissions.
Show the current state of the GRACE project.
Answers questions about GRACE projects by loading artifacts like AGENTS.md and knowledge-graph.xml, navigating modules, and citing code blocks for codebase, architecture, or implementation details.
Synthesizes project docs and codebase into roadmap status, gaps analysis, blockers, risks, and next actions. Use for health checks, progress tracking, and milestone planning.
Detects project type, tech stack, AIWG phase status, team config, git activity, blockers, and risks from .aiwg files and repo. Summarizes context and recommends next actions.
Share bugs, ideas, or general feedback.
Show the current state of the GRACE project.
Check existence and version of:
AGENTS.md — GRACE principlesdocs/knowledge-graph.xml — version and module countdocs/requirements.xml — version and UseCase countdocs/technology.xml — version and stack summarydocs/development-plan.xml — version and module countdocs/verification-plan.xml — version and verification entry countdocs/operational-packets.xml — optional packet template versionScan source files and report:
Quick check:
If the optional grace CLI is available, you may also run grace lint --path <project-root> as a fast integrity snapshot and include any relevant findings in the report.
When the report needs focused navigation instead of raw artifact dumps, you may also use:
grace module find <query> --path <project-root> to resolve the relevant module from names, IDs, dependencies, or changed pathsgrace module show M-XXX --path <project-root> --with verification for the shared/public module snapshotgrace file show <path> --path <project-root> --contracts --blocks for the file-local/private markup snapshotList the 5 most recent CHANGE_SUMMARY entries across source and substantive test files.
Based on the status, suggest what to do next:
$grace-plan"$grace-verification"$grace-execute or $grace-multiagent-execute"$grace-refresh"grace lint --path <project-root>"grace module show M-XXX --path <project-root> --with verification or grace file show <path> --path <project-root> --contracts --blocks"$grace-verification"