grace-generate
Generate code for the module specified by the user.
Prerequisites
docs/development-plan.xmlmust contain this module's contractdocs/knowledge-graph.xmlmust have this module registered- If either is missing, tell the user to run
$grace-planfirst
Process
Step 1: Load Context
Use the smallest complete context that still preserves contract fidelity.
- In standalone generation, read:
- the target module's entry in
docs/knowledge-graph.xml - all modules it depends on
- the contracts of those dependency modules
- the target module's entry in
- In controller-driven multi-agent generation, treat the controller's execution packet as the primary source of truth
- If the packet already contains the module contract, graph entry, dependency summaries, write scope, and verification command, do not reread the whole plan and graph again
- Read extra local files only when needed to implement the assigned module correctly
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-status
Show the current health status of a GRACE project. Use to get an overview of project artifacts, codebase metrics, knowledge graph health, verification coverage, and suggested next actions.
27grace-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.
27