agentsclimarketplace

Grace spec

Skill osovv/grace-marketplace/plugins/grace/skills/grace/grace-spec

Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-*/.From its SKILL.md

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

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

SKILL.md

2.1 KB, as published. Nobody here has run it

<skill> <change_bundle_contract> `.grace/changes/active/C-CHANGE-ID/`
  • spec.xml — normative GraceChangeSpec
  • design-context.xml — optional, explanatory only
  • plan.xml — created later by grace-plan </change_bundle_contract>

<status_rules> Create spec.xml as status="draft". Set status="approved" only after explicit user approval. Rejected or cancelled specs move to archive with terminal status. Do not create or edit plan.xml in this skill. </status_rules>

<strict_contract> The direct C-* wrapper must contain exactly one meaningful Summary, Goals, Constraints, NonGoals, AcceptanceCriteria, AffectedAreas, and VerificationIntent section. Empty containers are not approval-ready. Semantic anchors are canonical attribute-free XML tags, never attributes or attribute values. </strict_contract>

<workflow> 1. Ask one focused question at a time until goal, scope, constraints, non-goals, acceptance criteria, affected areas, and verification expectations are clear. 2. Propose a concise design summary and explicit assumptions. Ask for approval before writing an approved spec. 3. Create a deterministic uppercase-kebab `C-*` change id. 4. Write `spec.xml` from `references/change-spec-template.xml` with exactly one direct `C-*` wrapper and no empty required section. 5. If rationale, alternatives, scenarios, or external constraints would otherwise bloat the spec, write non-normative `design-context.xml` from its template. 6. If approval is not explicit, leave `spec.xml` as `status="draft"` and report the approval step needed. </workflow>

<hard_rules>

  • spec.xml is the source of truth for grace-plan; design context never adds requirements.
  • Do not implement code, mutate current graph/verification state, or create retroactive change bundles.
  • Recommend grace lint --path <project-root> --assertions current as a pre-implementation active-baseline check after writing the bundle; never present it as target or final evidence. </hard_rules> </skill>

What ships with it: 3 files

1.3 KB alongside SKILL.md

agents/

Gives 2 of the 12 instructions most plan spec skills give

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timehere, and in 73 of 1360
  • Write the spec using the templatehere, and in 22 of 1360
  • Ask clarifying questions if neededin 19 of 1360, across 18 files
  • Wait for user confirmation before proceedingin 19 of 1360
  • Save plans to the plans directoryin 17 of 1360, across 13 files
  • Check for product marketing context firstin 16 of 1360, across 5 files
  • Read the plan file completelyin 16 of 1360
  • Order tasks by dependencyin 16 of 1360
  • Gather context from the conversationin 15 of 1360, across 9 files
  • Explore the codebase instead of askingin 15 of 1360, across 13 files
  • Wait for explicit user approvalin 14 of 1360, across 13 files
  • Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

  • Propose a concise design summary
  • Create a deterministic uppercase-kebab change id
  • Write design-context.xml if needed
  • Leave spec.xml as draft without explicit approval

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 613,297. 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.