Use when the task is about requirements, acceptance criteria, capability scope, or implementation sequencing from OpenSpec changes.
Use when the task is about requirements, acceptance criteria, capability scope, or implementation sequencing from OpenSpec changes.
npx skills add https://github.com/Tzeusy/viz-on-shenton --skill spec-and-spine复制此命令并粘贴到 Claude Code 中以安装该技能
| name | spec-and-spine |
| description | Use when the task is about requirements, acceptance criteria, capability scope, or implementation sequencing from OpenSpec changes. |
Use this skill when the task is about requirements, acceptance criteria, or sequencing implementation from the new product foundation.
openspec/changes/v1-apartment-authoring-program/proposal.mdopenspec/changes/v1-apartment-authoring-program/design.mdopenspec/changes/canonical-document-and-command-spine/proposal.mdopenspec/changes/editor-runtime-and-selection/proposal.mdopenspec/changes/curated-asset-and-material-library/proposal.mdopenspec/changes/review-and-persistence-flow/proposal.mdopenspec/changes/natural-language-edit-assistant/proposal.mdopenspec/changes/rfc-driven-contract-expansion-wave-1/proposal.mdopenspec/changes/rfc-driven-contract-expansion-wave-1/design.mdopenspec/changes/rfc-driven-contract-expansion-wave-1/tasks.mdopenspec/changes/rfc-command-runtime-alignment-wave-2/proposal.mdopenspec/changes/rfc-review-persistence-alignment-wave-2/proposal.mdopenspec/changes/rfc-assistant-governance-alignment-wave-2/proposal.mdopenspec/changes/rfc-library-lifecycle-alignment-wave-3/proposal.mdUse when the task is about technical contracts, subsystem design decisions, mutation boundaries, or RFC-level architecture.
Use when the task is about product thesis, scope boundaries, non-goals, doctrine principles, or non-negotiable rules.
Use when the task is about system boundaries, runtime data flow, deployment topology, or component integration shape.