osovv/grace-marketplace/grace-init

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