osovv/grace-marketplace

Grace Ask answers questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup. It cites the artifacts and anchors that support each claim and distinguishes current state from active change intent.

Grace CLI operates the GRACE 4 command-line tools for linting, status checks, module and verification navigation, and file-local semantic markup. Use it to validate project baselines, run declared commands, and inspect GRACE records.

Grace Execute runs an approved GRACE GraceChangePlan in sequential or parallel-safe mode with preflight checks, recovery handling, and centralized durable apply. Use it when executing a validated plan and reconciling state after observed work.

Grace Explainer explains the GRACE 4 project model, `.grace` artifacts, semantic anchors, and the change lifecycle. Use it when you need to understand verification, migration boundaries, or how GRACE files are organized.

Grace Fix debug and fix issues in a GRACE 4 project using semantic navigation, assertions, and verification evidence. It starts from a failure or user report, then checks graph anchors, contracts, and tests before making the smallest safe fix.

Grace Init bootstraps a GRACE 4 project by creating the canonical .grace context, graph, verification, and changes folders from templates. Use it when starting a new project or setting up GRACE artifacts for the first time.

Grace Migrate guides a copy-and-validate workflow for moving a project from GRACE 3 to GRACE 4. It inventories legacy sources, prepares migration reports, and validates the result before any cleanup is approved.

Grace Plan converts an approved GraceChangeSpec into a draft GraceChangePlan with assertions, scopes, tasks, and verification gates. Use it before implementation to define the work and check preflight state.

Grace Refactor updates GRACE-governed code during renames, moves, splits, merges, and extractions while keeping graph, verification, and file-local anchors in sync. Use it when refactoring code with .grace artifacts and scope checks.

Grace Refresh detects drift between code, tests, and durable GRACE 4 state in .grace context, graph, and verification files. Use it to report stale or missing anchors and propose reconciliation changes.

Grace Reviewer checks GRACE 4 artifacts for routing, scopes, assertions, anchors, and verification evidence. Use it to review active changes and flag mismatches without making edits.

Grace Setup Subagents creates GRACE 4 worker and reviewer subagent presets for reading .grace context, graph, verification, and change packets. It is used when agents need to follow spec.xml, scope rules, and evidence-based verification workflows.

Grace Spec interviews the user to define a GRACE 4 GraceChangeSpec in .grace/changes/active/C-*/. It writes a draft spec.xml, can add optional design-context.xml, and waits for explicit approval before marking the spec approved.

Grace Status reports GRACE 4 project health from the current .grace context, including graph integrity, verification, active changes, scope conflicts, and migration boundaries. Use it to decide the next safe action without mutating artifacts.

Grace Verification designs and maintains deterministic verification entries, commands, scenarios, markers, and assertion evidence under .grace/verification. Use it when updating module coverage, gate tasks, or recorded evidence for GRACE 4.