specification
AI Native Development Platform.
Supercharge your agents with spec-driven development. Get the speed of agentic coding with the reliability of production software.
Related contents:
Open Responses is an open-source specification and ecosystem for building multi-provider, interoperable LLM interfaces based on the OpenAI Responses API. It defines a shared schema, and tooling layer that enable a unified experience for calling language models, streaming results, and composing agentic workflows—independent of provider.
Standardizing Feature Flagging for Everyone.
OpenFeature is an open specification that provides a vendor-agnostic, community-driven API for feature flagging that works with your favorite feature flag management tool or in-house solution.
If you build software, keep a changelog. Don’t let your friends dump git logs into changelogs.
Related contents:
Supply-chain Levels for Software Artifacts, or SLSA ("salsa").
SLSA is a specification for describing and incrementally improving supply chain security, established by industry consensus. It is organized into a series of levels that describe increasing security guarantees.
It’s a security framework, a checklist of standards and controls to prevent tampering, improve integrity, and secure packages and infrastructure. It’s how you get from "safe enough" to being as resilient as possible, at any link in the chain.
Related contents:
A lightweight spec‑driven framework.
OpenSpec aligns humans and AI coding assistants with spec-driven development so you agree on what to build before any code is written. No API keys required.
Related contents:
The WebMCP API enables web applications to provide JavaScript-based tools to AI agents.
Related contents:
One easy way to configure all your workloads. Everywhere.
The Score Specification provides a developer-centric and platform-agnostic Workload specification to improve developer productivity and experience. It eliminates configuration inconsistencies between environments.
A specification for developer-centric application definition used in Cloud Native Applications
The Compose Specification is a developer-focused standard for defining cloud and platform agnostic container-based applications.
An open specification for enriching containers with development specific content and settings.
A Development Container (or Dev Container for short) allows you to use a container as a full-featured development environment. It can be used to run an application, to separate tools, libraries, or runtimes needed for working with a codebase, and to aid in continuous integration and testing. Dev containers can be run locally or remotely, in a private or public cloud.
Related contents:
This site documents how to develop, deploy, and test a Container Storage Interface (CSI) driver on Kubernetes.
The Container Storage Interface (CSI) is a standard for exposing arbitrary block and file storage systems to containerized workloads on Container Orchestration Systems (COs) like Kubernetes. Using CSI third-party storage providers can write and deploy plugins exposing new storage systems in Kubernetes without ever having to touch the core Kubernetes code.
💫 Toolkit to help you get started with Spec-Driven Development.
Build high-quality software faster.
An effort to allow organizations to focus on product scenarios rather than writing undifferentiated code with the help of Spec-Driven Development.
Spec-Driven Development flips the script on traditional software development. For decades, code has been king — specifications were just scaffolding we built and discarded once the "real work" of coding began. Spec-Driven Development changes this: specifications become executable, directly generating working implementations rather than just guiding them.
Related contents:
- What's The Deal With GitHub Spec Kit @ Den Delimarsky.
- The ONLY guide you'll need for GitHub Spec Kit @ Den Delimarsky's YouTube.
- How to write a good spec for AI agents @ Addy Osmani.
- The uncomfortable truth about vibe coding @ RedHat Developer.
- What spec-driven development gets wrong @ augment code.