grace-plan
Read an approved GRACE 4 GraceChangeSpec and optional design context, then create a GraceChangePlan with assertions, scopes, tasks, and verification gates.
osovv · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add osovv/grace-marketplace --skill grace-planAbout this skill
name: grace-plan description: Read an approved GRACE 4 GraceChangeSpec and optional design context, then create a GraceChangePlan with assertions, scopes, tasks, and verification gates.
<approved_plan_immutability>
- If
plan.xmlalready exists with statusapproved, stop before writing. - Do not refresh
BaselineAssertions,TargetAssertions,DurableScope,ObservedWriteScope, or tasks in place. - Create a new
C-*bundle and mark the old bundle superseded with an explicit replacement reference. </approved_plan_immutability>
<must_do>
Produce plan.xml from references/change-plan-template.xml as draft unless the user explicitly approves the completed plan. Require a matching C-* wrapper, meaningful intent, non-empty machine-checkable baseline and target assertions, explicit durable and observed scopes, and unique acyclic T-NNN tasks. A scope with no writes must use an explicit <None /> marker; prose such as "none" is invalid. Every task has one Title, one DependsOn element listing zero or more predecessors as canonical comma-separated T-NNN values (for example <DependsOn>T-001, T-002</DependsOn>), non-empty acceptance criteria, and non-empty verification commands. Dependencies form a directed acyclic graph: list only true predecessors and never linearize independent tasks into a chain to express ordering. Surface stale-state and coexistence warnings, and reject unsupported scope glob syntax instead of guessing.
</must_do>
<command_phase_rules>
currentis an active-baseline preflight and is valid only before observed writes begin.baselineis the selected pre-edit gate,targetis selected post-edit evidence, andfinalis the outer apply/archive gate owned bygrace-execute.MustPassCommandcontains leaf project evidence such as tests, typecheck, build, format, or package checks. Never placegrace lint,grace status, or another GRACE lifecycle command inside it.- Never put
--assertions currentinTargetAssertionsor in task verification that runs after writes. Use selected target/final lint externally instead. </command_phase_rules>
<hard_rules> Do not implement code, silently approve a plan, overwrite an approved plan, or mutate current graph/verification artifacts while planning. Semantic anchors are canonical XML tags, never attributes. </hard_rules>