Grace plan
Read an approved GRACE 4 GraceChangeSpec and optional design context, then create a GraceChangePlan with assertions, scopes, tasks, and verification gates.From its SKILL.md
npx -y skills add osovv/grace-marketplace --skill grace-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
3.0 KB, as published. Nobody here has run it
<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, non-empty acceptance criteria, and non-empty verification commands. 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> </skill>
What ships with it: 2 files
1.3 KB alongside SKILL.md
agents/
- openai.yaml127 B
references/
- change-plan-template.xml1.2 KB
Gives 0 of the 12 instructions most plan spec skills give
Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06
- Ask one question at a timein 73 of 1360
- Write the spec using the templatein 22 of 1360
- Ask clarifying questions if neededin 19 of 1360, across 18 files
- Wait for user confirmation before proceedingin 19 of 1360
- Save plans to the plans directoryin 17 of 1360, across 13 files
- Check for product marketing context firstin 16 of 1360, across 5 files
- Read the plan file completelyin 16 of 1360
- Order tasks by dependencyin 16 of 1360
- Gather context from the conversationin 15 of 1360, across 9 files
- Explore the codebase instead of askingin 15 of 1360, across 13 files
- Wait for explicit user approvalin 14 of 1360, across 13 files
- Quiz the user on the breakdownin 13 of 1360, across 7 files
Said here and by no other author read
- Run grace lint before planning
- Produce plan.xml from template
- Require matching wrapper and meaningful intent
- Include non-empty baseline and target assertions
- Define explicit durable and observed scopes
- Create unique acyclic tasks
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.