grace-ask
Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.
@osovvInstall SkillDevelopment
Skill
/grace-init
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
Claude Code
$ npx -y skills add osovv/grace-marketplace --skill grace-init --agent claude-code
Codex
$ npx skills add osovv/grace-marketplace --skill grace-init -a codex -y
Cursor
$ npx skills add osovv/grace-marketplace --skill grace-init -a cursor -y
Gemini CLI
$ npx skills add osovv/grace-marketplace --skill grace-init -a gemini-cli -y
GitHub Copilot
$ npx skills add osovv/grace-marketplace --skill grace-init -a github-copilot -y
OpenCode
$ npx skills add osovv/grace-marketplace --skill grace-init -a opencode -y
Windsurf
$ npx skills add osovv/grace-marketplace --skill grace-init -a windsurf -y
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>
Stats
268
Stars
60
Forks
Maintained
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withgrace-marketplace
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.
26815 skills
Stars on GitHub
Momentum
- stars in total
- 268
Other skills on grace-marketplace.
@osovvInstall Skillgrace-cli
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
@osovvInstall Skillgrace-execute
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized…
@osovvInstall Skillgrace-explainer
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
@osovvInstall Skillgrace-fix
Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.
@osovvInstall Skillgrace-migrate
Agent-applied GRACE 3 to GRACE 4 migration workflow. CLI validates the result but does not convert or delete files.
@osovvInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about grace-init.
- Which coding agents can use grace-init?
- grace-init installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.