Grace Spec

What it does

Example prompts

• “/grace-spec”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Ask one focused question at a time until goal, scope, constraints, non-goals, acceptance criteria, affected areas, and verification…
2. 2Propose a concise design summary and explicit assumptions. Ask for approval before writing an approved spec.
3. 3Create a deterministic uppercase-kebab C-* change id.
4. 4Write spec.xml from references/change-spec-template.xml with exactly one direct C-* wrapper and no empty required section.
5. 5If rationale, alternatives, scenarios, or external constraints would otherwise bloat the spec, write non-normative design-context.xml from…
6. 6If approval is not explicit, leave spec.xml as status="draft" and report the approval step needed.

What it can do on your machine

Read from SKILL.md and the folder at commit 70f5ec4. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Grace Spec loads about 545 tokens when it runs, and up to ~848 if it reads all its reference files. Until then it costs about 36 tokens; SKILL.md has 238 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~36

When it runs · the whole SKILL.md, loaded when a task matches

~545

With references · SKILL.md plus every file in references/, read only if the agent opens them

~848

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from osovv/grace-marketplace at commit 70f5ec4, republished under its MIT licence (© osovv). 238 words, ~545 tokens.

name

grace-spec

description

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

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

© osovv, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/grace/grace-spec of osovv/grace-marketplace.

• SKILL.md
• agents/openai.yaml
• references/change-spec-template.xml
• references/design-context-template.xml

Open the folder on GitHubat commit 70f5ec4