SeedSpec.dev
GitHub
Protocol 0.1Design alpha

SeedSpec overview

A portable way to tell an AI agent what you want realized—and how success should be checked.

Get startedRead the specification

What is SeedSpec?

SeedSpec is an open protocol for packaging intent into specifications that people can read and agents can act on.

A package describes the outcome, provides useful context and choices, and defines how success should be checked. The agent still decides how to do the work, under the user’s direction.

Why SeedSpec?

Agents are increasingly capable, but important context often lives in prompts, tickets, documents, and people’s heads. SeedSpec turns that context into a portable, versioned handoff.

  • Clear intentKeep the outcome, constraints, decisions, and success criteria together instead of scattering them across a chat history.
  • Portable handoffsGive the same package to different compatible tools and agents without locking the work to one implementation stack.
  • Reviewable resultsCarry acceptance criteria and evidence expectations into the handoff so completion can be checked, not merely claimed.

Three problems. One portable format.

SeedSpec can carry the intent for a product your family uses every day, the internal software that runs a team, or a workflow that crosses several systems. Each package below is concrete enough to realize and broad enough to survive a change in tools or implementation stack.

Personal productInternal toolConnected workflow
Household application

Family Hub

Plan the week. Share the load.

One calm place for a family’s events and assigned tasks, with privacy-aware schedules and history everyone can trust.

  • Shared events
  • Recurring tasks
  • Allowance
  • Meals + groceries
Why it matters

A configurable multi-role app whose optional modules add useful depth without changing the core household promise.

Internal software

Operations Dashboard Starter Kit

Turn live operations into focused action.

A reusable internal console for trustworthy metrics, prioritized records, saved views, governed actions, and safe exports.

  • Metrics
  • Record queue
  • Roles
  • Audit history
Why it matters

How a portable starter can adapt to a team’s vocabulary and operating model while keeping access and data states precise.

Cross-system workflow

Customer Onboarding Orchestrator

Make every handoff owned and visible.

Turn an approved deal into milestones, owners, customer updates, stalled-work escalation, and auditable completion.

  • Handoff
  • Milestones
  • Escalation
  • Evidence
Why it matters

One durable outcome with three viable realization paths: configure the current stack, automate it, or build a service.

Browse all seven reference specifications

Package anatomy

At its core, a SeedSpec package is a folder with a seedspec.yaml manifest and a Markdown definition. It can also include configuration, decisions, acceptance criteria, capability contracts, and implementation resources.

text
my-package/
├── seedspec.yaml              # Required: identity + package map
├── definition/               # Example: native primary intent
│   └── feature.md
├── configuration/            # Optional: choices and defaults
│   ├── schema.json
│   └── example.yaml
├── acceptance/               # Optional: success criteria
│   └── criteria.md
└── capabilities/             # Optional: capability contracts

How does SeedSpec work?

SeedSpec separates reusable intent from a specific implementation in three stages.

  1. Package

    An author describes the intended outcome and bundles the context an agent may need.

    seedspec validate ./my-package

  2. Resolve

    The user reviews fit, chooses configuration, and combines any additions into one project handoff.

    seedspec begin ./my-package

  3. Realize

    The chosen agent realizes the resolved intent. Completion is checked separately against the selected evidence requirements.

    seedspec completion ./project

What can SeedSpec describe?

The format is intentionally broad. A package describes the outcome; its kind helps people and agents understand the shape of the work without restricting how packages compose.

Applications

Describe a complete product or solution.

Features

Add portable intent to an existing project.

Workflows

Define an outcome that spans tools or systems.

Configurations

Capture desired state in a service or platform.

Open development

SeedSpec is an open-source protocol released under Apache 2.0. The specification, versioned schemas, reference runtime, CLI, and conformance suite are developed in public.

Protocol 0.1 is a design alpha for implementation and interoperability testing. Pin exact prerelease versions when building integrations.

Join the project on GitHub

Get started with SeedSpec

Author a packageCreate a small package and validate its structure.Read the specificationExplore the complete Protocol 0.1 format.
npx --yes @seedspec/cli@next version