# Ready Standard

## Docs

- [Flags and Claim Gates: Controlling Coding Readiness](https://docs.dotready.org/concepts/flags-and-claims.md): Flags are attention records attached to primitive branches that control when a coding agent may claim implementation work and what proof removes the flag.
- [Governance Documents, Standard Resources, and Artifacts](https://docs.dotready.org/concepts/governance.md): Project governance, the Ready standard package, and artifact directories each serve a distinct role in constraining and supporting product work.
- [Primitive Records: Typed YAML Units of Product Truth](https://docs.dotready.org/concepts/primitive-records.md): Primitive records are typed .ready.yml files that hold every durable product decision — parsed, validated, diffed, and compiled into views by any tool.
- [Product Tree: The Git-Backed Source of Product Truth](https://docs.dotready.org/concepts/product-tree.md): A Ready product tree is a Git-backed filetree that stores product truth as typed YAML records, compiled into views for any audience or tool.
- [Prepare a Product Tree Work Package for Coding Agents](https://docs.dotready.org/guides/coding-handoff.md): How to write seed and delta flags that give coding agents everything they need to claim, implement, verify, and return evidence without avoidable blockers.
- [Organize Your Product Tree with Stages and Milestones](https://docs.dotready.org/guides/managing-stages.md): Learn how to create, configure, and manage product tree stages — from a first milestone to horizon concepts — using the root manifest stage registry.
- [How to Start a New Ready Product Tree from Scratch](https://docs.dotready.org/guides/starting-a-project.md): Bootstrap a Ready product tree for any project — from human docs, an existing codebase, or a discovery conversation — step by step.
- [How to Version and Review a Ready Product Tree with Git](https://docs.dotready.org/guides/using-git.md): Use Git to branch product experiments, review primitive edits, merge accepted truth, and keep an auditable history of product decisions.
- [Write High-Quality Primitive Records in Ready Standard](https://docs.dotready.org/guides/writing-primitives.md): A practical how-to for writing .ready.yml primitive records — premises, intents, standards, services, and question cards — with full YAML examples.
- [Ready Standard: Git-Backed File Format for Product Truth](https://docs.dotready.org/introduction.md): Ready Standard is a specification for storing product direction as typed YAML records in git — review, diff, and merge product decisions alongside code.
- [Ready Standard Quickstart: Your First Product Tree](https://docs.dotready.org/quickstart.md): Set up your first Ready product tree step by step — from creating the directory structure to writing your first primitive record and governance stubs.
- [Ready Standard Product Tree Directory Layout Reference](https://docs.dotready.org/reference/directory-layout.md): The recommended filetree structure for a conforming Ready product tree, with guidance on each directory, its purpose, and the rules that govern it.
- [Ready Product Tree Manifest Files Schema Reference](https://docs.dotready.org/reference/manifest-schema.md): Complete schema reference for all Ready manifest files: the root stage registry, per-stage manifests, governance manifests, and artifact manifests.
- [.ready.yml Primitive Source Record Schema Reference](https://docs.dotready.org/reference/ready-yml.md): Complete field reference for the .ready.yml primitive source format, including required fields, type-specific content, artifact metadata, and ref syntax.
- [Ref Roles and Relationship Rules for Ready Primitives](https://docs.dotready.org/reference/ref-roles.md): The five approved ref roles for Ready primitives, canonical edge directions, compact vs. explicit syntax, and rules for storing and deriving inverse edges.
- [Required and Warning Validator Rules for Ready Trees](https://docs.dotready.org/reference/validator-rules.md): All required and warning-level validation checks that a conforming Ready product-tree importer or docs compiler must apply before accepting source truth.
- [Ready Product Leader Skill Pack for AI Agents Guide](https://docs.dotready.org/skills/overview.md): The Ready Product Leader Skill Pack gives AI agents a portable, versioned set of instructions for creating and refining Ready product trees.
- [Ready Skill Modules: All Five Specialist Agent Guides](https://docs.dotready.org/skills/skill-modules.md): Five specialist modules extend the Ready Skill Pack — each handles a focused domain and loads only when the product tree has a relevant gap to close.
- [Governance Document Templates for Your Ready Project](https://docs.dotready.org/templates/governance-templates.md): Four governance templates let you define agent behavior, authority hierarchy, product process, and workspace access policy for any Ready-based project.
- [Ready Standard Project Templates: Complete Setup Guide](https://docs.dotready.org/templates/overview.md): Ready project templates are starter files you copy into a target project, fill in placeholders, and commit as that project's own reviewed product truth.