Spec-driven AI workflow tool (by Fission AI) enforcing field-level contracts across repos

A uniquely-named data field with agreed type, format, and business meaning across all repos

An AI-generated change to the spec requiring human review before merge

OpenSpec slash command to generate a spec proposal for new or changed fields

Slash command that applies an approved proposal's changes to the current repo

Slash command checking that all canonical fields in code match the spec

Slash command pulling latest spec changes from the shared spec repository

CLI command bootstrapping OpenSpec in a repository with config.yaml and AI instructions

Per-repo OpenSpec config defining domain description, glossary, and agent tool settings

Claude Code's project instruction file; OpenSpec auto-generates a Rules section in it

Gemini Code Assist's equivalent of CLAUDE.md for OpenSpec-managed repos

Process of reviewing spec changes, resolving conflicts, and maintaining spec health

Condition where code implementation diverges from the agreed canonical spec

OpenSpec's primary goal - same field name/type enforced across all services

Company that builds OpenSpec and the @fission-ai/openspec npm package