OpenSpec
The open specification format for AI agent orchestration. A versioned, tool-agnostic format describing software projects as hierarchical specs that any compliant agent can execute.
Think OpenAPI, but for agent orchestration instead of REST APIs.
{
"implementationSteps": [{ "text": "Add auth middleware", ... }],
"filesToBeCreated": ["src/middleware/auth.ts"],
"filesToBeModified": ["src/routes/index.ts"],
"filesToBeDeleted": ["src/legacy/session.ts"],
"filesToBeReferenced": ["src/config/jwt.config.ts"],
"codeReferences": [{ "filePath": "src/auth/jwt.ts", "symbol": "JwtConfig" }],
"typeReferences": [{ "filePath": "src/types.ts", "typeName": "User" }],
"acceptanceCriteria": [{ "given": "no token", "when": "GET /me", "then": "401", ... }],
"testSpecification": { "testTypes": ["integration"], "qualityGates": ["auth paths covered"] },
"dependencies": [{ "ticketId": "tkt-1", "type": "requires" }]
}Why This Format
Eight lessons from 400+ builds. Every field exists because its absence caused a real failure.
Getting Started
Write, validate, and use an OpenSpec in five minutes. No account required.
Schema Explorer
Browse every entity and field in the format with types, requirements, and descriptions.
Live Editor
Paste or write a spec file and validate it in real-time against the v1.1 schema.
Three Formats
JSON for machines, YAML for humans, TOON for LLMs. All lossless representations of one schema.
Offline Validator
npm package that validates specs locally. Zero auth, zero SaaS dependency.
Schema URL (permanent)
https://openspec.tech/schema/v1.1/openspec-schema.json
OpenSpec is an open specification. Any tool can generate, validate, and consume .oschema.json files. The format belongs to the ecosystem.