osovv spec.xml— normativeGraceChangeSpecdesign-context.xml— optional, explanatory onlyplan.xml— created later bygrace-plan
Grace Spec
Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-*/.
Grace Spec by osovv · 65c15c6
npx skillmds@latest add osovv/grace-spec File contents
---name: grace-specdescription: Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-*/.---<skill><change_bundle_contract>`.grace/changes/active/C-CHANGE-ID/`- `spec.xml` — normative `GraceChangeSpec`- `design-context.xml` — optional, explanatory only- `plan.xml` — created later by `grace-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><workflow>1. Ask one focused question at a time until goal, scope, constraints, non-goals, acceptance criteria, affected areas, and verification expectations are clear.2. Propose a concise design summary and explicit assumptions. Ask for approval before writing an approved spec.3. Create a deterministic uppercase-kebab `C-*` change id.4. Write `spec.xml` from `references/change-spec-template.xml` with exactly one direct `C-*` wrapper and no empty required section.5. If rationale, alternatives, scenarios, or external constraints would otherwise bloat the spec, write non-normative `design-context.xml` from its template.6. If approval is not explicit, leave `spec.xml` as `status="draft"` and report the approval step needed.</workflow><hard_rules>- `spec.xml` is the source of truth for `grace-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 current` as a pre-implementation active-baseline check after writing the bundle; never present it as target or final evidence.</hard_rules></skill>
osovv/grace-marketplace/tree/main/skills/grace/grace-spec commit 65c15c6032
Frequently asked questions
Run npx skillmds@latest add osovv/grace-spec in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-*/. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
osovv (@osovv) published this skill. Their other Agent Skills are listed on their SkillMD profile.