Skip to content
cccskills
FreePublished on GitHub

grace-init

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

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace
See how to install

Files included (12)

  • SKILL.md2.9 KB
  • agents/openai.yaml122 B
  • assets/.grace/context/deployment.xml.template269 B
  • assets/.grace/context/principles.xml.template321 B
  • assets/.grace/context/requirements.xml.template411 B
  • assets/.grace/context/technology.xml.template410 B
  • assets/.grace/context/ux-guidelines.xml.template311 B
  • assets/.grace/graph/index.xml.template178 B
  • assets/.grace/graph/main.xml.template84 B
  • assets/.grace/verification/index.xml.template213 B
  • assets/.grace/verification/main.xml.template98 B
  • assets/AGENTS.md.template3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<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 sourceTarget in project
assets/AGENTS.md.templateAGENTS.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>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

grace-ask

Free

Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace253Updated Sep 24, 2026

grace-cli

Free

Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace253Updated Sep 24, 2026

grace-execute

Free

Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace253Updated Sep 24, 2026

grace-explainer

Free

Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace253Updated Sep 24, 2026

grace-fix

Free

Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace253Updated Sep 24, 2026

grace-migrate

Free

Agent-applied GRACE 3 to GRACE 4 migration workflow. CLI validates the result but does not convert or delete files.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace253Updated Sep 24, 2026

See all skills by osovv

Report a problem with this skill