grace-spec
Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-*/.
osovv · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add osovv/grace-marketplace --skill grace-spec技能说明
name: grace-spec description: Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-*/.
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>