From grace
Bootstraps GRACE framework structure for new projects: creates docs/ directory with XML templates for requirements, technology, development/verification plans, knowledge graph, operational packets, plus AGENTS.md.
npx claudepluginhub osovv/grace-marketplace --plugin graceThis skill uses the workspace's default tool permissions.
Initialize GRACE framework structure for this project.
Explains GRACE methodology for AI-driven code generation: principles, knowledge graphs, module contracts, semantic markup, verification plans, operational packets. Use for user explanations, project onboarding, framework reference.
Scaffolds greenfield project architecture, test infrastructure, guard rails, and AI agent harness via interview-driven layers to requirements.md. Use for /scaffold, new projects, or setup.
Generates complete production-ready projects from descriptions: directory structure, code, tests, docs, config, git init. Orchestrates pipeline with verification to ensure builds and tests pass.
Share bugs, ideas, or general feedback.
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."