// Bootstrap GRACE framework structure for a new project. Use when starting a new project with GRACE methodology - creates docs/ directory, AGENTS.md, and XML templates for requirements, technology, development plan, verification plan, knowledge graph, and operational packet contracts.
Operate the optional `grace` CLI against a GRACE project. Use when you want to lint GRACE artifacts, explain/remediate lint issues, check autonomy readiness, inspect project or module health, inspect verification entries, resolve modules from names or file paths, inspect shared/public module context, or inspect file-local/private markup through `grace lint`, `grace status`, `grace module`, `grace verification`, and `grace file show`.
Complete GRACE methodology reference. Use when explaining GRACE to users, onboarding new projects, or when you need to understand the GRACE framework - its principles, semantic markup, knowledge graphs, contracts, testing, and unique tag conventions.
Execute the full GRACE development plan step by step with controller-managed context packets, verification-plan excerpts, scoped reviews, level-based verification, and commits after validated sequential steps.
Execute a GRACE development plan in controller-managed parallel waves with selectable safety profiles, verification-plan excerpts, batched shared-artifact sync, and scoped reviews.
Create GRACE subagent presets for the current agent shell. Use when you want GRACE worker and reviewer agent files scaffolded for Claude Code, OpenCode, Codex, or another shell.
Show the current health status of a GRACE project. Use to get an overview of project artifacts, codebase metrics, knowledge graph health, verification coverage, and suggested next actions.
| name | grace-init |
| description | Bootstrap GRACE framework structure for a new project. Use when starting a new project with GRACE methodology - creates docs/ directory, AGENTS.md, and XML templates for requirements, technology, development plan, verification plan, knowledge graph, and operational packet contracts. |
Initialize GRACE framework structure for this project.
All documents MUST be created from template files located in this skill's assets/ directory.
Read each template file, replace the $PLACEHOLDER variables with actual values gathered from the user, and write the result to the target project path.
| Template source | Target in project |
|---|---|
assets/AGENTS.md.template | AGENTS.md (project root) |
assets/docs/knowledge-graph.xml.template | docs/knowledge-graph.xml |
assets/docs/requirements.xml.template | docs/requirements.xml |
assets/docs/technology.xml.template | docs/technology.xml |
assets/docs/development-plan.xml.template | docs/development-plan.xml |
assets/docs/verification-plan.xml.template | docs/verification-plan.xml |
assets/docs/operational-packets.xml.template | docs/operational-packets.xml |
Important: Never hardcode template content inline. Always read from the
.templatefiles — they are the single source of truth for document structure.
Gather project info from the user. Ask for:
Create docs/ directory and populate documents from templates:
For each assets/docs/*.xml.template file:
$PLACEHOLDER variables with user-provided valuesdocs/ pathCreate or verify AGENTS.md at project root:
AGENTS.md does not exist — read assets/AGENTS.md.template, fill in $KEYWORDS and $ANNOTATION, and write to project rootAGENTS.md already exists — warn the user and ask whether to overwrite or keep the existing onePrint a summary of all created files and suggest the next step:
"Run
$grace-planto design modules, data flows, and verification references. Then use$grace-verificationto deepen tests, traces, and log-driven evidence before large execution waves. Usedocs/operational-packets.xmlas the canonical packet and delta reference during execution and refactors."