mcpbeat

Grace Execute

osovv/grace-marketplace-grace-execute

Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.

This is a copy. The original lives at osovv/grace-execute.

870 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
231
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/osovv/grace-marketplace --skill grace-execute

The instruction itself

as written by the author

<skill>

<preflight>

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.

</preflight>

<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>

  • Run the selected baseline before implementation, including explicit --run-commands when its assertions declare MustPassCommand.
  • Execute one dependency-ready task or one verified parallel-safe batch at a time.
  • Run each task's acceptance and verification immediately.
  • Apply approved durable context, graph, and verification changes centrally.
  • 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.
  • Ask for explicit apply confirmation after fresh end-state evidence passes.
  • Only then set spec and plan to applied and archive the complete bundle.
  • Never edit approved assertions/scopes/tasks in place, bypass stale evidence, or continue through unknown drift.

</execution_rules>

</skill>

How to use it

Copy the folder

Take osovv/grace-marketplace-grace-execute from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.