Grace spec
Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-*/.From its SKILL.md
npx -y skills add osovv/grace-marketplace --skill grace-specAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.1 KB, as published. Nobody here has run it
spec.xml— normativeGraceChangeSpecdesign-context.xml— optional, explanatory onlyplan.xml— created later bygrace-plan</change_bundle_contract>
<status_rules>
Create spec.xml as status="draft". Set status="approved" only after explicit user approval. Rejected or cancelled specs move to archive with terminal status. Do not create or edit plan.xml in this skill.
</status_rules>
<strict_contract>
The direct C-* wrapper must contain exactly one meaningful Summary, Goals, Constraints, NonGoals, AcceptanceCriteria, AffectedAreas, and VerificationIntent section. Empty containers are not approval-ready. Semantic anchors are canonical attribute-free XML tags, never attributes or attribute values.
</strict_contract>
<hard_rules>
spec.xmlis the source of truth forgrace-plan; design context never adds requirements.- Do not implement code, mutate current graph/verification state, or create retroactive change bundles.
- Recommend
grace lint --path <project-root> --assertions currentas a pre-implementation active-baseline check after writing the bundle; never present it as target or final evidence. </hard_rules> </skill>
What ships with it: 3 files
1.3 KB alongside SKILL.md
agents/
- openai.yaml117 B
references/
Gives 2 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 timehere, and in 73 of 1360
- Write the spec using the templatehere, and in 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
- Propose a concise design summary
- Create a deterministic uppercase-kebab change id
- Write design-context.xml if needed
- Leave spec.xml as draft without explicit approval
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.