Grace init

Skill osovv/grace-marketplace/plugins/grace/skills/grace/grace-init

Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.From its SKILL.md

Install

npx -y skills add osovv/grace-marketplace --skill grace-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

runs commandsInstructs the agent to run 1 command, including `grace lint --path <project-root>`.

SKILL.md

2.9 KB, 714 tokens by cl100k_base, as published. Nobody here has run it

<skill> <task> Create the canonical GRACE 4 project layout from this skill's `assets/` templates:

AGENTS.md
.grace/context/requirements.xml
.grace/context/technology.xml
.grace/context/principles.xml
.grace/context/deployment.xml
.grace/context/ux-guidelines.xml
.grace/graph/index.xml
.grace/graph/main.xml
.grace/verification/index.xml
.grace/verification/main.xml
.grace/changes/active/
.grace/changes/archive/

Every XML artifact uses graceVersion="4.0". Semantic anchors are XML tags, never attributes. Do not create dummy C-* change bundles. Do not overwrite existing .grace artifacts without explicit confirmation. </task>

<template_sources>

Template source	Target in project
`assets/AGENTS.md.template`	`AGENTS.md`
`assets/.grace/context/requirements.xml.template`	`.grace/context/requirements.xml`
`assets/.grace/context/technology.xml.template`	`.grace/context/technology.xml`
`assets/.grace/context/principles.xml.template`	`.grace/context/principles.xml`
`assets/.grace/context/deployment.xml.template`	`.grace/context/deployment.xml`
`assets/.grace/context/ux-guidelines.xml.template`	`.grace/context/ux-guidelines.xml`
`assets/.grace/graph/index.xml.template`	`.grace/graph/index.xml`
`assets/.grace/graph/main.xml.template`	`.grace/graph/main.xml`
`assets/.grace/verification/index.xml.template`	`.grace/verification/index.xml`
`assets/.grace/verification/main.xml.template`	`.grace/verification/main.xml`
</template_sources>

<steps> 1. Gather project name, annotation, keywords, language/runtime/framework, testing stack, observability constraints, deployment applicability, UX applicability, and any known initial modules. 2. If `.grace` or `AGENTS.md` already exists, stop and ask whether to keep, merge, or overwrite each existing artifact. Never overwrite silently. 3. Create `.grace/context`, `.grace/graph`, `.grace/verification`, `.grace/changes/active`, and `.grace/changes/archive`. 4. Read each `.template` file, replace `$PLACEHOLDER` values with gathered project information, and write the target file. 5. Print created files and recommend the next workflow: use `grace-spec` to create an active `GraceChangeSpec`, then `grace-plan` to produce a `GraceChangePlan` before implementation. </steps>

<hard_rules>

GRACE 4 state lives under .grace; do not create legacy docs/*.xml as the bootstrap surface.
GraceChangeSpec and GraceChangePlan are created by later change workflows, not by init.
If legacy GRACE 3 docs are present, explain that migration is handled only by grace-migrate; init must not convert or delete them.
Validate the resulting project with grace lint --path <project-root> when the CLI is available. </hard_rules> </skill>

What ships with it: 11 files

5.6 KB alongside SKILL.md

agents/

openai.yaml122 B

assets/

Gives 0 of the 12 instructions most project setup skills give in 714 tokens

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

Write the configuration filein 36 of 1553
Create the directory structurein 35 of 1553, across 33 files
Verify the setupin 31 of 1553, across 28 files
Run the setup scriptin 30 of 1553, across 29 files
Pre-determine the required sample sizein 29 of 1553, across 12 files
Check if the configuration already existsin 29 of 1553
Document every testin 26 of 1553, across 10 files
Start with a hypothesisin 26 of 1553, across 11 files
Ask one question at a timein 22 of 1553
Test a single variable per testin 21 of 1553, across 9 files
Read product marketing context before asking questionsin 19 of 1553, across 8 files
Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

Create the canonical GRACE project layout
Print created files and recommend next workflow
Validate the resulting project with grace lint

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.