mcpField
G
grace-execute

grace-execute

github.com/osovvDevelopment25642 installsUpdated 5w ago
Repository

About grace-execute

A workflow skill for executing projects governed by approved GRACE spec and plan bundles. It enforces baseline and final lint checks, task verification, controlled parallel work, and explicit confirmation before applying and archiving a bundle.

Key features

  1. 01Approved bundle and identity checks
  2. 02Baseline and final lint gates
  3. 03Task-level acceptance verification
  4. 04Parallel-safety preflight
  5. 05Durable-state reconciliation
  6. 06Explicit apply confirmation

Use cases

  1. 01Executing an approved GRACE project plan
  2. 02Verifying work before applying a bundle
  3. 03Stopping safely when project drift is unexplained

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/osovv/grace-marketplace --skill grace-execute

After installing, type/grace-executein Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README
Require one active bundle with approved, identity-matched `spec.xml` and `plan.xml`. Approved plans are immutable. Read context, projections, assertions, scopes, task dependencies, and verification before editing. Reject phase-incompatible plans before writes: `MustPassCommand` must be leaf project evidence, and neither target assertions nor post-write task verification may invoke `--assertions current` or nest GRACE lifecycle commands. Supersede and replan instead of editing an approved conflict in place.

<assertion_commands>

  • Active-baseline preflight before observed writes: grace lint --path PROJECT --assertions current
  • Selected baseline: grace lint --path PROJECT --change C-ID --assertions baseline (add --run-commands when the baseline declares MustPassCommand)
  • Selected target without commands: grace lint --path PROJECT --change C-ID --assertions target
  • Selected target with command evidence: grace lint --path PROJECT --change C-ID --assertions target --run-commands
  • Final end-state validation: grace lint --path PROJECT --change C-ID --assertions final (add --run-commands when the target declares MustPassCommand)
  • Parallel preflight: grace lint --path PROJECT --parallel-preflight </assertion_commands>

<mode_selection> Wait for explicit sequential or parallel-safe choice. Parallel-safe requires the explicit preflight to pass. Workers never mutate approved plans; durable .grace changes are applied centrally after observed work verifies. </mode_selection>

<recovery_decision_table> | state | required action | | clean-to-start | Run selected baseline, then execute tasks. | | partial-observed-writes | Inspect the declared observed scope and ask whether to resume or revert. | | durable-state-changed | Hard stop; supersede and replan. Approved assertions are immutable. | | target-already-satisfied | Run final end-state validation, opted-in command evidence when declared, durable reconciliation, and ask for explicit apply confirmation. | | unsafe-unknown-drift | Hard stop and report unexplained files. | </recovery_decision_table>

<execution_rules>

  1. Run the selected baseline before implementation, including explicit --run-commands when its assertions declare MustPassCommand.
  2. Execute one dependency-ready task or one verified parallel-safe batch at a time.
  3. Run each task's acceptance and verification immediately.
  4. Apply approved durable context, graph, and verification changes centrally.
  5. Reconcile durable state, run leaf plan gates, then run selected --assertions final as the outermost lifecycle gate, including --run-commands when MustPassCommand is declared. Final mode performs full project lint, evaluates the selected target, keeps unrelated approved baselines active, and does not re-evaluate the selected plan's superseded baseline.
  6. Ask for explicit apply confirmation after fresh end-state evidence passes.
  7. Only then set spec and plan to applied and archive the complete bundle.
  8. Never edit approved assertions/scopes/tasks in place, bypass stale evidence, or continue through unknown drift. </execution_rules>

Comments

Markdown supported