osovv/grace-marketplace/grace-execute

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

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