grace-status
Show the current state of the GRACE project, including whether it is safe to hand to a longer autonomous run.
When the optional CLI is available, prefer grace status --path <project-root> for the initial report. Use grace status --with modules --path <project-root> when project-level health is not enough and you need module summaries before deeper investigation.
Report Contents
1. Artifacts Status
Check existence and version of:
-
AGENTS.md— GRACE principles -
docs/knowledge-graph.xml— version and module count -
docs/requirements.xml— version and UseCase count -
docs/technology.xml— version and stack summary -
docs/development-plan.xml— version and module count -
docs/verification-plan.xml— version and verification entry count -
docs/operational-packets.xml— optional packet template version
2. Codebase Metrics
Scan source files and report:
- Total source files
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-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.
27grace-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, map data flows, and establish verification references. Produces development-plan.xml, verification-plan.xml, and knowledge-graph.xml.
27