Skip to content
cccskills
FreePublished on GitHub

grace-spec

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md2.1 KB
  • agents/openai.yaml117 B
  • references/change-spec-template.xml787 B
  • references/design-context-template.xml424 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Answer questions about a GRACE 4 project by navigating .grace current-state artifacts and file-local semantic markup.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Debug and fix issues in a GRACE 4 project using .grace semantic navigation, assertions, and verification evidence.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.

The English summary is being prepared. Showing the original description.

osovv/grace-marketplace254Updated Sep 24, 2026

See all skills by osovv

Report a problem with this skill