agentsclimarketplace

Grace plan

Skill osovv/grace-marketplace/skills/grace/grace-plan

GRACE (Graph-RAG Anchored Code Engineering): open Agent Skills for contract-driven AI code generation with semantic markup, knowledge graphs, and support for Claude Code, Codex CLI, and Kilo Code.

Install
npx -y skills add osovv/grace-marketplace --skill grace-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Read an approved GRACE 4 GraceChangeSpec and optional design context, then create a GraceChangePlan with assertions, scopes, tasks, and verification gates.

SKILL.md

2.4 KB, as published. Nobody here has run it

<skill> <purpose>Convert one approved active `GraceChangeSpec` into the executable `GraceChangePlan`; do not implement source code.</purpose> <inputs> - Required: `.grace/changes/active/C-CHANGE-ID/spec.xml` - Optional: sibling `design-context.xml` - Current state: `.grace/context`, graph and verification indexes, and their routed documents </inputs> <preflight> - Require `.grace/changes/active/C-CHANGE-ID/spec.xml` with `GraceChangeSpec`, status `approved`, and exactly one matching direct `C-*` wrapper. - Refuse draft, rejected, cancelled, applied, or superseded specs. - Treat optional `design-context.xml` as explanatory; `spec.xml` wins on conflict. - Run `grace lint --path PROJECT --assertions current` and surface stale or invalid state before planning. </preflight>

<approved_plan_immutability>

  • If plan.xml already exists with status approved, stop before writing.
  • Do not refresh BaselineAssertions, TargetAssertions, DurableScope, ObservedWriteScope, or tasks in place.
  • Create a new C-* bundle and mark the old bundle superseded with an explicit replacement reference. </approved_plan_immutability>

<must_do> Produce plan.xml from references/change-plan-template.xml as draft unless the user explicitly approves the completed plan. Require a matching C-* wrapper, meaningful intent, non-empty machine-checkable baseline and target assertions, explicit durable and observed scopes, and unique acyclic T-NNN tasks. A scope with no writes must use an explicit <None /> marker; prose such as "none" is invalid. Every task has one Title, one DependsOn, non-empty acceptance criteria, and non-empty verification commands. Surface stale-state and coexistence warnings, and reject unsupported scope glob syntax instead of guessing. </must_do>

<validation> - Current validation: `grace lint --path PROJECT --assertions current` - Parallel safety: `grace lint --path PROJECT --parallel-preflight` - Recommend `grace status --path PROJECT --json` after approval. </validation>

<hard_rules> Do not implement code, silently approve a plan, overwrite an approved plan, or mutate current graph/verification artifacts while planning. Semantic anchors are canonical XML tags, never attributes. </hard_rules> </skill>

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.