/grace-init
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
$ npx -y skills add osovv/grace-marketplace --skill grace-init --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/grace-init
Context preview
The summary Claude sees to decide when to auto-load this skill.
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
SKILL.md
grace-init.SKILL.mdname: grace-init
description: Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
<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>
Read more
name: grace-init description: Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
<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>
GRACE means Graph-RAG Anchored Code Engineering: a contract-first AI engineering methodology built around semantic markup, .grace XML artifacts, knowledge-graph navigation, assertions, scopes, and log-driven verification.
Repo: osovv/grace-marketplace
Other skills on grace-marketplace.
- /grace-ask
Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
Open skill - /grace-cli
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
Open skill - /grace-execute
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
Open skill - /grace-explainer
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
Open skill - /grace-fix
Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.
Open skill - /grace-migrate
Agent-applied GRACE 3 to GRACE 4 migration workflow. CLI validates the result but does not convert or delete files.
Open skill