Skip to main content
Ready Standard gives your team a single, durable source of product truth stored as ordinary files. Primitive records capture why your product exists, what it promises, how it must behave, and what it depends on. Everything lives in Git — branches hold experiments, merges represent accepted decisions, and agents compile any view you need from the same source.

Quick Start

Set up your first Ready product tree in minutes

Core Concepts

Understand the product tree, primitives, flags, and stages

Guides

Step-by-step walkthroughs for common workflows

Reference

Full schema reference for .ready.yml and manifests

What is a Ready product tree?

A Ready product tree is a committed filetree that stores product decisions as typed records. Instead of scattering requirements across tickets, chat logs, design files, and wikis, you keep the durable part — the why, what, and how — in version-controlled YAML files that any tool or agent can parse.
1

Create your ready/ directory

Initialize a ready/manifest.yaml with a stage registry and a governance/ folder for project policies.
2

Write primitive records

Add .ready.yml files for premises (why), intents (what), standards (how), and services (dependencies).
3

Gate work with flags

Use seed and delta flags to signal when coding work is ready to claim — preventing agents from starting on incomplete specs.
4

Compile views

Let apps, agents, or docs compilers project the tree into PM summaries, developer briefs, design specs, or customer-facing explanations.

Key capabilities

Typed Primitive Records

Premises, intents, standards, services, and question cards — each with stable IDs, directed refs, and structured fields.

Flag & Claim Gates

Discovery, seed, delta, and blocker flags signal readiness. Coding agents can only claim claimable, unblocked flags.

Stage Registry

Organize work into named stages (milestones, experiments, horizons) with deterministic default selection.

Portable Skill Pack

The Ready Product Leader Skill Pack gives AI agents everything they need to create and refine product trees.

Governance Templates

Starter templates for agent guidelines, product-orchestrator charters, and workspace authority policies.

Validator Rules

A defined set of required and warning checks so importers and compilers fail loudly on ambiguous source truth.