Skip to content
cccskills
FreePublished on GitHub

grace-execute

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.3 KB
  • agents/openai.yaml130 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Agent-applied GRACE 3 to GRACE 4 migration workflow. CLI validates the result but does not convert or delete files.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

See all skills by osovv

Report a problem with this skill