grace-spec
SkillMediaInterview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-*/.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the grace-spec skill
What this skill tells your AI
The instructions your AI receives, as published by osovv/grace-marketplace in skills/grace/grace-spec/SKILL.md and read by ahel’s review.
spec.xml— normativeGraceChangeSpecdesign-context.xml— optional, explanatory onlyplan.xml— created later bygrace-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>
<hard_rules>
spec.xmlis the source of truth forgrace-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 currentas a pre-implementation active-baseline check after writing the bundle; never present it as target or final evidence. </hard_rules>
Signals
- GitHub stars
- 241
- Forks
- 55
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
grace-spec- Source
- github.com/osovv/grace-marketplace